03-31-2003
default time in Solaris 8 for time-wait
Ok, heres the situation. We use Solaris 8 and sometimes users who are logged into our system restart their pc's without shutting down the application that attached to our unix backend. I netstat and I get time-waits for the users.
My question is how long before the time-wait ends and the user can log back in?
10 More Discussions You Might Find Interesting
1. Solaris
What is the time_wait interval for Solaris 8/9??? and is it configurable???
For example sometimes a clients pc will freeze up dropping the connection, closing the port. The problem is on our side our system still thinks their logged in (until it realizes it dropped on the otherside and drops on... (1 Reply)
Discussion started by: eloquent99
1 Replies
2. Solaris
Hi all,
I am trying to find out the process wait time on Unix(AIX/SOLARIS) machine( only sh/ksh/csh):
Like
EXAMPLE 1 :
$ vmstat 2
System configuration: lcpu=16 mem=32000MB
kthr memory page faults cpu
----- -----------... (1 Reply)
Discussion started by: chandrakala.sg
1 Replies
3. Shell Programming and Scripting
Hi guys,
I know that this topic has been discuss numerous times, and I have search the net and this forum for it.
However, non able to address the problem I faced so far.
I am on Solaris Platform and unable to install additional packages like the GNU date and gawk to make use of their... (5 Replies)
Discussion started by: DrivesMeCrazy
5 Replies
4. Shell Programming and Scripting
I'm a novice at unix and need it more and more to do my work.
I seem running into problems getting this script "attempt" to work:
I need to copy all files in a directory, which is containing 22000 files, into a directory one level up. There a tool monitors the content of the dir and processes... (2 Replies)
Discussion started by: compasscard
2 Replies
5. Shell Programming and Scripting
Hi,
Is there any easy way to convert date time(stored in shell variable ) to epoch time in solaris box? As +%s is working on linux but not on solaris, also -d option is not working.
Any suggestion please? (6 Replies)
Discussion started by: anshuman0507
6 Replies
6. Shell Programming and Scripting
Hello everyone.
I'm trying to create a script that waits a given amount of time unless a given key is pressed. I found a very useful thread here
https://www.unix.com/shell-programming-scripting/59605-trap-key-press-script.html
however, I cannot figure out a way of avoiding the keypress if the... (2 Replies)
Discussion started by: cue
2 Replies
7. Solaris
I have a cluster of two Solaris server (veritas cluster). one working and the other is standby
I am going to change the date on them , and am looking for a secure solution as it is giving an important service.
my opinion is that the active one doesn't need to be restarted (if I don't change the... (1 Reply)
Discussion started by: barry1946
1 Replies
8. AIX
Hi,
I can't seem to make sense of this. My wait time is showing really high but vmstat's and topas are showing normal usage.
ps aux
USER PID %CPU %MEM SZ RSS TTY STAT STIME TIME COMMAND
root 9961810 5680.7 0.0 448 384 - A Dec 16 6703072:12 wait
... (2 Replies)
Discussion started by: techy1
2 Replies
9. Shell Programming and Scripting
Hi All,
I have the requirement that ,i have to write a shell script that job has to wait for a 7 touch files created by another application for 4 hours, if i get all 7 touch files ,i have to send a mail that i jobs are completed, if if it is waiting for more than 4 hours i have to send a mail... (2 Replies)
Discussion started by: Pradeep Shetty
2 Replies
10. UNIX for Dummies Questions & Answers
I want to create a script which calls another script with certain interval.
Script "A" should call script "B" every 60 seconds.
Script "A" should also be able to call other scripts such as "C", "D", etc. at an interval of 60, 120, 180 seconds respectively.
Basically script A should take two... (1 Reply)
Discussion started by: Vee
1 Replies
LEARN ABOUT FREEBSD
poweroff
SHUTDOWN(8) BSD System Manager's Manual SHUTDOWN(8)
NAME
shutdown, poweroff -- close down the system at a given time
SYNOPSIS
shutdown [-] [-h | -p | -r | -k] [-o [-n]] time [warning-message ...]
poweroff
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.
-p The system is halted and the power is turned off (hardware support required) at the specified time.
-r The system is rebooted 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).
-o If one of the -h, -p or -r options are specified, shutdown will execute halt(8) or reboot(8) instead of sending a signal to init(8).
-n If the -o option is specified, prevent the file system cache from being flushed by passing -n to halt(8) or reboot(8). This option
should probably not be used.
time Time is the time at which shutdown will bring the system down and may be the case-insensitive word now (indicating an immediate shut-
down) or a future time in one of two formats: +number, or yymmddhhmm, where the year, month, and day may be defaulted to the current
system values. The first form brings the system down in number minutes and the second at the absolute time specified. +number may
be specified in units other than minutes by appending the corresponding suffix: ``s'', ``sec'', ``m'', ``min''. ``h'', ``hour''.
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. Five minutes before shutdown, or immediately if shutdown is in less than 5 minutes, logins are dis-
abled by creating /var/run/nologin and copying the warning message there. If this file exists when a user attempts to log in, login(1)
prints its contents and exits. The file is removed just before shutdown exits.
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. The corresponding signal is then sent to init(8) to respectively halt, reboot or bring the system down to single-user state (depending
on the above options). The time of the shutdown and the warning message are placed in /var/run/nologin and should be used to inform the
users about when the system will be back up and why it is going down (or anything else).
A scheduled shutdown can be canceled by killing the shutdown process (a SIGTERM should suffice). The /var/run/nologin file that shutdown
created will be removed automatically.
When run without options, the shutdown utility will place the system into single user mode at the time specified.
Calling ``poweroff'' is equivalent to running:
shutdown -p now
FILES
/var/run/nologin tells login(1) not to let anyone log in
EXAMPLES
Reboot the system in 30 minutes and display a warning message on the terminals of all users currently logged in:
# shutdown -r +30 "System will reboot"
COMPATIBILITY
The hours and minutes in the second time format may be separated by a colon (``:'') for backward compatibility.
SEE ALSO
kill(1), login(1), wall(1), nologin(5), halt(8), init(8), reboot(8)
HISTORY
The shutdown utility appeared in 4.0BSD.
BSD
December 15, 2014 BSD