← Back to team overview

ubuntu-phone team mailing list archive

Re: Customized Upstart Jobs/Overrides

 

hi,
Am Samstag, den 03.05.2014, 10:00 +0200 schrieb Martin Pitt:
> Oliver Grawert [2014-05-02 22:46 +0200]:
> > how about making the usage of /etc/default/ mandatory for all our own
> > services so we can easily disable them
> 
> Please please not. Parsing these has been a huge pain, source of bugs,
> and unnecessary shell scriptery for a long time, in both the upstart
> and tne systemd world. Also, they have no standardized format, so this
> is opposite to "easy".
and yet you use it in apport for enabling/disabling the service ? 

> 
> Both upstart and systemd have standard ways how to disable a service
> "foo": Create an upstart override with an empty "start", or "systemctl
> disable foo". Soon, update-rc.d in Ubuntu will work for all three
> systems (Debian's already does, we need to merge), so IMHO update-rc.d
> should be considered the standard interface for disabling/enabling
> services with any init system.

but that means giving the customizer direct access to the init system
configuration again, which i thought we wanted to avoid ... (and it will
also be very painful to make sure this works on our readonly setup)

ciao
	oli

Attachment: signature.asc
Description: This is a digitally signed message part


Follow ups

References