Sponsored Content
Full Discussion: NVT logins
Top Forums UNIX for Dummies Questions & Answers NVT logins Post 1574 by Neo on Thursday 15th of March 2001 10:26:30 PM
Old 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

Help with logins

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

Logins-logouts

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

Limit logins to 1

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

Last two logins script

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

How to track FTP logins

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

Logging user logins

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

find information about logins

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

User Logins

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

Not able to login Openvas after update NVT

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
RDS-INFO(1)						    BSD General Commands Manual 					       RDS-INFO(1)

NAME
rds-info -- display information from the RDS kernel module SYNOPSIS
rds-info [-v] [-cknrstIT] DESCRIPTION
The rds-info utility presents various sources of information that the RDS kernel module maintains. When run without any optional arguments rds-info will output all the information it knows of. When options are specified then only the information associated with those options is displayed. The options are as follows: -v Requests verbose output. When this option is given, some classes of information will display additional data. -c Display global counters. Each counter increments as its event occurs. The counters may not be reset. The set of supported counters may change over time. CounterName The name of the counter. These names come from the kernel and can change depending on the capability of the kernel module. Value The number of times that the counter has been incremented since the kernel module was loaded. -k Display all the RDS sockets in the system. There will always be one socket listed that is neither bound to nor connected to any addresses because rds-info itself uses an unbound socket to collect information. BoundAddr, BPort The IP address and port that the socket is bound to. 0.0.0.0 0 indicates that the socket has not been bound. ConnAddr, CPort The IP address and port that the socket is connected to. 0.0.0.0 0 indicates that the socket has not been connected. SndBuf, RcvBuf The number of bytes of message payload which can be queued for sending or receiving on the socket, respectively. Inode The number of the inode object associated with the socket. Can be used to locate the process owning a given socket by searching /proc/*/fd for open files referencing a socket with this inode number. -n Display all RDS connections. RDS connections are maintained between nodes by transports. LocalAddr The IP address of this node. For connections that originate and terminate on the same node the local address indicates which address initiated the connection establishment. RemoteAddr The IP address of the remote end of the connection. NextTX The sequence number that will be given to the next message that is sent over the connection. NextRX The sequence number that is expected from the next message to arrive over the connection. Any incoming messages with sequence num- bers less than this will be dropped. Flg Flags which indicate the state of the connection. s A process is currently sending a message down the connection. c The transport is attempting to connect to the remote address. C The connection to the remote host is connected and active. -r, -s, -t Display the messages in the receive, send, or retransmit queues respectively. LocalAddr, LPort The local IP address and port on this node associated with the message. For sent messages this is the source address, for receive messages it is the destination address. RemoteAddr, RPort The remote IP address and port associated with the message. For sent messages this is the destination address, for receive messages it is the source address. Seq The sequence number of the message. Bytes The number of bytes in the message payload. The following information sources are dependent on specific transports which may not always be available. -I Display the IB connections which the IB transport is using to provide RDS connections. LocalAddr The local IP address of this connection. RemoteAddr The remote IP address of this connection. LocalDev The local IB Global Identifier, printed in IPv6 address syntax. RemoteDev The remote IB Global Identifier, printed in IPv6 address syntax. If verbose output is requested, per-connection settings such as the maximum number of send and receive work requests will be dis- played in addition. -T Display the TCP sockets which the TCP transport is using to provide RDS connections. LocalAddr, LPort The local IP address and port of this socket. RemoteAddr, RPort The remote IP address and port that this socket is connected to. HdrRemain The number of bytes that must be read off the socket to complete the next full RDS header. DataRemain The number of bytes that must be read off the socket to complete the data payload of the message which is being received. SentNxt The TCP sequence number of the first byte of the last message that we sent down the connection. ExpectedUna The TCP sequence number of the byte past the last byte of the last message that we sent down the connection. When we see that the remote side has acked up to this byte then we know that the remote side has received all our RDS messages. SeenUna The TCP sequence number of the byte past the last byte which has been acked by the remote host. BSD
October 30, 2006 BSD
All times are GMT -4. The time now is 03:49 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy