[Frugalware-devel] enabling services by default in upstart?

Alex Smith alex at alex-smith.me.uk
Wed Jun 20 17:58:15 CEST 2007


Christian Hamar [krix] wrote:
> 2007. 06. 15, péntek keltezéssel 21.31-kor VMiklos ezt írta:
>> hi,
>>
>> in sysvinit, you have a default: if you install rc.foo then it'll be
>> never started by default, we have to write an install scriptlet to
>> enable a service
>>
>> in upstart, you can choose the default:
>>
>> 1) enable each job by default, so that we have to write a scriptlet to
>> disable it
>>
>> 2) disable jobs by default, just like in sysvinit
> Well. I dont know upstart but, all services enabled at scriptlet or
> disabled right now no ? I mean like in sysvinit, you install a package
> putting upstart script into place and then it will be enabled by
> default ?
> 
> I think its bad. Why enable default a cups server or anything else, if i
> dont have a printer. Or why enable acpid or anything else that installed
> by default or by mass-install :S

Nobody here seems to remember me mentioning that I can quite easily have 
cups/acpid/hardware stuff run only if the box needs it. But for that to 
work, I need the job enabled by default. Having something enabled only 
means that the job respond to events. Even if it's "enabled", it won't 
run unless it receives an event it's configured to run on...

> 
> I like the normal way like how its now.

Ok, that's what you like. What about other people?

> 
> BTW whats matter if we write disable (or enable) to a package install
> scriptlet ?

Writing enable in an install scriptlet is quite annoying for 
upstart-jobs. It requires sed hacks etc on upgrades if a job is renamed, 
and this results in there being a far higher chance of mistake (what if 
I make a typo?).

> 
> We cant calculate how our users thinking and what is good for them. (If
> enabled by default or disabled) Who will deal that we enable this or
> not ?

Then make a poll in the forums.

> 
> And afterall if we force users to disable or enable stuffs, then all the
> same. Does not matter if we say disable to all or enable to all. We
> force users to enable OR disable services

I prefer enable. Usually if a user installs a package, they probably 
want it to work.

-- 
Alex Smith
Frugalware Linux developer - http://www.frugalware.org


More information about the Frugalware-devel mailing list