> -----Original Message-----
> From: Hiroshi Saito [mailto:saito at inetrt.skcapi.co.jp] 
> Sent: 05 July 2005 03:03
> To: slony1-general at gborg.postgresql.org
> Cc: Magnus Hagander; Andreas; Dave Page
> Subject: Service handling of Slon
> 
> Should turn with Win32 the operation of Slon is Services.
> It looks like pg_ctl, and it entails a kill signal. 

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.

> Therefore, 
> I propose it as sl_ctl. Then, it thinks that it should be used 
> in all the platforms. (don't kill -9 slon....)

'kill -9' is not a problem. In PostgreSQL that warning is given because
an individual backend cannot properly release locks and clean shared
memory if it's kill -9'd. The same warning used to be given for the
postmaster, however that can recover cleanly using WAL in modern
versions. Kill -9 should not be an issue for Slon.

Regards, Dave.