[Frugalware-devel] service question
vmiklos at frugalware.org
Tue Aug 5 16:25:52 CEST 2008
This is related to http://bugs.frugalware.org/task/154.
So, the question is: When should we enable / start a service after
By 'enable', I mean to run service foo add, so that it will be started
on next boot.
By 'start', I mean immediate start.
I think this is quite subjective, but it would be nice to make such a
decision then fix up buildscripts so that it will not be random.
Here is what I would propose:
- Never start a service automatically. This would be very problematic in
the installer, for example.
- For the 'enable' one, this is more problematic. First, some services
must be enabled, like udev, and such. OTOH, some packages have init
scripts which are obviously optional, like git's rc.git (the git
daemon, most devs won't need it at all).
Do you guys have an idea how could we define some rule so that we could
document it and if a user does a pacman -S randompackage then the user
can expect if the service will be enabled by default or not?
I think there are white, grey and black zones here. White is like udev
(it must be enabled), grey is like avahi (kde depends on it, but it is
not a musthave to have it enabled) or powernowd (you probably want to
enabled it but who knows), and black (starting git-deamon by default is
Or maybe - mainly because this question is not so trivial - we should
just leave the current situation untouched?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: not available
Url : /pipermail/attachments/20080805/680dce7a/attachment-0001.sig
More information about the Frugalware-devel