Break from Managment Station

[Ulf Sandberg]

How to send a break from the Superdome Managment station to break a looping init.d process?

[Jeff Schussele]

Hi Ulf,

I don't know of any way other than to login to the system & send some sort of kill command to the PID.
You can try 24 (SIGSTOP) to stop it & that would allow a 26 (SIGCONT) later to restart it. If you want to stop it & not restart try 2 (SIGINT) to interrupt it or a 3 (SIGQUIT) to quit out, but these may be trapped. So you may be forced to do a "normal" 15 (SIGTERM) to terminate it. Only use 9 (SIGKILL) as a kill of last resort.

IF the PID s in HP-UX realtime priority range 0 -to-> 127 or POSIX realtime 0 -to-> 32, then you may have to use between 37 (SIGRTMIN) and 44 (SIGRTMAX) to halt them as no other kill would work.

Rgds,
Jeff

[Sundar_7]

Are you referrring to way to interrupt the startup script execution ?

works for me in rp74XX.

[Ulf Sandberg]

Problem is during startup, so I can't login, msg is
"NFS server (pid733@/net) not responding still trying"
and I have to do the break to get the login promt to correct the problem

[Matti_Kurkela]

If the problem is caused by a NFS server not being available (as you later clarified), it depends on the mount options of the NFS mount.

If the NFS mount has the options "hard,nointr", there is no way to break the connection attempt. You must reset the server (or the partition, if your Superdome is partitioned) and re-boot to single-user mode.

If the NFS mount is with default options (hard,intr) it depends on what program has caused the NFS access attempt and how it behaves. If the program has already disconnected from the console (preparing to daemonize itself), you'd need a login... which you don't have. Again a reset and reboot to single-user mode is needed.

If the program still receives input from the console, the keyboard interrupt might still work. However, the keyboard interrupt character might not be the usual Ctrl-C: since at this point there has been no getty on the console yet, it is possible that the interrupt character is still set as the "factory default" for all tty devices... which seems to be "@" on HP-UX. (This is a holdover from the age of printing terminals, I guess.)

When your immediate problem is solved, remember to modify the startup script of the program that caused the NFS access so that the server can complete the boot even if NFS is not available. Without knowing more from your setup, I can't give any specific help in that.