[18:25] <mikhas> heya - just a quick question: can I configure upstart dependencies so that if service A needs a restart, service B is restarted, too?
[18:29] <ion> B: start on started A, stop on stopping A
[18:32] <mikhas> hm, will that  also work if A crashes?
[18:32] <ion> yes
[18:33] <mikhas> cool, thanks!
[21:16] <mshadle> now that a lot of services are being setup to run via upstart, simple rc.d symlink management like S -> K to stop a service isn't an option. so what -is- the best way to say, not have vsftpd start on boot (without just rm /etc/init/vsftpd.conf or manually editing the file?)
[21:56] <mbiebl> mshadle: there is currently no better way than to either remove the file or comment out the "start on" lines
[21:56] <mbiebl> this is supposed to be fixed in 0.10
[21:59] <mshadle> how's the change going to be done?
[21:59] <mshadle> the other thing is to tell people "hey if you want to use upstart, you need an /etc/default/$daemon file, with $daemon_ENABLED="no" etc.
[22:10] <mbiebl> mshadle: afaik the plan is to use "override" files
[22:11] <mbiebl> Keybuk can tell you more, when he's around
[22:59] <JanC> well, you can make the /etc/default/* option work now
[23:11] <ion> Well, there’s really not much of a difference between changing a value in /etc/init/foo.conf and changing a value in /etc/default/foo, except that the latter just splits stuff to two files for no reason.
[23:49] <mbiebl> ion: the reasoning behind separate "override" files is, that you can manipulate with say a run level editor
[23:49] <mbiebl> and your next package update will not cause a dpkg prompt
[23:50] <ion> Yeah, but we were talking about /etc/default/foo with foo_enabled="no", which sounds like /etc/init/foo.conf sourcing /etc/default/foo.
[23:51] <JanC> ion: which splits often used options from the main script...  ;)
[23:52] <JanC> editing or rewriting a script is fine for those who understand them, for others editing a simple config file is safer (and they are safer to edit by GUI tools too)
[23:55] <mbiebl> ion: well, yeah, I hate those /etc/default/foo files with foo_enabled=.. 
[23:56] <mbiebl> for sysv we already have a perfectly working mechanism to enable/disable scripts from being started on boot