reassign 505292 vserver-debianutils severity 505292 wishlist thanks * Ola Lundqvist <[EMAIL PROTECTED]> [2008-11-12 01:53-0500]: > On Tue, Nov 11, 2008 at 11:24:25PM +0100, Harald Weidner wrote: > > Hello, > > > > > I can hardly see that this is a problem in the vserver-debiantools > > > package. > > > > I have now found out that it is a bug in the util-vserver package.
Actually, this is not a bug in util-vserver, it is considered by upstream as a feature. The util-vserver package aims to only start the services that are vital to the guest persisting, and any other service should be enabled by the administrator, rather than running by default consuming resources without any point. It is the position of util-vserver that administrators should enable the services that they want. If you want cron, you should enable cron. All default guests are built to only come up with just syslog running, and you are expected to enable any other service that you want to be running. Now, I believe that a lot of people debootstrap guests and expect many fundamental system elements to be enabled, as they are creating mini-servers, however there are many people who create contexts just to exec processes, and do not necessarily want any services running in them, except for the ones that they have explicitly setup to run there. It seems as if the desire to have cron enabled in guests is a strong one, that should be something that vserver-debiantools provides, rather than something that util-vserver changes, at least that is until util-vserver provides profile support (which is on the TODO). > > Removing any system startup links for /etc/init.d/cron ... > > /etc/rc1.d/K11cron > > /etc/rc2.d/S89cron > > /etc/rc3.d/S89cron > > /etc/rc4.d/S89cron > > /etc/rc5.d/S89cron > > This is done deliberately, guests on Fedora/CentOS/etc. do not even have cron installed, much less enabled, so this is being done for conformity's sake. > > - (sysklogd|syslog-ng|rsyslog|dsyslog) > > + (sysklogd|syslog-ng|rsyslog|dsyslog|cron) > > ;; > > (README|skeleton|sendsigs|single|rc|rc.local|rcS) > > ;; > > The only reason that syslog is enabled is so that the guests work on kernels where persistent contexts aren't supported. > > What to do now? Is it possible to reassign this bug to the package > > util-vserver, or shall I file a new bug? Seeing as upstream finds this intentional, its probably best for newvserver to re-enable cron for people, rather that util-vserver to revert the change from upstream. Micah
signature.asc
Description: Digital signature
