02-24-2004
TMOUT is working with HP-UX (ksh and POSIX) .
you just need to set it in the user profile
TMOUT=90 (for example).
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
How do i increase the timeout period of a telnet session? (4 Replies)
Discussion started by: Nadeem Mistry
4 Replies
2. 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
3. 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
4. UNIX for Advanced & Expert Users
Hello,
I was wondering is there a way for SCP to shorten the timeout to fail when it attempts to connect a host that is down. Seems like it takes about a minute or so for scp to timeout. This is on a AIX 5.3 box.
I saw someone suggest use -o ConnectTimeout but the scp I use doesn't have that... (1 Reply)
Discussion started by: benefactr
1 Replies
5. Shell Programming and Scripting
Hi All,
I want to know whether we can timeout the cd command in unix.
If we can how is it implemented?
Suppose cd command hangs can we timeout the command.
Please help (9 Replies)
Discussion started by: dipashre
9 Replies
6. Shell Programming and Scripting
When I run a script where the 1st parameter is ip address
ftp -n -i -v $1
I hang here if the ip is wrong
how to set a timeout something like
if (20s not complete "ftp -n -i -v $1") then
echo "error"
fi
Thanks a lot. (14 Replies)
Discussion started by: uativan
14 Replies
7. Programming
I want to write a small application using Libpcap in C on Linux.
Currently, it starts to sniff and waits for the packets. But that's not what I need actually. I want it to wait for N seconds and then stop listening. (I think there's something wrong with my usage of 'pcap_open_live'...)
How... (0 Replies)
Discussion started by: xyzt
0 Replies
8. Shell Programming and Scripting
Hi
I'm writing a script which based on a condition, restarts a set of servers. The problem I'm facing is, say if one of the server is down, my script stops there and fails to proceed. How can I ensure to set a timeout value on that script, so when the server is not reachable, the script should... (2 Replies)
Discussion started by: mathbalaji
2 Replies
9. Shell Programming and Scripting
Hello,
I'm doing a simple script with expect (a telnet which works without user/pass), and I want to put a condition if timeout happens, then to print a message, but it doesn't work. The script looks like below:
#!/usr/bin/expect
log_user 0
set timeout 10
spawn telnet IP PORT
send... (3 Replies)
Discussion started by: rainbow19
3 Replies
10. Shell Programming and Scripting
I saw several thread for this issue but none addresses my issue.
I have tried read -t but the result is read bad options
My requirement is
1. Ask for input
2. If input = y or no input in 60 seconds
then continue processing
else
exit
fi
Kindly consider this urgent. (8 Replies)
Discussion started by: rprasad
8 Replies
LEARN ABOUT HPUX
xtappaddworkproc
XtAppAddWorkProc() XtAppAddWorkProc()
XtAppAddWorkProc - register a procedure to be called when the event loop is idle.
Synopsis
XtWorkProcId XtAppAddWorkProc(app_context, proc, client_data)
XtAppContext app_context;
XtWorkProc proc;
XtPointer client_data;
Inputs
app_context
Specifies the application context.
proc Specifies the procedure that is to be called when the application is idle.
client_data
Specifies data to be passed to proc when it is called.
Returns
A handle of type XtWorkProcId that can be passed to XtRemoveWorkProc() to unregister the work procedure.
Description
XtAddWorkProc() registers the procedure proc and the data client_data to be called by XtAppNextEvent() or XtAppProcessEvent() when there
are no pending input events and it would otherwise block. Multiple work procedures can be registered, and the most recently added one is
always the one that is called. However, if a work procedure itself adds another work procedure, the newly added one has lower priority
than the current one.
A work procedure returns a Boolean. If it returns True, it will automatically be unregistered and will not be called again. If it returns
False it will be called the next time the application is idle. See XtWorkProc(2) for more information.
Usage
XtAppAddWorkProc() implements a limited form of background processing. Most applications spend most of their time waiting for input; to do
useful work during this idle time, you can register a work procedure that will run when the application is idle.
A work procedure must return quickly or the application will not be able to promptly respond to user events. If a large task needs to be
done in the background, the work procedure should periodically save its state and return False. Work procedures should not be used to do
frivolous work in the background. In a multi-tasking system, an idle application should generally actually be idle, and not steal CPU time
from other processes.
A work procedure can be explicitly removed by calling XtRemoveWorkProc() with the XtWorkProcId returned by this function.
Structures
The XtWorkProcId type is defined as follows:
typedef unsigned long XtWorkProcId;
See Also
XtAppNextEvent(1), XtAppProcessEvent(1), XtRemoveWorkProc(1),
XtWorkProc(2).
Xt - Event Handling XtAppAddWorkProc()