Solved. It was permissions; I think I'd been staring at my monitor
too long.

I'm not using start-stop-daemon anymore, however I have tested it and
can confirm it works.


--- Glyn Astill <glynastill at yahoo.co.uk> wrote:

> Hi Chris,
> 
> It seems it may not be the start-stop-daemon afterall. I changed my
> script to not use it and just start via su. 
> 
> E.g. I have this:
> 
> su - $PGUSER -c "$SLONDAEMON -f $SLONCONF &" >> "$SLONLOG" 2>&1 <
> /dev/null
> echo "su - $PGUSER -c '$SLONDAEMON -f $SLONCONF &' >> "$SLONLOG"
> 2>&1
> < /dev/null"
> 
> And it echos to the screen the following
> 
> su - slony -c '/usr/local/pgsql/bin/slon -f
> /data/postgres/slon.conf'
> >> /data/postgres/
> slon.log 2>&1 < /dev/null
> 
> Does that look wrong?
> 
> Either way, I end up with the following in my log file:
> 
> 2008-01-10 12:34:59 GMT ERROR  could not open configuration file
> "/data/postgres/slon.conf"
> 2008-01-10 12:34:59 GMT CONFIG main: slon version 1.2.12 starting
> up
> usage: /usr/local/pgsql/bin/slon [options] clustername conninfo
> 
> And slon.conf is there:
> 
> -rwxrw-rw- 1 slony slony 4513 2008-01-09 17:55
> /data/postgres/slon.conf
> 
> 
> 
> --- Christopher Browne <cbbrowne at ca.afilias.info> wrote:
> 
> > Glyn Astill <glynastill at yahoo.co.uk> writes:
> > > Actually.. How do I run strace from with my start script?
> > >
> > >
> > > I'm basically doing:
> > >
> > > prefix=/usr/local/pgsql
> > > PGDATA="/data/postgres"
> > > PGUSER="slony"
> > > SLONLOG="$PGDATA/slon.log"
> > > SLONCONF="-f $PGDATA/slon.conf"
> > > SLONPID=="$PGDATA/slon.pid"
> > >
> PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
> > > DAEMON="$prefix/bin/slon"
> > >
> > > start-stop-daemon --start --verbose --pidfile $SLONPID --chuid
> > > $PGUSER --exec $DAEMON -- $SLONCONF 
> > 
> > Actually, I think I now see the problem, at least partly.
> > 
> > I expect that "start-stop-daemon" isn't invoking slon the way it
> > expects to be invoked.
> > 
> > start-stop-daemon is presumably a function with a bunch of
> > parameters
> > which then assembles a command line to use to invoke a daemon
> > program.
> > 
> > I'll bet that it *isn't* assembling something looking like:
> > 
> >    /usr/local/pgsql/bin/slon -f /data/postgres/slon.conf
> > 
> > I don't know what it *is* building, but I can only assume that
> it's
> > NOT that (and I'm pretty sure I'm right ;-)).
> > 
> > It may be assembling something like:
> > 
> >    /usr/local/pgsql/bin/slon -- -f /data/postgres/slon.conf
> > 
> > (though that is simply a wild guess)
> > 
> > I haven't tried to "seriously daemonize" the slon; it *isn't* a
> > daemon
> > in the sense of automatically throwing itself into the
> background,
> > so
> > I haven't tried to use tools that expect to work with true
> daemons.
> > -- 
> > let name="cbbrowne" and tld="acm.org" in String.concat "@"
> > [name;tld];;
> > http://www3.sympatico.ca/cbbrowne/linux.html
> > Why are men like blenders?
> > You need one, but you're not quite sure why. 
> > 
> 
> 
> 
>       ___________________________________________________________
> Yahoo! Answers - Got a question? Someone out there knows the
> answer. Try it
> now.
> http://uk.answers.yahoo.com/ 
> 
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general
> 



      ___________________________________________________________
Yahoo! Answers - Got a question? Someone out there knows the answer. Try it
now.
http://uk.answers.yahoo.com/