[12:35] <KurtKraut> I have Ubuntu running in a desktop CPU. I use this machine as personal webserver. Actually, I'm using Dapper's kernel for desktop. I would have a better performance with linux-image-server ?
[10:38] <blue-frog> I installed timeoutd on my breezy, there's a script in /etc/init.d . what command must I do for timeoutd to be run at boot time pls? (update-rc?)
[10:46] <lionelp__> blue-frog: yes, it is update-rc.d
[10:46] <blue-frog> ty
[10:46] <infinity> blue-frog: It's not already set up to do so?
[10:47] <blue-frog> apparently not, timeoutd shows up in /etc/init.d but it's not launched at boot time
[10:47] <infinity> (base)adconrad@cthulhu:~$ ls -l /etc/rc?.d/???timeoutd
[10:47] <infinity> lrwxrwxrwx 1 root root 18 2006-05-19 18:47 /etc/rc0.d/K20timeoutd -> ../init.d/timeoutd
[10:47] <infinity> lrwxrwxrwx 1 root root 18 2006-05-19 18:47 /etc/rc1.d/K20timeoutd -> ../init.d/timeoutd
[10:47] <infinity> lrwxrwxrwx 1 root root 18 2006-05-19 18:47 /etc/rc2.d/S20timeoutd -> ../init.d/timeoutd
[10:47] <infinity> lrwxrwxrwx 1 root root 18 2006-05-19 18:47 /etc/rc3.d/S20timeoutd -> ../init.d/timeoutd
[10:47] <infinity> lrwxrwxrwx 1 root root 18 2006-05-19 18:47 /etc/rc4.d/S20timeoutd -> ../init.d/timeoutd
[10:48] <infinity> lrwxrwxrwx 1 root root 18 2006-05-19 18:47 /etc/rc5.d/S20timeoutd -> ../init.d/timeoutd
[10:48] <infinity> lrwxrwxrwx 1 root root 18 2006-05-19 18:47 /etc/rc6.d/K20timeoutd -> ../init.d/timeoutd
[10:48] <infinity> Well, it's configured to start.
[10:48] <infinity> update-rc.d won't help you here (since it was already run successfully to do exactly what you want)
[10:48] <blue-frog> it shows up in all rc* indeed but I still have to start it manually
[10:49] <lionelp__> infinity: blue-frod is on breezy
[10:49] <infinity> So, find out why it's not starting, then. :)
[10:49] <infinity> lionelp__: Makes no difference.  As he says, it has the links in the right place in breezy too.
[10:49] <lionelp__> oups, i missed it
[10:49] <infinity> blue-frog: Make the init script log its actions somehwere and see if there's some reason it's dying on boot.
[10:50] <lionelp__> blue-frog: yesterday you told that you were not sure of your configuration syntax
[10:50] <lionelp__> that maybe the reason
[10:50] <blue-frog> config syntax problem is to have timeoutd reading correctly /etc/timeouts
[10:51] <blue-frog> am not sure about my syntax in /etc/timeouts
[10:51] <blue-frog> which so far is
[10:52] <blue-frog> Al:*:joe:*:2:3:5:WARN
[10:52] <blue-frog> the figures are riciculously low for my tests...
[10:53] <infinity> blue-frog: Well, does it start correctly with "/etc/init.d/timeoutd start"?  If so, then config syntax won't change how it works at boot versus how it works later.
[10:53] <blue-frog> otherwise I just installed timeoutd using synaptic and didn't touch anything else
[10:53] <infinity> If it's failing to start ONLY at boot, then there's something special about the state of the machine at S20 that's making timeoutd not start.
[10:54] <blue-frog> yes starting manually causes no problem to the daemon
[10:54] <blue-frog> and I think of it I have a similar problem with ssh and samba as well now
[10:55] <blue-frog> not starting at boot but starting and working manually ok
[10:56] <blue-frog> ps ax gives me   8178 ?        Ss     0:00 /usr/sbin/timeoutd
[10:57] <lionelp> why not :)
[10:58] <lionelp> did ps show you an init script that is still running ?
[10:58] <blue-frog> ps gives me bash and ps
[10:59] <lionelp> ps waux or similar i mean :)
[11:00] <blue-frog> not sure what am supposed to look for with px waux, gives me shitloads of lines
[11:01] <lionelp> ps waux | grep init.d
[11:01] <blue-frog> /bin/sh /etc/init.d/rc 2
[11:02] <lionelp> Ok
[11:02] <lionelp> You should not have anything
[11:03] <blue-frog> aha ah
[11:03] <lionelp> One of the starting script never ends
[11:03] <blue-frog> ok i know which
[11:03] <lionelp> it starts with a letter before "S" :)
[11:03] <blue-frog> hotkeysetup, i deleted it in /etc/ini.td but dind't take out the links
[11:04] <infinity> Uhm, if rc is still stuck between runlevels, that's generally considered bad, yes. :)
[11:05] <blue-frog> so is ther a command to update all rc* or do i have to rm manually the bad links?
[11:05] <lionelp> you have to do it manually
[11:06] <blue-frog> ok will do ty for this, now any idea why my /etc/timeouts seems not to be read correctly pls?
[11:06] <infinity> update-rc.d hotkeysetup remove
[11:06] <infinity> But why did you remove it in the first place? :)
[11:07] <blue-frog> was new to linux and kept having lines an d lines in the logs about key not assigned
[11:07] <infinity> Oh, it's hotkey-setup, not hotkeysetup, according to my system.
[11:07] <blue-frog> yes sry typo from my part
[11:07] <infinity> blue-frog: You could have just purges the hotkey-setup package. :)
[11:08] <blue-frog> that's what i would do now yes, but kind of forgot about waht i did ^ months ago :)
[11:09] <blue-frog> k links removed
[11:09] <blue-frog> infinity, are you familiar with time restriction and session timeout pls?
[11:10] <infinity> I don't use timeoutd, sorry.
[11:10] <infinity> Just installed it for 20 seconds up there to check on your init.d problem.
[11:11] <blue-frog> too bad for me, and about account required pam_time.so in /etc/pam.d/common-account?
[11:11] <blue-frog> I have a weird thing going on with gksudo when I do it
[11:11] <lionelp> blue-frog: it works for me
[11:12] <lionelp> I do a simple test with timeoutd
[11:12] <lionelp> lionel@cigogne:~$
[11:12] <lionelp> You have exceeded your idle time limit.  Logging you off now.
[11:12] <lionelp> Connection to cigogne closed by remote host.
[11:12] <lionelp> Connection to cigogne closed.
[11:12] <blue-frog> what 's your syntax in /etc/timeouts pls lionel?
[11:12] <lionelp> Only one line:
[11:12] <lionelp> Al:*:lionel:*:2:0:0:0
[11:13] <blue-frog> hum same than me but now as all my daemon were not loaded i may have a problem from ther
[11:13] <blue-frog> going to load all of them and i'll be back
[11:13] <infinity> I don't use pam_time either, though it looks somewhat straightforward.
[11:14] <blue-frog> inifinity, yes it is straight forward
[11:14] <blue-frog> but as soon as I activate pam_time.so, my admin account is not able to use the graphical frontend for programs such as synaptic
[11:15] <infinity> Then I suspect you configured it wrong. :)
[11:15] <blue-frog> while sudo in console stilll works, going to load everything, might be coming from that unachieved boot...
[11:15] <blue-frog> configured what?
[11:15] <infinity> pam_time
[11:15] <lionelp> blue-frog: hunt only one problem at the same time :)
[11:16] <lionelp> timeoutd and pam_time are two different things
[11:16] <blue-frog> well as you said straight forward so i din't fiddled with much thing except pam.d/coomon-account...well yes c ya in a bit
[11:16] <blue-frog> right lionel
[11:31] <blue-frog> infinity, lionel ty for your help, found the script that was hanging up in rc2, was partimage server...removed it all works fine now, timeouts and so on...will double check in 10 minutes about this gksudo problem
[11:34] <lionelp> nice
[11:34] <blue-frog> this timeou thing is most helpful as otherwise someone connectiong 2 minutes vbefore the end of its authorized session can stay connected forever
[11:35] <blue-frog> still i have to make timeoutd check for time range but i'll get there eventually
[11:36] <blue-frog> is there a way to accelerate the sudo timeout pls?
[11:37] <blue-frog> I mean to force it
[11:38] <lionelp> blue-frog: sudo -K
[11:39] <blue-frog> ty
[11:39] <blue-frog> what about gksudo
[11:42] <blue-frog> don't see anything in man
[11:42] <blue-frog> and sry for sudo, man would have given me the answer
[11:43] <lionelp> that is more a desktop issue than a server issue btw
[11:43] <blue-frog> it is indeed but the problem with the other channels is that they are more into displaying nvidia and ati stuff than anything else unfortunately
[11:44] <blue-frog> or installing games... :(
[11:44] <lionelp> i know, i know
[11:45] <blue-frog> btw regarding timeoutd and pime_time, if I setup damba-ldap pam_time and timeoutd will still work the same correct?
[11:46] <blue-frog> sry for typos..
[11:46] <blue-frog> anyway will install it so iw ill see by myself, not thinking straight today..
[11:46] <lionelp> it is more or less the same
[11:47] <lionelp> I ma note sure (I do not remember, but samba guide should say) if time policy are realy used bu samba
[11:48] <blue-frog> it's ok made myself a script that installs/configure samba-ldap in 5 minutes so it's easy for me to check...
[11:48] <lionelp> blue-frog: does timeoutd covers your needs ? It will logout a user only if he is idleing, right ?
[11:48] <blue-frog> not only
[11:49] <blue-frog> you can specify idle, max time in session, max time per day
[11:49] <blue-frog> and normally it can check as well for time range
[11:49] <blue-frog> by adding it just after Al for exaple
[11:50] <blue-frog> testing it right nw, will tell you in a minute
[11:50] <lionelp> ah yes, okay
[11:51] <lionelp> I should tell my school to use it instead of rebooting 5 times the workstations until people definitely left the school :)
[11:51] <blue-frog> hum have to man a bit more to make timeoutd checks the time range
[11:51] <blue-frog> that's exactly why am looking at it... children :)
[11:52] <lionelp> :)
[11:52] <lionelp> you work for a university ?
[11:52] <blue-frog> but that can be applied to all companies anyway..
[11:52] <blue-frog> no looking for a job
[11:52] <lionelp> I am not at school anymore
[11:53] <lionelp> (so do not call me children anymore ;-))
[11:53] <blue-frog> and been trainig myself hard on linux, so I am missing a lot of command line, but i can find my way around and perpare a server wihtout problems
[11:53] <blue-frog> :)
[11:54] <blue-frog> am not anti windows but pro linux...
[11:54] <blue-frog> now
[02:28] <blue-frog> am at a loss to achieve the following. joe can only log in and use gdm from 3pm ot 5pm. if he logs in at 4.45pm he must be disconnected at 5pm. fiddled with pam_time and timeoutd but can't achieve what I want, hints/help most welocmed
[02:51] <airjump> hello
[02:52] <lionelp> hi airjump
[02:53] <airjump> hi lionelp
[04:24] <BlackHand> hi
[04:26] <lionelp> Hi BlackHand
[04:29] <BlackHand> for server what fs can be the recomended for ubuntu
[04:29] <BlackHand> ext3, reiserfs or xfs ?
[04:30] <BlackHand> rhel and derived (centos, tao) don't use other thing that ext3 (centos support xfs in unofficial way) in suse i see reiserfs, but some ppls recomends me to stay away from reiserfs in servers
[04:30] <BlackHand> in the ubuntu server inititative will be a recomended fs  ?
[04:32] <maswan> My personal recommendation is ext3 or xfs depending if you value stability or performance highest.
[04:34] <lionelp> BlackHand: there was a rescent article on debian-administration about that
[04:34] <lionelp> http://www.debian-administration.org/articles/388
[04:34] <lionelp> it will give you more arguments than I can
[04:34] <BlackHand> gud
[04:35] <lionelp> The conclusion is that XFS is the best compromise (for those who are too lazy too read :-))
[04:36] <lionelp> I personnaly use XFS
[04:36] <BlackHand> yes i see
[04:37] <maswan> if you break your storage only slightly, xfs_repair is fairly good at finding your data. I don't have the same confidence in reiser tools.
[04:37] <BlackHand> and the point about xfs and 4k stacks ?
[04:38] <maswan> dunno, what was that point?
[04:41] <BlackHand> for example xfs + lvm or xfs + soft raid or worse xfs + lvm + soft raid, stack exhausting and core dump
[04:41] <maswan> ok, never seen that happen.
[04:41] <BlackHand> xfs alone (no other layer for device/filesystem) no probs
[04:42] <BlackHand> the ubuntu kernel have 4k stacks active ?
[04:42] <maswan> we run breezy with lvm+xfs and md+xfs and no issues.
[04:43] <maswan> not sure on lvm+md+xfs in produciton use right now
[04:44] <lionelp> I have no lvm+md+xfs here
[04:44] <lionelp> but I have md+xfs on breezy and dapper without probelm
[04:50] <BlackHand> uhm
[04:50] <BlackHand> ubuntu dont use 4K stacks i see now
[04:50] <BlackHand> no risk to reduced stack size for many layers in device/filesystem
[04:50] <BlackHand> ok
[04:51] <BlackHand> ^_^
[11:08] <CarlFK> lionelp: todays server install still failing on installing kernel https://launchpad.net/distros/ubuntu/+source/debian-installer/+bug/45248
[11:09] <CarlFK> hmm, that may still have been yesterdays .iso
[11:10] <CarlFK> yep.  let me try again today using today's image ;)