On Wed, Nov 28, 2012 at 07:52:02PM -0500, John Hupp wrote: > But I find no documentation regarding scripts in /usr/share/ltsp/init-ltsp.d. > Is this an LTSP-PNP innovation?
The general ltsp documentation probably needs a bit of updating. The init-ltsp.d hooks are executed from /sbin/init-ltsp, which is a fairly recent LTSP development (5.3+). It is used in recent LTSP versions, regardless of how you create the LTSP boot environment (i.e. thin client, fat client, LTSP-PNP). /sbin/init-ltsp is run in the place of /sbin/init, as the first process to run, and then hands it over to the *real* /sbin/init. The kernel boot parameter "init" is used to select the init process, and with LTSP, it passes "init=/sbin/init-ltsp". This hopefully allows more shared code and consistancy between different distros without relying on the same sort of initramfs, or in theory, no initramfs at all. > Could it be that these scripts are executed > after apcupsd has already started in the client environment? If that is so, > then using a /usr/share/ltsp/init-ltsp.d/50-apcupsd script to edit /etc/ > apcupsd/apcupsd.conf would have no effect. It will definitely run before any daemons or other processes are started, so you shouldn't worry about that. live well, vagrant ------------------------------------------------------------------------------ Keep yourself connected to Go Parallel: BUILD Helping you discover the best ways to construct your parallel projects. http://goparallel.sourceforge.net _____________________________________________________________________ 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
