03-15-2001
Clearing the connection status depends on where the state of the connections are maintained. It might be possible that the connection states for these IPX connections are stored in a file? If so, you can just remove the stale files.
If the IPX connection state information is being preserved by a process, which should terminate on idle, but does not; then you can kill the process manually.
So, the trick to solving this puzzle is to do some homework and find out where the IPX connection state information resides. After you discover where the connection state info is managed, then you can decide the best way to clear the state information.
You are correct in observing that all robust implementation of TCP/IP manage state information in the socket structure and TCP does not have these problems. It is interesting that IPX does. Please let us know what you find out.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Could someone please tell me what I would have to do so I can dial in to Solaris through a modem and login?
Thanks in advance.
Jomar (2 Replies)
Discussion started by: crispyco
2 Replies
2. Shell Programming and Scripting
I want a script that checks the logins and logouts in a system.Is there a way to keep the logins and logouts in files and then compare them every e.g. 10 seconds?
for tcsh. (1 Reply)
Discussion started by: aekaramg20
1 Replies
3. AIX
Trying to limit 1 login per account...
Setup:
We have 2 auth logins, one to the AIX (telnet)then into a distribution mgmt software, the users do not have a shell to log into on the AIX itself, so placing a script such as:
active=`who | awk '{printf",%s,\n",$1}' | grep ,$LOGNAME, | wc -l`
... (0 Replies)
Discussion started by: pheusion
0 Replies
4. Shell Programming and Scripting
This is the contents of my file:
donald.duck 12/07/2009 12:07:58
donald.duck 12/07/2009 12:17:36
donald.duck 12/07/2009 12:22:29
donald.duck 12/07/2009 12:26:39
donald.duck 12/07/2009 12:28:01
mickey.mouse 12/07/2009 12:48:49
mickey.mouse 12/07/2009 12:49:33
mickey.mouse 12/07/2009... (3 Replies)
Discussion started by: diallo0024
3 Replies
5. Shell Programming and Scripting
I have put in the "script" command in the .profile of a particular user id that tracks the terminal session when the user id logs in.
But when the user logs on to the server using FTP, how can this be tracked?
Any input will be appreciated. (1 Reply)
Discussion started by: ggayathri
1 Replies
6. AIX
I want to know how I can turn off and turn on login logging. We have a server that appears to have stopped logging user logins. Running the who command shows nothing and the last command shows no logins for a month. The var/adm/wtmp file isn't full and there is plenty of space in the var file... (2 Replies)
Discussion started by: daveisme
2 Replies
7. Shell Programming and Scripting
Hi, all
I want to make a bash script that print all users from a system using last command.
I want to print the number of user's login in the format (descending order):
5 user1 address1
4 user2 address2
I am trying the command
last | awk '{print $1 " " $3}' | sort | uniq
... (9 Replies)
Discussion started by: peter20
9 Replies
8. Solaris
Is the below logins are needed in the machine.....
nuucp , uucp ,smmsp , svctag , listen , webservd , ip ( We are not using printers),
Can you help in these?
Regards,
kumar (3 Replies)
Discussion started by: rajeshkumarvg
3 Replies
9. Cybersecurity
Hello,
Today, i just updated my Openvas server for latest NVT, portsname and scapdata but after that i am not able to login to my openvas instance.
Below command i fired to get this done.
openvas-nvt-sync
openvas-certdata-sync
openvas-portnames-update
openvas-scapdata-sync... (0 Replies)
Discussion started by: sunnysthakur
0 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