Re: Native upstart scripts – implemented

2010-05-10 Thread Jacek Konieczny
On Sun, May 09, 2010 at 02:52:57AM +0300, Elan Ruusamäe wrote: also, configtest before reload/restart action would be really important to have in upstart as well, considering that we restart services on rpm upgrades. Done. Not for 'initctl reload' (which is only 'kill -HUP'), but for

Re: Native upstart scripts – implemented

2010-05-09 Thread Jacek Konieczny
On Sun, May 09, 2010 at 02:52:57AM +0300, Elan Ruusamäe wrote: i'd rather avoid completely the new subpackage here, if needed move the /etc/init dir to filesystem package to avoid dirdeps pulling upstart, and use conflicts tag for the current requires tag. Patrys asked for subpackages and it

Re: Native upstart scripts – implemented

2010-05-09 Thread Elan Ruusamäe
On Sunday 09 May 2010 09:57:57 Jacek Konieczny wrote: On Sun, May 09, 2010 at 02:52:57AM +0300, Elan Ruusamäe wrote: i'd rather avoid completely the new subpackage here, if needed move the /etc/init dir to filesystem package to avoid dirdeps pulling upstart, and use conflicts tag for the

Re: Native upstart scripts – implemented

2010-05-09 Thread Elan Ruusamäe
On Friday 07 May 2010 16:33:21 Jacek Konieczny wrote: Hello, Your volunteer has done his job :) seems there's some deadlock with initctl emiting also seems the nice service name is lost there (see sshd part). also seems there's no our typical restart service after package upgrade, if you've

Re: Native upstart scripts – implemented

2010-05-09 Thread Jacek Konieczny
On Sun, May 09, 2010 at 11:39:14AM +0300, Elan Ruusamäe wrote: On Friday 07 May 2010 16:33:21 Jacek Konieczny wrote: Hello, Your volunteer has done his job :) seems there's some deadlock with initctl emiting Isn't that another result of https://bugs.launchpad.net/upstart/+bug/406397

Re: Native upstart scripts – implemented

2010-05-09 Thread Elan Ruusamäe
On Sunday 09 May 2010 12:00:57 Jacek Konieczny wrote: also seems the nice service name is lost there (see sshd part). How is that supposed to work and where is that 'sshd part'? line 1 and 3 - the nice name, line 4 plain service name 1: * Reloading OpenSSH

Re: Native upstart scripts – implemented

