03-21-2002
10 More Discussions You Might Find Interesting
1. Programming
The scenerio is:
1. A server listens on a port number
2. If the server is down and the Client tries to connect
3. How to set the timeout for the client
Detailed explaination:
In a client server architecture over a TCP/IP, normally the server is started first which waits and listens for the... (1 Reply)
Discussion started by: shilpi_gup
1 Replies
2. Shell Programming and Scripting
Hi all,
I want to set a timeout say 10 sec to shh prompt i.e. if no password is enetered for 10 sec prompt should again come to shell.
How can this be achieved ??
I am using Linux RHEL 5 and Solaris 10.
Pls help.
Thanks in adv.
VIKAS (3 Replies)
Discussion started by: vikas027
3 Replies
3. 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
4. UNIX for Dummies Questions & Answers
I've created a script that checks the health of a piece of equipment out in the field by first establishing that it is pingable, and then parsing
log files to gather information. Today I realized that there are times where the equipment may be pingable, and will not show any
immediate issues in... (1 Reply)
Discussion started by: DeCoTwc
1 Replies
5. Shell Programming and Scripting
SSHing into a machine can take a few seconds, but after I'm in, the commands return quickly. I was wondering if the timeout setting can be changed once I'm logged into the machine. Does anyone know if this can be set on the fly? The problem here is, if I have to set timeout = 10, it'll take 10... (1 Reply)
Discussion started by: mrwatkin
1 Replies
6. AIX
Friends,
Could anyone let me know - how to set the timeout value for ssh session to HMC? My HMC version is -- V7R7.4.0. I'm sure the version doesn't have anything to do with it.
Thanks,
-- Souvik (2 Replies)
Discussion started by: thisissouvik
2 Replies
7. Red Hat
How is it possible to set the screensaver timeout on red hat.
For solaris I understand it is :
for file in /usr/dt/config/*/sys.resources; do
dir=`dirname $file | sed s/usr/etc/`
mkdir -p $dir
echo 'dtsession*saverTimeout: 10' >>$dir/sys.resources
echo 'dtsession*lockTimeout: 10'... (0 Replies)
Discussion started by: alvinoo
0 Replies
8. Shell Programming and Scripting
I have a command to check the status of hostname and port number,
echo > /dev/tcp/hostname/80
echo $?
0
success case
echo > /dev/tcp/hostname/809999
I got the output
-------------------
connection timed out
It took almost 4 minutes to time out,,, how can I set it to 10 seconds?
my... (2 Replies)
Discussion started by: sam@sam
2 Replies
9. Linux
Hello friends,
I work on Linux servers via SSH (putty) and run "screen" to preserve my sessions so I can attach/detach them at anytime I wish without losing the connectivity/process disruption which is working perfectly fine.
As my team members also have root access to those servers, it is... (7 Replies)
Discussion started by: prvnrk
7 Replies
10. AIX
I have to make a command to work when connecting to AIX 7.1 (used by an internal software).
I have a linux server L where the following command is runned ssh -t <aix-server-ip> ls
For a <non-aix-server-ip> the command runs successfully.
For AIX the terminal just gets blocked.
ssh connection... (5 Replies)
Discussion started by: ufo
5 Replies
LEARN ABOUT MOJAVE
shutdown
SHUTDOWN(8) BSD System Manager's Manual SHUTDOWN(8)
NAME
shutdown -- close down the system at a given time
SYNOPSIS
shutdown [-] [-h [-u] | -r | -s | -k] [-o [-n]] time [warning-message ...]
DESCRIPTION
The shutdown utility provides an automated shutdown procedure for super-users to nicely notify users when the system is shutting down, saving
them from system administrators, hackers, and gurus, who would otherwise not bother with such niceties.
The following options are available:
-h The system is halted at the specified time.
-k Kick everybody off. The -k option does not actually halt the system, but leaves the system multi-user with logins disabled (for all
but super-user).
-n If the -o is specified, prevent the file system cache from being flushed by passing -n option to halt(8) or reboot(8). This option
should probably not be used.
-o If -h or -r is specified, shutdown will execute halt(8) or reboot(8) instead of sending a signal to launchd(8).
-r The system is rebooted at the specified time.
-s The system is put to sleep at the specified time.
-u The system is halted up until the point of removing system power, but waits before removing power for 5 minutes so that an external
UPS (uninterruptible power supply) can forcibly remove power. This simulates a dirty shutdown to permit a later automatic power on.
OS X uses this mode automatically with supported UPSs in emergency shutdowns.
time Time is the time at which shutdown will bring the system down and may be the word now (indicating an immediate shutdown) or specify a
future time in one of two formats: +number, or yymmddhhmm, where the year, month, and day may be defaulted to the current system val-
ues. The first form brings the system down in number minutes and the second at the absolute time specified.
warning-message
Any other arguments comprise the warning message that is broadcast to users currently logged into the system.
- If '-' is supplied as an option, the warning message is read from the standard input.
At intervals, becoming more frequent as apocalypse approaches and starting at ten hours before shutdown, warning messages are displayed on
the terminals of all users logged in.
At shutdown time a message is written to the system log, containing the time of shutdown, the person who initiated the shutdown and the rea-
son. Corresponding signal is then sent to launchd(8) to respectively halt, reboot or bring the system down to single-user state (depending
on the above options).
A scheduled shutdown can be canceled by killing the shutdown process (a SIGTERM should suffice).
SIGTERM TO SIGKILL INTERVAL
Upon shutdown, all running processes are sent a SIGTERM followed by a SIGKILL. The SIGKILL will follow the SIGTERM by an intentionally inde-
terminate period of time. Programs are expected to take only enough time to flush all dirty data and exit. Developers are encouraged to
file a bug with the OS vendor, should they encounter an issue with this functionality.
SEE ALSO
kill(1), login(1), wall(1), halt(8), launchd(8), reboot(8)
BACKWARD COMPATIBILITY
The hours and minutes in the second time format may be separated by a colon (``:'') for backward compatibility.
HISTORY
The shutdown utility appeared in 4.0BSD.
BSD
December 11, 1998 BSD