On Wednesday 30 November 2005 13:23, Mike Leahy wrote: I have a rather slow server box on which the postgresql init script always claimed that startup failed. However, postgresql was running quite happily with no apparent probs. I tracked it down to a timeout in the init script: /etc/init.d/postgresql, line 191-192: $SU -l postgres -c "$PGENGINE/postmaster -p '$PGPORT' -D '.blahblah......& ... sleep 2 The timeout was simply too short for postmaster to init itself on the old box (350MHz PII), and the wrapper script thought the whole thing had failed. I increased it to 6 seconds, and while the service takes a little longer to start (duh), it no longer displays an ugly red [FAILED] message. As a side note, I had to do an SElinux relabeling to get postgresql to work initially.. Why, I don't know (the system has never run with selinux turned off). Relabeling seems to be the cure way too often, when strange problems occur that seem inexplicable (before you check /var/log/audit.log). Øyvind -- < Øyvind Stegard < oyvinst at ifi uio no > < http://www.oyvind.nu/ < `Lottery: A tax on people who are bad at math.'

At 11:01 PM -0600 12/2/05, Christofer C. Bell wrote: Or, how about having a 2 second timeout test that loops up to 5 times, so that it will run fast if startup is fast? (An RFE might be appropriate if someone actually does this. Fixed timeouts, ugh.) ____________________________________________________________________ TonyN.:' <mailto:tonynelson@georgeanelson.com> ' <http://www.georgeanelson.com/>