Tue Jul 5 08:48:30 PDT 2005
- Previous message: [Slony1-general] Service handling of Slon
- Next message: [Slony1-general] Re: Service handling of Slon
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> -----Original Message----- > From: Hiroshi Saito [mailto:saito at inetrt.skcapi.co.jp] > Sent: 05 July 2005 08:31 > To: Dave Page; slony1-general at gborg.postgresql.org > Cc: Magnus Hagander; Andreas > Subject: Re: Service handling of Slon > > > No - there is not sl_ctl at present, so we should not add > one. We only > > did that on PostgreSQL because pg_ctl already existed. Adding the > > service code directly to slon is no problem anyway - that's > how I did it > > with pg_autovacuum. > > Ooops, Do you work service into slon? Not yet, but if Magnus gets short of time when he's porting the rest of it, I can help out with that. > From the main of slon to control exec slon process. > Probably, you are the thought which solves a HUP problem.:-) >From a brief glance at the code, HUP just restarts slon using slon_kill_child() & execvp() so putting in a huge amount of work to emulate signals is probably of little benefit (unless I missed something), given that the SCM makes it nice and easy to restart a service on Windows. /D
- Previous message: [Slony1-general] Service handling of Slon
- Next message: [Slony1-general] Re: Service handling of Slon
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list