04-01-2003
check your /etc/inittab file for any errors.
to find some errors you can try this:
grep wait /etc/inittab
who -d
you want each result from your grep to have a corisponding line in the who-d output. (note who -d might have some stuff your grep didnt return do not worry about that)
your zombies should be released from memory via the init proc (if i am correct).
i was haveing a prob with a zombie and did some searching on google groups and well that is what i came up with. hope it helps.
edit: also if they dont go away you might just have to reboot. i know its a dirty fix but yes even we have to reboot sometimes.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi, everyone. I tried to install red hat 8.0 on this computer ( CPU: Intel PIII 866, Memory 128 M, HD: 6.4G MATROX, Vedio card: RIVA TNT 16M), but the process always stuck. And the CD-ROM stopped and the light turned of, the HardDrive's light still on. I waited for almost one hour, but nothing... (5 Replies)
Discussion started by: HOUSCOUS
5 Replies
2. UNIX for Dummies Questions & Answers
Hi,
Today, on one of my SCO machines, i was getting the following:
PANIC : exit cannot exec /etc/init (PID1).
I used two floppy boot/root disks to boot from floppy.
I followed the procedures to restore the files:
/usr/lib/libc.so.1 and /etc/init.
When I reached the part of making... (6 Replies)
Discussion started by: BAM
6 Replies
3. UNIX and Linux Applications
Greetings all,
I'm on a solaris 9 system with vnc-4.1.2 installed. I had a connection to a vnc server that suddenly started sapping up cpu cycles - getting up around 13%. I killed the server instance, and now when I try to start a new server, i get the following message:
"vncserver: socket... (0 Replies)
Discussion started by: mike_q
0 Replies
4. HP-UX
Hello.
system fails on reboot this AM.
received message about not possible for kernel to find process that caused crash.
system does memory dump succesfully, then tries to boot again.
looking further at messages during this time, i'm getting 'init died with return value 256'...system panic... (12 Replies)
Discussion started by: mrviking
12 Replies
5. What is on Your Mind?
so my windows xp box has died. trust me, if i didnt game so much id be using solaris or linux but they dont make games for them :( anyway, i've got a really beat up old linux laptop that i'm using now. it runs well it just can't handle most of todays web pages. gmail is awful on this thing!! i wish... (4 Replies)
Discussion started by: pupp
4 Replies
6. Shell Programming and Scripting
Hello all,
I would be happy if any one could help me with a shell script that would determine all the processes running on a Unix server and post a mail if any of the process is not running or aborted.
Thanks in advance
Regards,
pradeep kulkarni.
:mad: (13 Replies)
Discussion started by: pradeepmacha
13 Replies
7. HP-UX
Hi,
I am trying to setup subversion on hpux 11.11, the svnserve process can be started and the repos have been created, but every we connect to the svn via port 3699 the svnserver will died.
how can i troubleshoot this issue? there is not error from the syslog file. (0 Replies)
Discussion started by: robertngo
0 Replies
8. Shell Programming and Scripting
Hi Experts, we do have a shell script for Unix Solaris, which will kill all the process manullay, it used to work in my previous env, but now it is throwing this error.. could some one please help me to resolve it
This is how we execute the script (and this is the requirement) ... (2 Replies)
Discussion started by: jonnyvic
2 Replies
9. What is on Your Mind?
Oh Boy,
Sad News.
My amazing ASUS ROG Swift PG348Q 34" Gaming Monitor has just died.
I'm pretty sure the problem is with the electronic on/off switch, but none-the-less, it's dead.
Purchased on 10 January 2017, the warranty card say it's under 3 year warranty, and I still have the... (10 Replies)
Discussion started by: Neo
10 Replies
LEARN ABOUT HPUX
sem_trywait
sem_wait(2) System Calls Manual sem_wait(2)
NAME
sem_wait, sem_trywait - lock a POSIX semaphore
SYNOPSIS
DESCRIPTION
is used to lock a semaphore. The calling thread will not return from its call to until one of the following events occur: it successfully
obtains a lock on the semaphore; it is interrupted by a signal or an error condition occurs.
is used to lock a semaphore, if it is available. The value of the semaphore sem is checked at some unspecified time during the call. If
the semaphore is available at the time its value is checked, the calling thread will atomically, with respect to the checking of the value,
lock the semaphore. The thread will now own a lock on the semaphore; the call will return successfully. If the semaphore is unavailable
at the time its value is checked, then the call returns -1 with errno set to EAGAIN.
If the specified semaphore referred to by sem is a named semaphore, then this semaphore must have been opened by the calling process with
The calling process must have both read and write permissions on the semaphore to perform these operations. The semaphore will be locked
upon successful return and will stay locked until it is explicitly released by a call to
To use this function, link in the realtime library by specifying on the compiler or linker command line.
EXAMPLES
The following call to will lock the semaphore sem.
The following call to will lock the semaphore sem, if it is available.
RETURN VALUE
A successful call to will return 0 and the calling thread will then own a lock on the semaphore. Otherwise, the call to will return -1
with errno set to the appropriate value of the error condition.
A successful call to will return 0, if the semaphore was available and the calling thread was able to lock the semaphore. Otherwise, the
call to will return -1 with errno set to the appropriate value of the error condition.
ERRORS
and fail and do not perform the requested operation if any of the following conditions are encountered:
[EPERM] The calling process does not have the privileges necessary to lock the semaphore.
[EAGAIN] The semaphore was not available and hence could not be locked by This error condition only occurs in
[EINVAL] The argument sem does not refer to a valid semaphore.
[EINTR] The function was interrupted by a signal
SEE ALSO
sem_post(2), <semaphore.h>.
STANDARDS CONFORMANCE
sem_wait(2)