[Bug 694066] Re: RC_WHITELIST prevents a lot of services from being started on thin/fat clients
Alkis Georgopoulos
694066 at bugs.launchpad.net
Fri Feb 10 10:48:04 UTC 2012
Fix committed in http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-
trunk/revision/2008, it'd be nice if someone could check if the new
RM_SYSTEM_SERVICES and RM_THIN_SYSTEM_SERVICES lists are reasonable.
** Changed in: ltsp (Ubuntu)
Importance: Undecided => Medium
** Changed in: ltsp (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: ltsp
Status: Triaged => Fix Committed
** Changed in: ltsp
Assignee: Stéphane Graber (stgraber) => Alkis Georgopoulos (alkisg)
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ltsp in Ubuntu.
https://bugs.launchpad.net/bugs/694066
Title:
RC_WHITELIST prevents a lot of services from being started on thin/fat
clients
Status in Linux Terminal Server Project:
Fix Committed
Status in “ltsp” package in Ubuntu:
Fix Committed
Bug description:
In the Ubuntu/000-basic-configuration, some whitelists are defined for allowed services:
RCS_WHITELIST=${RCS_WHITELIST:-"mountkernfs.sh mountdevsubfs.sh hostname.sh loopback udev module-init-tools procps.sh etc-setserial ltsp-client-setup setserial console-setup console-screen.kbd.sh"}
RC2_WHITELIST=${RC2_WHITELIST:-"klogd sysklogd ltsp-client-core usplash rmnologin dbus"}
RC6_WHITELIST=${RC6_WHITELIST:-"reboot"}
RC0_WHITELIST=${RC0_WHITELIST:-"halt"}
On the other hand, Debian/000-basic-configuration has those lists commented out:
#RCS_WHITELIST=${RCS_WHITELIST:-"mountkernfs.sh mountvirtfs hostname.sh keymap.sh loopback udev mountdevsubfs.sh mountdevsubfs module-init-tools procps.sh etc-setserial ltsp-client-setup setserial console-screen.sh xorg-common x11-common xfree86-common ifupdown networking fuse nbd-client"}
#RC2_WHITELIST=${RC2_WHITELIST:-"klogd sysklogd ltsp-client ltsp-client-core nbd-client usplash rmnologin rsyslog dbus hal"}
For Ubuntu, where those variables are defined, the 000-init-whitelist plugin calls update-rc.d and prevents those services from starting on boot. A lot of those services are significant, for example cups (for printer sharing), ondemand (so that thin client CPUs don't overheat), sendsigs (for proper shutdown), binfmt-support (if wine or java apps are installed on the chroot), openbsd-inetd (if ident2 is installed on the chroot for squid), etc etc, see attached file.
Is there any reason for those white lists to be defined? Can we
comment them out like Debian does?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ltsp/+bug/694066/+subscriptions
More information about the foundations-bugs
mailing list