[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ltsp-discuss
Subject:    Re: [Ltsp-discuss] CHROOT: Installing cron, client time is off
From:       Jordan Erickson <jerickson () logicalnetworking ! net>
Date:       2009-01-23 17:34:46
Message-ID: 4979FFB6.1020909 () logicalnetworking ! net
[Download RAW message or body]

Ah, another hidden variable! ;) Thanks Stéphane!

Googling that var gave me this URL: 
https://wiki.ubuntu.com/LtspUpdateManagerIntegration - this is something 
that I'd been thinking about as well (integrating chroot updates into 
update-manager for easy updates). Has there been any work done on this 
at all since the page was created?


Cheers,
Jordan/Lns



Stéphane Graber wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Jordan Erickson wrote:
>   
>> (Running Ubuntu 8.04.2)
>>
>> Hey all,
>>
>> I've been trying to get a simple cron script to run in my chroot that 
>> halts the thin-clients at a specified time. I've run into an issue:
>>
>> Initially, when installing cron in the chroot, it shows that the daemon 
>> launches (Starting periodic command scheduler cron [ ok ] - but it seems 
>> to launch on the SERVER because when I edit /opt/ltsp/i386/etc/crontab 
>> and add an entry to test the halt command, the server halts before my 
>> ltsp-update-image completes. :(
>>
>> This happens only once, until I bring the server back up. This should 
>> probably be fixed, and I'm glad I was testing it out on my own server 
>> instead of one of my production (well, more production than my own 
>> anyway) servers. Cron starts fine on the client after this little 
>> fiasco. I was able to easily reproduce this by 
>> uninstalling/re-installing cron (after checking my own mental sanity).
>>
>> I'm assuming this is a cron issue - should I file a bug with them?
>>
>>
>> Cheers,
>> Jordan/Lns
>>     
>
> This is the expected behavior of a chroot.
> When installing a chrooted service, this one starts as it would do on a
> normal system and except the different system root has access to
> everything including the ability to kill all your processes and reboot
> your server.
>
> The fix as it's implemented in LTSP is to do:
> export LTSP_HANDLE_DAEMONS="false"
>
> and then do you apt-get installs, this way the daemon won't start when
> installed in the chroot.
>
> Stéphane
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkl5W10ACgkQjxyfqkjBhuyOXwCeKHt+ucXVN0dz+b/rr1O1VXqF
> pNEAnRGitVsicxJKNZsjsXJPNiZK+qzf
> =AVA6
> -----END PGP SIGNATURE-----
>   


------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

[prev in list] [next in list] [prev in thread] [next in thread]