Run scripts

Run scripts

[Gilles Sadowski]

Hello.

Does anyone have a run script for "postgresql"?

The script at
  http://smarden.org/runit/runscripts.html
is quite outdated.

Best,
Gilles

Re: Run scripts

[Mike Buland]

Sure, I haven't looked at the one online, but I use this:

#!/bin/bash

exec chpst -u postgres /usr/bin/postmaster \
   -D /srv/pgsql/data 2>&1

Works pretty well, you should change /srv/pgsql/data to whatever the path to 
your cluster is, and of course, use whatever your postgres user is.

--Mike

On Friday 04 July 2008 09:22:32 am Gilles Sadowski wrote:
> Hello.
>
> Does anyone have a run script for "postgresql"?
>
> The script at
>   http://smarden.org/runit/runscripts.html
> is quite outdated.
>
> Best,
> Gilles

Re: Run scripts

[Gilles Sadowski]

Hi.

> exec chpst -u postgres /usr/bin/postmaster \
>    -D /srv/pgsql/data 2>&1
> 
> Works pretty well, you should change /srv/pgsql/data to whatever the path to 
> your cluster is, and of course, use whatever your postgres user is.

Well, I've just installed postgresql 8.3 and I was fairly lost because I was
expected more automatic configuration to take place (I use Debian).
As far as I can tell, the install just created an empty /var/lib/postgresql
directory.  In the end browsing through the documentation on the
postgresql web site, I tried "initdb". And there it was.
The second thing is that all the programs (like "postmaster") are not in
/usr/bin but in /usr/lib/postgresql/<version>/bin.  Again that's not
indicated in the Debian readme file.
But the usual startup script (in /etc/init.d) is quite complex, so I guess
that for "normal" people, it might have performed everything necessary (?)
at first launch.

Anyways, now it runs ;-)

Thanks,
Gilles

Re: run scripts

[TheOldFellow]

Charlie Brady wrote:
> 
> On Thu, 6 Oct 2005, Daniel Zilli wrote:
> 
>> I'm start working with runit and found it great. I would like to
<snip>
> What's also important is that the TERM signal will actually cause the
> process to shut down. A few badly behaved programs don't do that - mysql
> in particular.

But you can use a finish script to kill them (or send them their correct
shutdown signals).  I find that I need to do that for the nfsd threads
after stopping mountd (with rpc.nfsd -- 0).

> It's common practice to have programs log to stderr rather than via syslog.

Unless you use socklog (recommended).

R.

Re: run scripts

[Charlie Brady]

On Thu, 6 Oct 2005, Daniel Zilli wrote:

> I'm start working with runit and found it great. I would like to migrate 
> all my rc.d scripts (slackware 10.2) to runit scheme. Some scripts are 
> easy other hard to migrate. I would like some advise. What do I need 
> consider when writing runit scripts ?

What's critically important is that the program must keep running, and 
must not "put itself into the background" or "daemonize itself".

What's also important is that the TERM signal will actually cause the 
process to shut down. A few badly behaved programs don't do that - mysql 
in particular.

It's common practice to have programs log to stderr rather than via 
syslog.

run scripts

[Daniel Zilli]

Hi!

I'm start working with runit and found it great. I would like to migrate 
all my rc.d scripts (slackware 10.2) to runit scheme. Some scripts are
easy other hard to migrate. I would like some advise. What do I need 
consider when writing runit scripts ?

Bests,
Daniel Zilli