Re: Time to start populating ltsp-config.d?

On Fri, Mar 26, 2010 at 08:43:29AM +0200, Alkis Georgopoulos wrote:
> I'd like to introduce a new ENABLE_WOL lts.conf variable:
> 
> if boolean_is_true "$ENABLE_WOL" && [ -x /usr/sbin/ethtool ]; then
>     ethtool -s "$(ip route | grep default | cut -d " " -f5)" wol g || true
> fi

i think ltsp_config and ltsp_config.d shouldn't be used to do anything other
than set variables. i'm not sure off the top of my head where it should go-
ltsp-init-common and one of the init scripts perhaps?

> I'd put it in ltsp_config, but I think it's becoming too cluttered, and
> it'd be better if we started putting things in ltsp-config.d/*
> instead...

i do think we should split ltsp_config into ltsp_config.d snippets, though i
would want to add support so that sysadmins could drop files in
/etc/ltsp/ltsp_config.d, and packages should install hooks into
/usr/share/ltsp/ltsp_config.d. they can be processed in order(i.e. /etc/ and
then /usr/share/ltsp), presuming that all hooks properly check if variables get
set before resetting them.

live well,
  vagrant

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_____________________________________________________________________
Ltsp-developer mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-developer
For additional LTSP help,   try #ltsp channel on irc.freenode.net