RE: Anyone have problems with shutdown not working properly?

On Fri, 14 Mar 2003, Shaw, Michael D wrote:

> I have use either:
> 
> shutdown -r now
> 
> or
> 
> /sbin/shutdown -r now

Should be fine.

> I tried switching vc's when the shutdown was happening but no luck.  Next
> time I was going to try the shutdown using our KVM switch and then unhook it
> and attach a regular monitor and keyboard and see what happens.  I'm
> trhinking like you say I'm just not looking at the "right" console when the
> shutdown happens.  BTW, my grub.conf is:

Switching VC's will not help if the issue is a serial term, BUT ..

> #
> # Note that you do not have to rerun grub after making changes to this file
> # NOTICE:  You have a /boot partition.  This means that
> #          all kernel and initrd paths are relative to /boot/, eg.
> #          root (hd0,0)
> #          kernel /vmlinuz-version ro root=/dev/ida/c0d0p6
> #          initrd /initrd-version.img
> #boot=/dev/ida/c0d0
> default=1
> timeout=10
> splashimage=(hd0,0)/grub/splash.xpm.gz
> title Red Hat Linux (2.4.7-10enterprise)
>         root (hd0,0)
>         kernel /vmlinuz-2.4.7-10enterprise ro root=/dev/ida/c0d0p6
>         initrd /initrd-2.4.7-10enterprise.img
> title Red Hat Linux (2.4.7-10smp)
>         root (hd0,0)
>         kernel /vmlinuz-2.4.7-10smp ro root=/dev/ida/c0d0p6
>         initrd /initrd-2.4.7-10smp.img
> title Red Hat Linux-up (2.4.7-10)
>         root (hd0,0)
>         kernel /vmlinuz-2.4.7-10 ro root=/dev/ida/c0d0p6
>         initrd /initrd-2.4.7-10.img


No evidence of a serial term so let's forget that path.

> >1)  init 6
> >
> Not yet but will do.
> 
> >OR
> >
> >1) init 1
> >   manually shutdown continuus
> >   init x 
> > 
> We have done:
> manually shutdown continuus
> shutdown -r now

Hmmm, how do you make sure that the users are out of Informix before
you shut it down?

> this of course will shutdown continuus properly although its redundant if
> things are working right.  BTW, does it matter if the script is linked as
> S99/K99 instead of maybe S89/K89 or S90/K90?  I wouldn't think so, but I
> have never had anything linked at x99.

OK, the numbers are just relative.  During startup the scripts are 
executed in numeric order, so S99anything is at the end of the sequence.
Scripts with the same number can be started in any order relative to one 
another.  Moving it to S90anything merely says it will be started after
anything with a number < 90 but before those with numbers >= 91.  Using
this schema is a way to ensure that contigencies are met; i.e., networking
will have a lower number than any specific network service, portmap needs
a lower number than nfs or ypbind which both depend on the portmapper, 
etc.   On shutdown the K scripts are run in numeric order, so again 
dependencies play on which number any script should have relative to
others.


Now to go back to what others have said,  If this is a server there is
no reason to run it at runlevel 5.  Runlevel 5 is the same as 3 EXCEPT
it starts the X-based GUI console.  You do not need/want an X-based
GUI console on a server; just eats memory and CPU cycles.  Plus,
some console messages can be 'lost' (not displayed on the console) due
to the changeover from the graphical to the text console.  Best
advice; change the runlevel to 3 in inittab so that on next reboot
it comes up in rl 3.  Then you will have a snappier machine and you
will see more of what is really happening.

- rick -