Naaaaah, the runlevel is there - the script is there when you run the script it fails. It seems the issue has been fixed after running the upgrade in RHN. > On Fri, 2002-11-22 at 06:30, David Durst wrote: >> Won't start up >> > On Thu, 21 Nov 2002 20:49:27 -0800 (PST) >> > David Durst <ddurst@larubber.com> wrote: >> > # What is the fix for postgres? >> > Or more importantly, what is the problem with postgres? >> > -- >> > Jesse Keating > > Hi, > > Maybe postgresql is not set to startup on your run level. > You can see what is your default run level with: > > # grep default: /etc/inittab > id:3:initdefault: > > In the above case, 3 is the default run level. > > Now, what is the status of PostgreSQL? > > # /sbin/chkconfig --list postgresql > postgresql 0:off 1:off 2:off 3:off 4:off 5:off 6:off > > > In this case, it is off in all run levels!!! Maybe that's your case too. > > To make it startup on run level 3 (the default in this example), you > must do: > > # /sbin/chkconfig --level 3 postgresql on > > And now, you will see: > > # /sbin/chkconfig --list postgresql > postgresql 0:off 1:off 2:off 3:on 4:off 5:off 6:off > > Now, so you don't need to reboot just to get PostgreSQL, do: > > # service postgresql start > > Happy hacking... > > Rui > > See also: man chkconfig, man grep, /sbin/service --help, man inittab > > -- > + No matter how much you do, you never do enough -- unknown > + Whatever you do will be insignificant, > | but it is very important that you do it -- Gandhi > + So let's do it...? -- Psyche-list mailing list Psyche-list@redhat.com https://listman.redhat.com/mailman/listinfo/psyche-list
