05-06-2006
The problem is: on a busy system the pid may possibly be another process. You would in trouble if that process were a process you owned. So, try to keep the sleep value reasonably close to what your process actually needs to complete its job.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am currently running SCO OpenServer.
When the machine is restart it automatically intitiates processes that allow me to use the ARCserv backup software... Recently, these process were killed and I would like to restart them. The problem is I dont know the name or location of the files invoked... (1 Reply)
Discussion started by: LowOrderBit
1 Replies
2. HP-UX
How can I kick a user out after being idle for a certain amount of time, would prefer not to use scripts, will TMOUT work on HP-UX? (5 Replies)
Discussion started by: csaunders
5 Replies
3. Solaris
Hello everyone
I am a new one,I want to know how to get the solaris force the loginer out if he do not in a time
thanks (4 Replies)
Discussion started by: lyh003473
4 Replies
4. UNIX for Advanced & Expert Users
Is there a way to monitor certain processes and if they hang too long to kill them, but certain scripts which are expected to take a long time to let them go?
Thank you
Richard (4 Replies)
Discussion started by: ukndoit
4 Replies
5. Red Hat
I have a RHEL 2.1 machine that I am trying to get to mount a remote nfs filesystem. Both servers have 2 network interfaces. My linux machine can mount the filesystem through one interface with no problems but if I switch over and try to mount it through the other interface using a totally... (1 Reply)
Discussion started by: darren.wyatt
1 Replies
6. Solaris
Hi
Is there an easy way to identify and group currently running processes into OS processes and APP processes. Not all applications are installed as packages.
Any free tools or scripts to do this?
Many thanks. (2 Replies)
Discussion started by: wilsonee
2 Replies
7. SCO
Hello - We have setup printers to startup in the /etc/rc.d/8 directory and when the SCO system is booted this script should kick them off or start them up but it doesn't. So I have to start it from root and leave the window open. I know this isn't right and trying to figure out what's missing. ... (13 Replies)
Discussion started by: dbm7230
13 Replies
8. AIX
Hello,
I'm having a problem starting the cron daemon automatically from inittab, let me provide the details below:
We are having five equally installed machines. One of them was upgraded in the past, one we upgraded recently, both from 5300-05-06 to 5300-07-01-0748. On the upgraded... (6 Replies)
Discussion started by: hybr1d
6 Replies
9. Shell Programming and Scripting
I had issues with processes locking up. This script checks for processes and kills them if they are older than a certain time.
Its uses some functions you'll need to define or remove, like slog() which I use for logging, and is_running() which checks if this script is already running so you can... (0 Replies)
Discussion started by: sukerman
0 Replies
10. UNIX for Dummies Questions & Answers
e.g.
File name: File.txt
cat File.txt
Result:
#INBOUND_QUEUE=FAQ1
INBOUND_QUEUE=FAQ2
I want to get the value for one which is not commented out.
Thanks, (3 Replies)
Discussion started by: Tanu
3 Replies
LOCK(1) BSD General Commands Manual LOCK(1)
NAME
lock -- reserve a terminal
SYNOPSIS
lock [-npv] [-t timeout]
DESCRIPTION
The lock utility requests a password from the user, reads it again for verification and then will normally not relinquish the terminal until
the password is repeated. There are two other conditions under which it will terminate: it will timeout after some interval of time and it
may be killed by someone with the appropriate permission.
The following options are available:
-n Do not use a timeout value. Terminal will be locked forever.
-p A password is not requested, instead the user's current login password is used.
-t timeout
The time limit (default 15 minutes) is changed to timeout minutes.
-v Disable switching virtual terminals while this terminal is locked. This option is implemented in a way similar to the -S option of
vidcontrol(1), and thus has the same restrictions. It is only available if the terminal in question is a syscons(4) or vt(4) virtual
terminal.
SEE ALSO
vidcontrol(1), syscons(4), vt(4)
HISTORY
The lock command appeared in 3.0BSD.
BSD
July 10, 2002 BSD