Re: [ADMIN] postgres at reboot

Hi Scott,

When I issue: /sbin/chkconfig --list | grep postgres
it comes back with:

 postgresql_ORG  0:off   1:off   2:off   3:off   4:off   5:off   6:off
 postgresql      0:off   1:off   2:on    3:on    4:on    5:on    6:off

I felt a bit strange that it says 'off' at run level 6.
I went into /etc/rc.d and issued:
 sudo find . -name \*postgresql\* -ls | grep S98postgresql
and it came back with:

 15618186    0 lrwxrwxrwx   1 root     root           20 Aug 21 17:00 ./rc4.d/S98postgresql -> ../init.d/postgresql
 15618294    0 lrwxrwxrwx   1 root     root           20 Aug 21 17:00 ./rc3.d/S98postgresql -> ../init.d/postgresql
 15618351    0 lrwxrwxrwx   1 root     root           20 Aug 21 17:00 ./rc2.d/S98postgresql -> ../init.d/postgresql
 15618024    0 lrwxrwxrwx   1 root     root           20 Aug 21 17:00 ./rc5.d/S98postgresql -> ../init.d/postgresql

Next, I went into /etc/rc.d/rc6.d and typed:
 ls -l
and it gave me this:
     .       .  .    .      .  .   .   .         .              .        .
     .       .  .    .      .  .   .   .         .              .        .
lrwxrwxrwx   1 root root   20 Aug 21 17:00 S98postgresq -> ../init.d/postgresql

There is an 'l' missing from the name!  I thought for a moment
I found the culprit, but then I issued the command below:
 /sbin/chkconfig --list | grep '6:on'
and it returned nothing.

I am a bit confused.  As I understand, run level 6 means, in
redhat context, shutdown and reboot.  But it seems in my case
nothing is turned on for level 6.  Then that missing 'l'
is really of no significance?

Any thoughts?  Clues?

Regards,

Tena Sakai
tsakai@gallo.ucsf.edu



-----Original Message-----
From: Scott Marlowe [mailto:scott.marlowe@gmail.com]
Sent: Thu 9/25/2008 12:46 PM
To: Tena Sakai
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] postgres at reboot

On Thu, Sep 25, 2008 at 1:42 PM, Tena Sakai <tsakai@gallo.ucsf.edu> wrote:
> Hi Everybody,
>
> About 1.5 month ago, my machine (which runs redhat linux
> 2.6.9-78.0.1.ELsmp on Dell hardware with postgres 8.3.3)
> had a terrible crash.  I am mostly recovered, but there
> is at least one more thing that's not right.
>
> Namely, when the machine gets rebooted, postgres doesn't
> start automatically.  Before the crash, there was no such
> problem.

In RH, you use chkconfig to see what's set to start:

chkconfig --list

will show you all the services and what run levels they come up in.

chkconfig servicename on|off -- will turn a service on or off at boot.

service servicename start -- will start a service.