2010-05-09 Thread Elan Ruusamäe
On Sunday 09 May 2010 12:00:57 Jacek Konieczny wrote: I guess  --no-wait for emit should be used here. Though there is something blocking – emit waits for some action on the 'started' event to finish and some service starting on this even has probably locked up (most probably due to

Re: Native upstart scripts – implemented

2010-05-09 Thread Jacek Konieczny
On Sun, May 09, 2010 at 12:26:56PM +0300, Elan Ruusamäe wrote: On Sunday 09 May 2010 12:00:57 Jacek Konieczny wrote: also seems the nice service name is lost there (see sshd part). How is that supposed to work and where is that 'sshd part'? line 1 and 3 - the nice name, line 4 plain

Re: Native upstart scripts – implemented

2010-05-08 Thread Elan Ruusamäe
On Friday 07 May 2010 16:33:21 Jacek Konieczny wrote: Some documentation for the rc-scripts+upstart usage is here:   http://svn.pld-linux.org/cgi-bin/viewsvn/rc-scripts/branches/upstart_native /doc/upstart.txt?rev=11395view=markup does $JOB=_ has special meaning? ... emit starting JOB=_

Re: Native upstart scripts – implemented

2010-05-08 Thread Jacek Konieczny
On Sat, May 08, 2010 at 05:07:35PM +0300, Elan Ruusamäe wrote: On Friday 07 May 2010 16:33:21 Jacek Konieczny wrote: Some documentation for the rc-scripts+upstart usage is here:   http://svn.pld-linux.org/cgi-bin/viewsvn/rc-scripts/branches/upstart_native

Re: Native upstart scripts

2010-05-08 Thread Elan Ruusamäe
On Tuesday 04 May 2010 12:17:41 Jacek Konieczny wrote: What do you think? Should I try to prepare a proof-of-concept implementation? any plans of moving rc.sysinit also to upstart? -- glen ___ pld-devel-en mailing list

Re: Native upstart scripts

2010-05-08 Thread Elan Ruusamäe
On Saturday 08 May 2010 23:25:27 Jacek Konieczny wrote: And no, switching fully to Upstart at this point is not a good idea. Have anybody recently upgraded upstart 0.5 to 0.6 on a production machine? i've upgraded once. there was no way to reload init process. the TERM signal which was

Re: Native upstart scripts – implemented

2010-05-08 Thread Elan Ruusamäe
On Friday 07 May 2010 16:33:21 Jacek Konieczny wrote: Patryk Zawadzki pat...@pld-linux.org wrote: I'd opt for having 2 separate -init subpackages, one with the current rc.d contents and one with an upstart job description and a simple rc.d wrapper that runs start $foo, stop $foo etc.

Re: Native upstart scripts

2010-05-05 Thread Patryk Zawadzki
On Tue, May 4, 2010 at 11:17 AM, Jacek Konieczny jaj...@jajcus.net wrote: Hello, In PLD Th, we have upstart as the /sbin/init daemon for some time, but it is only used to start the old 'SysVinit' scripts from /etc/rc.d/init.d. To make full use of Upstart features, like process supervising,

Re: Native upstart scripts

2010-05-05 Thread Jacek Konieczny
On Wed, May 05, 2010 at 11:20:30AM +0200, Patryk Zawadzki wrote: On Tue, May 4, 2010 at 11:17 AM, Jacek Konieczny jaj...@jajcus.net wrote: In PLD Th, we have upstart as the /sbin/init daemon for some time, but it is only used to start the old 'SysVinit' scripts from /etc/rc.d/init.d. To

Re: Native upstart scripts

2010-05-05 Thread Jacek Konieczny
On Tue, May 04, 2010 at 07:40:43PM +0300, Elan Ruusamäe wrote: i don't like the idea that the links are managed via some script, i'd like easily to boot to upstart-mode or sysvinit-mode with a kernel commandline, or something in /etc/sysconfig/system the both solutions should be available and

Re: Native upstart scripts

2010-05-05 Thread Łukasz Jernaś
On Wed, May 5, 2010 at 11:20 AM, Patryk Zawadzki pat...@pld-linux.org wrote: On Tue, May 4, 2010 at 11:17 AM, Jacek Konieczny jaj...@jajcus.net wrote: Hello, In PLD Th, we have upstart as the /sbin/init daemon for some time, but it is only used to start the old 'SysVinit' scripts from

Re: Native upstart scripts

2010-05-05 Thread Patryk Zawadzki
On Wed, May 5, 2010 at 2:03 PM, Łukasz Jernaś deej...@srem.org wrote: Well, after seeing how many people have weird problems with PulseAudio I would be cautious about using another thing  thought out by Lennart... To be fair you have to admit that a vast number of the problems experienced

Re: Native upstart scripts

2010-05-05 Thread Jacek Konieczny
On Wed, May 05, 2010 at 02:13:51PM +0200, Patryk Zawadzki wrote: On Wed, May 5, 2010 at 2:03 PM, Łukasz Jernaś deej...@srem.org wrote: Well, after seeing how many people have weird problems with PulseAudio I would be cautious about using another thing  thought out by Lennart... To be

Re: Native upstart scripts

2010-05-05 Thread Patryk Zawadzki
On Wed, May 5, 2010 at 2:32 PM, Jacek Konieczny jaj...@jajcus.net wrote: I would rather say it is because of putting another audio server where it is not needed at all. ALSA alone does its job well enough nowadays (and if it does not, it should be fixed not wrapped with another layer).

Re: Native upstart scripts

2010-05-05 Thread Jacek Konieczny
On Wed, May 05, 2010 at 03:48:18PM +0200, Patryk Zawadzki wrote: This /sbin/init things are not that easy. We will always need some init daemon… though I still won't chose an implementation only basing on the fact that the idea is great. It must work and be maintained (or at least stable

Re: Native upstart scripts

2010-05-04 Thread Caleb Maclennan
2010/5/4 Jacek Konieczny jaj...@jajcus.net: I think Upstart support should be implemented as an option, coexisting with current solution, so the administrator may choose what he prefers and even use init.d for some services and upstart for other. +1  - chkconfig would link/unlink the files

Re: Native upstart scripts

2010-05-04 Thread Elan Ruusamäe
On Tuesday 04 May 2010 12:17:41 Jacek Konieczny wrote: What do you think? Should I try to prepare a proof-of-concept implementation? i describe ubuntu like implementation that i had in first mind to do: 1. some packages have been migrated to upstart, having /etc/init/service.conf file 2.

Re: Native upstart scripts

2010-05-04 Thread Jacek Konieczny
On Tue, May 04, 2010 at 12:04:39PM +0200, Patryk Zawadzki wrote: I think Upstart support should be implemented as an option, coexisting with current solution, so the administrator may choose what he prefers and even use init.d for some services and upstart for other. I was hoping for

Re: Native upstart scripts

2010-05-04 Thread Jacek Konieczny
On Tue, May 04, 2010 at 12:04:39PM +0200, Patryk Zawadzki wrote: - scripts in /etc/rc.d/init.d would emit 'started' and 'stopped'  events when necessary, so upstart services can rely on that I'd opt for having 2 separate -init subpackages, one with the current rc.d contents and one with an

Re: Native upstart scripts

2010-05-04 Thread Pawel Golaszewski
On Tue, 4 May 2010, Patryk Zawadzki wrote: I think Upstart support should be implemented as an option, coexisting with current solution, so the administrator may choose what he prefers and even use init.d for some services and upstart for other. I was hoping for eventually dropping rc

Re: Native upstart scripts

2010-05-04 Thread Pawel Golaszewski
On Tue, 4 May 2010, Jacek Konieczny wrote: Maybe we could make /etc/init.d a directory with symlinks to /etc/rc.d/init.d or the upstart wrapper, depending on what is used to handle the service? see how ubuntu made this. Every service is in that directory, some are links. I can see how does

Re: Native upstart scripts

2010-05-04 Thread Elan Ruusamäe
On Tuesday 04 May 2010 12:17:41 Jacek Konieczny wrote: My proposition: - packages will provide upstart configuration files in /etc/rc.d/upstart - those could be linked or copied to /etc/init/subsys when needed   - chkconfig would link/unlink the files when requested (global     configuration

Re: Native upstart scripts

2010-05-04 Thread Jacek Konieczny
On Tue, May 04, 2010 at 07:40:43PM +0300, Elan Ruusamäe wrote: On Tuesday 04 May 2010 12:17:41 Jacek Konieczny wrote: My proposition: - packages will provide upstart configuration files in /etc/rc.d/upstart - those could be linked or copied to /etc/init/subsys when needed   - chkconfig