Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have installed on my CentOS server postgresql service and another one called netnfork. The 'netnfork' service starts only after postgresql starts.

netnfork init script:

# netnfork init
# chkconfig: 2345 99 15
# description: netnfork

From netnfork's init script you can see that start order is 99.

The postgresql init script:

# postgresql    This is the init script for starting up the PostgreSQL
#               server.
# chkconfig: - 64 36
# description: PostgreSQL database server.

As you can see from the postgresql's init script, the start order is 64. The problem is that there are some times when the netnfork service fails to start due to the fact that postgresql service isn't completely started. I know that from log files.

Do you have any workaround for that issue?

N.B. I also put on netnfork's init script the following line:

# Required-Start: network postgresql-9.1,

but without any results.

share|improve this question
In a pinch, I'd just manage both daemons with Monit. But that's not a clean fix. – ewwhite Nov 2 '12 at 7:48

It looks like your startup service is named postgresql not postgresql-9.1

Try this out in netnfork:

# Required-Start: network postgresql
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.