Le lundi 27 août 2007 à 15:19 -0500, Scott Balneaves a écrit : > > Don't forget that you can run ssh under inetd/xinetd, which means that, > > until there's a connection, you don't use any resources. > Good point, we'd have to do some fancy footwork for a few things: > 1) We don't want a static inetd.conf, as if no printer's defined > for a terminal, there's no point in starting jetpipe at all. So, > what we'd want to do, on boot, is zero out the inetd.conf file, and > then update-inetd calls based on things like if PRINTER_0_DEV/PORT > are set, LOCALDEV=true are set, etc.
xinetd supports a configuration directory instead of a single configuration file. Every service has its own file in /etc/xinetd.d. So the init scripts could just write files in /etc/xinetd.d to activate the required services, then launch xinetd (or kill -HUP if it's already started). > 2) Some services would need to be modified to work under inetd, > i.e. both ltspfsd and jetpipe bind to ports, as opposed to listening > on stdin/out, however, this is just a case of turning the crank. > Some further investigation/discussion would be needed to see if this is > a worthwhile way to go. > > Cheers, > Scott > -- Jean-Michel Dault <[EMAIL PROTECTED]> Révolution Linux inc. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _____________________________________________________________________ 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
