| Newsgroups |
gmane.linux.terminal-server.devel |
| Message-ID |
<[email protected]> |
On Wed, Apr 16, 2008 at 08:53:02PM -0400, Warren Togami wrote:
> ltsp-init-common:
> configure_localdev() {
> if boolean_is_true "$LOCALDEV" ; then
> # Make this sessions secret auth cookie for ltspfs
> mcookie > /var/run/ltspfs_token
> /usr/bin/ltspfsd
> # cdrom devices are handled by the cdpingerponger
> /usr/sbin/cdpinger cdrom # default for usb cdroms
>
> # and start one for every additional cdrom device
> if [ -L /dev/cdrom?* ];then
> for CDDEV in $(ls /dev/cdrom?*); do
> /usr/sbin/cdpinger $(basename ${CDDEV})
> done
> fi
> fi
> }
>
> Are either of these needed?
this is definitely needed, until we switch to calling cdpinger and
ltspfsd from udev and/or add_fstab_entry.
i could merge my bzr branch to do this, but i'm not 100% happy with the
way the code has turned out:
http://llama.freegeek.org/~vagrant/bzr/ltspfs/ltspfs-udev-cdpinger/
but i think it's at least a proof of concept that is the right direction
to take it.
> * Apparently ltsp-setup hasn't been using the ltsp-init-common version.
> Is this code actually harmful?
no, both init scripts are run on debian and ubuntu and they are supposed
to do different things. ltsp-setup runs in the S runlevel and configures
things, whereas ltsp-core runs in runlevel 2 and starts services. it
hasn't perfectly matched that vision, but that's sort of how it always
worked, at least in my head.
live well,
vagrant
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_____________________________________________________________________
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