Sponsored Content
Full Discussion: Hung Port
Operating Systems HP-UX Hung Port Post 9405 by Perderabo on Friday 26th of October 2001 08:31:23 AM
Old 10-26-2001
Remember that we are talking HP-UX here. HP's man page for ndd mentions "ndd -h unsupported". If you run:
ndd -h unsupported | grep disco
you will see:

tcp_discon - Terminate a TCP connection
tcp_discon_by_addr - Terminate a TCP connection

I have never had a TCP connection that I want to terminate, so I have never tried them. But I know several people who claim that they do work. Why are you saying that ndd can't do this? Did you guys try these and find that they don't work?
 

10 More Discussions You Might Find Interesting

1. IP Networking

system hung

I installed sco unix v 5.0.5 in the hp server lc 2000 HD size 27gb & ram 256 , used micro focus cobol for unix , aplication system bank , the problem is the system hung 2 or 3 times a day will you pls. give me the solution. thanks talib alsaadi :( (2 Replies)
Discussion started by: talib alsaadi
2 Replies

2. UNIX for Dummies Questions & Answers

SCSI bus is hung

Anyone have any ideas what could be causing me to get the error "The SCSI bus is hung. Perhaps an external device is turned off"? This is occuring when I try to boot off of my external CDROM. I have tried this CDROM on 3 different systems, tried different SCSI cables, and different terminators... (2 Replies)
Discussion started by: saucierm
2 Replies

3. Solaris

SUN is hung/dead

What do you do if the system will not respond to commands? I'm using SUN Fire v210. We had a power hit, so i think it caused a problem. The monitor does not come up anymore. So i plugged in on a laptop via serial port, rebooted. The system seems to start to boot, but comes up to message "SC... (11 Replies)
Discussion started by: ireeneek
11 Replies

4. HP-UX

Server hung

So my server was hung when I came in this morning. It was responding to pings, but the console and telnet sessions would not respond. There was no disk activity. The display said FA1F which I discovered that the "A" represents a high CPU load. I tired several things to get it going but was forced... (6 Replies)
Discussion started by: biznatch
6 Replies

5. Shell Programming and Scripting

Monitoring for a hung process

A coworker has a shell script that runs from a scheduler at the 3am. The shell script runs sqlplus passing in a sql statement, which generate a file. This is done 21 times for 21 different sql statements. Recently, one of the sqlplus processes got hung. Is there a way to monitor how long the... (2 Replies)
Discussion started by: prismtx
2 Replies

6. Programming

Subroutine Hung

Hi friends I am Administrator for a system works with uinx OS but, many times I get messages from server console inform me about Subroutine is Hanging so what can I do to reset this Subroutine? Note: always when I got that I restart the server but I think that is not professional solution. (3 Replies)
Discussion started by: bintaleb
3 Replies

7. HP-UX

ssh session getting hung (smilar to hpux telnet session is getting hung after about 15 minutes)

Our network administrators implemented some sort of check to kill idle sessions and now burden is on us to run some sort of keep alive. Client based keep alive doesn't do a very good job. I have same issue with ssh. Does solution 2 provided above apply for ssh sessions also? (1 Reply)
Discussion started by: yoda9691
1 Replies

8. Solaris

Hung ILOM - e2900

While trying to perform a firmware upgrade on this ilom, the system refused to allow uploading of more than ~900k or so... We tried multiple approaches using FTP and all failed. I decided to start this morning by firing up Apache on another box and trying the same process via HTTP but when I went... (8 Replies)
Discussion started by: DustinT
8 Replies

9. Solaris

How to find port number wwn of particular port on dual port HBA,?

please find the below o/p for your reference bash-3.00# fcinfo hba-port HBA Port WWN: 21000024ff295a34 OS Device Name: /dev/cfg/c2 Manufacturer: QLogic Corp. Model: 375-3356-02 Firmware Version: 05.03.02 FCode/BIOS Version: BIOS: 2.02; fcode: 2.01;... (3 Replies)
Discussion started by: sb200
3 Replies

10. Shell Programming and Scripting

How to check if the process is Hung?

I wish to monitor if my Tomcat process if Running, Hung, or Shutdown. I cannot use any third party monitoring tools so i decided to use one of these to test if the tomcat server is responding or not . 1. nslookup 2. telnet 3. ps The reason I do not use wget / curl is because it will... (2 Replies)
Discussion started by: mohtashims
2 Replies
INIT(8) 						      System Manager's Manual							   INIT(8)

NAME
init - process control initialization SYNOPSIS
/etc/init DESCRIPTION
Init is invoked inside UNIX as the last step in the boot procedure. It normally then runs the automatic reboot sequence as described in reboot(8), and if this succeeds, begins multi-user operation. If the reboot fails, it commences single user operation by giving the super- user a shell on the console. It is possible to pass parameters from the boot program to init so that single user operation is commenced immediately. When such single user operation is terminated by killing the single-user shell (i.e. by hitting ^D), init runs /etc/rc with- out the reboot parameter. This command file performs housekeeping operations such as removing temporary files, mounting file systems, and starting daemons. In multi-user operation, init's role is to create a process for each terminal port on which a user may log in. To begin such operations, it reads the file /etc/ttys and executes a command for each terminal specified in the file. This command will usually be /usr/libexec/getty. Getty opens and initializes the terminal line, reads the user's name and invokes login to log in the user and execute the Shell. Ultimately the Shell will terminate because of an end-of-file either typed explicitly or generated as a result of hanging up. The main path of init, which has been waiting for such an event, wakes up and removes the appropriate entry from the file utmp, which records cur- rent users, and makes an entry in the wtmp, file which maintains a history of logins and logouts. The wtmp entry is made only if a user logged in successfully on the line. Then the appropriate terminal is reopened and getty is reinvoked. Init catches the hangup signal (signal SIGHUP) and interprets it to mean that the file /etc/ttys should be read again. The Shell process on each line which used to be active in ttys but is no longer there is terminated; a new process is created for each added line; lines unchanged in the file are undisturbed. Thus it is possible to drop or add terminal lines without rebooting the system by changing the ttys file and sending a hangup signal to the init process: use `kill -HUP 1.' Init will terminate multi-user operations and resume single-user mode if sent a terminate (TERM) signal, i.e. ``kill -TERM 1''. If there are processes outstanding which are deadlocked (due to hardware or software failure), init will not wait for them all to die (which might take forever), but will time out after 30 seconds and print a warning message. Init will cease creating new getty's and allow the system to slowly die away, if it is sent a terminal stop (TSTP) signal, i.e. ``kill -TSTP 1''. A later hangup will resume full multi-user operations, or a terminate will initiate a single user shell. This hook is used by reboot(8) and halt(8). Init's role is so critical that if it dies, the system will reboot itself automatically. If, at bootstrap time, the init process cannot be located, the system will loop in user mode at location 0x13. DIAGNOSTICS
/usr/libexec/getty gettyargs failing, sleeping. A process being started to service a line is exiting quickly each time it is started. This is often caused by a ringing or noisy terminal line. Init will sleep for 30 seconds, then continue trying to start the process. WARNING: Something is hung (wont die); ps axl advised. A process is hung and could not be killed when the system was shutting down. This is usually caused by a process which is stuck in a device driver due to a persistent device error condition. FILES
/dev/console, /dev/tty*, /var/run/utmp, /usr/adm/wtmp, /etc/ttys, /etc/rc SEE ALSO
login(1), kill(1), sh(1), ttys(5), crash(8), getty(8), rc(8), reboot(8), halt(8), shutdown(8) 4th Berkeley Distribution November 27, 1996 INIT(8)
All times are GMT -4. The time now is 03:29 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy