Sponsored Content
Operating Systems SCO Apparent logoff’s due to inactivity. Post 302087137 by gadgetman on Tuesday 29th of August 2006 10:07:33 PM
Old 08-29-2006
Question Apparent logoff’s due to inactivity.

I have run across an issue with the last two Dell Poweredge servers I have attempted to deploy. I seems that when a telnet session sits idle for 5 to 30 minutes (seems random) the session is being closed and users are logged off. If the session has user activity there is no problem staying connected. I know it sounds like an inactivity timer but the odd thing is that this does not happen when connected via a local switch or crossover cable only through a router plus the idle out time is not consistent. VPN or straight telnet have the same result. I have flashed the router twice. Replaced the router. Installed an out board intel pro 100 nic (which is native to SCO). Locked the nic into 100mb fdx & adjusted the mtu from 1500 to 1300 ( per sonicwall tech support). Flown 1500 miles to do a bare metal re-installation of the OS. Replaced the machine. Remove all of the routers from the loop and connected the server direct to the internet. Moved the whole setup to a new facility on a different backbone in a different city. Still the issue remains. The kicker is that if I put a humble Power Edge 1800 non raid system on 5.0.7 MP4 with onboard Intel pro / 1000's it stays connected just fine. Has anyone else seen this odd behavior with this class of server or OS version?

The current configuration is:
Server:
Dell poweredge 2800 raid 5 perc 4/di ( amird )
Dual Procs, 8 gb ram
Dual integrated Intel Pro / 1000 using driver version 5.0.7f
SCO 5.0.7 MP5 (Updated from MP4)

Previous configuration:
Dell poweredge 6800 raid 5 perc 4/di ( amird )
Dual Procs, 8 gb ram
Dual integrated Broadcom BCM57xx / 1000 using driver version 9.4.1
SCO 5.0.7 MP4

Router:
Sonicwall 4060 on OS 3.2 enhanced

Alternate router used in trouble shooting process:
Sonicwall 3060 on OS 3.2 enhanced
 

9 More Discussions You Might Find Interesting

1. AIX

Logoff a user...

Hi... could anyone tell me how to kill a user session on my server with out affecting other user? Bala (6 Replies)
Discussion started by: balaji_prk
6 Replies

2. UNIX for Advanced & Expert Users

User inactivity at OS level

Dear friends, Can anyone let me know how to configure various OS mentioned below to get user ids deactivated automatically if not logged in at all for a period of, say, 45 days? 1. UNIX / Linux / AIX / Tru64 2. It is OK whether the solution is by running OS commands / running scripts written... (1 Reply)
Discussion started by: bache_gowda
1 Replies

3. Solaris

solaris 9 console inactivity timeout

All, I log into Solaris 9 server through a command line at the console and want enable a inactivity timer to log out of the server after 5 minutes. How can it be done? (1 Reply)
Discussion started by: bubba112557
1 Replies

4. Cybersecurity

apparent non randomness in a public pgp key

Hello here is what I've seen inside some public pgp keys. gAIAAAAAAAkBAAAAAAoAAAAFAAoArwFI/gkAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA... (1 Reply)
Discussion started by: morten44
1 Replies

5. Red Hat

inactivity default to 30 days

Hi All, On red hat ent 4. How do I make the inactivity a default to 30 days? What config file I need to modify so that I will not modify /etc/shadow? Thanks for any comment you may add. (1 Reply)
Discussion started by: itik
1 Replies

6. UNIX for Dummies Questions & Answers

lock the console after 5 minutes of inactivity.

How would i force The server console to be locked automatically after 5 minutes ? I want it to happen for X as well as terminal session of the machine. My Linux distribution details. LSB Version: :core-3.1-ia32:core-3.1-noarch:graphics-3.1-ia32:graphics-3.1-noarch Distributor ID:... (11 Replies)
Discussion started by: pinga123
11 Replies

7. Shell Programming and Scripting

Shell exit due to inactivity

I am installing an executable files. It takes around 30 minutes. During this time...the shell pops the msg "due to inactivity shell pops out in 60 seconds. I dont want this to happen. the terminal shouldnt exit at all. Is there any way that it doesnt exit.I am using putty with ksh (7 Replies)
Discussion started by: sriki32
7 Replies

8. AIX

last - find out inactivity

I am on AIX 6.1, and need to find out who has not accessed the system within 1, 2, or 3 months depending upon the filter I specify. The output I need to have is the account name and the last time accessed: i.e. kart Mar 27 05:13 - 05:13 (00:00) Please advise. (5 Replies)
Discussion started by: Daniel Gate
5 Replies

9. Solaris

User inactivity

Simple question: for determining whether the user has exceeded the maximum amount of "inactivity" (as set in the shadow file) what date is the current login being compared to? Is it wtmp data or something? (3 Replies)
Discussion started by: thmnetwork
3 Replies
EM(4)							   BSD Kernel Interfaces Manual 						     EM(4)

NAME
em -- Intel(R) PRO/1000 Gigabit Ethernet adapter driver SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file: device em Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_em_load="YES" DESCRIPTION
The em driver provides support for PCI Gigabit Ethernet adapters based on the Intel 82540, 82541ER, 82541PI, 82542, 82543, 82544, 82545, 82546, 82546EB, 82546GB, 82547, 82571, 81572, 82573, and 82574 Ethernet controller chips. The driver supports Transmit/Receive checksum off- load and Jumbo Frames on all but 82542-based adapters. Furthermore it supports TCP segmentation offload (TSO) on all adapters but those based on the 82543, 82544 and 82547 controller chips. The identification LEDs of the adapters supported by the em driver can be controlled via the led(4) API for localization purposes. For further hardware information, see the README included with the driver. For questions related to hardware requirements, refer to the documentation supplied with your Intel PRO/1000 adapter. All hardware require- ments listed apply to use with FreeBSD. Support for Jumbo Frames is provided via the interface MTU setting. Selecting an MTU larger than 1500 bytes with the ifconfig(8) utility configures the adapter to receive and transmit Jumbo Frames. The maximum MTU size for Jumbo Frames is 16114. This driver version supports VLANs. The em driver supports the following media types: autoselect Enables auto-negotiation for speed and duplex. 10baseT/UTP Sets 10Mbps operation. Use the mediaopt option to select full-duplex mode. 100baseTX Sets 100Mbps operation. Use the mediaopt option to select full-duplex mode. 1000baseSX Sets 1000Mbps operation. Only full-duplex mode is supported at this speed. 1000baseTX Sets 1000Mbps operation. Only full-duplex mode is supported at this speed. The em driver supports the following media options: full-duplex Forces full-duplex operation half-duplex Forces half-duplex operation. Only use mediaopt to set the driver to full-duplex. If mediaopt is not specified, the driver defaults to half-duplex. For more information on configuring this device, see ifconfig(8). HARDWARE
The em driver supports Gigabit Ethernet adapters based on the Intel 82540, 82541ER, 82541PI, 82542, 82543, 82544, 82545, 82546, 82546EB, 82546GB, 82547, 82571, 82572, 82573, and 82574 controller chips: o Intel PRO/1000 CT Network Connection (82547) o Intel PRO/1000 F Server Adapter (82543) o Intel PRO/1000 Gigabit Server Adapter (82542) o Intel PRO/1000 GT Desktop Adapter (82541PI) o Intel PRO/1000 MF Dual Port Server Adapter (82546) o Intel PRO/1000 MF Server Adapter (82545) o Intel PRO/1000 MF Server Adapter (LX) (82545) o Intel PRO/1000 MT Desktop Adapter (82540) o Intel PRO/1000 MT Desktop Adapter (82541) o Intel PRO/1000 MT Dual Port Server Adapter (82546) o Intel PRO/1000 MT Quad Port Server Adapter (82546EB) o Intel PRO/1000 MT Server Adapter (82545) o Intel PRO/1000 PF Dual Port Server Adapter (82571) o Intel PRO/1000 PF Quad Port Server Adapter (82571) o Intel PRO/1000 PF Server Adapter (82572) o Intel PRO/1000 PT Desktop Adapter (82572) o Intel PRO/1000 PT Dual Port Server Adapter (82571) o Intel PRO/1000 PT Quad Port Server Adapter (82571) o Intel PRO/1000 PT Server Adapter (82572) o Intel PRO/1000 T Desktop Adapter (82544) o Intel PRO/1000 T Server Adapter (82543) o Intel PRO/1000 XF Server Adapter (82544) o Intel PRO/1000 XT Server Adapter (82544) LOADER TUNABLES
Tunables can be set at the loader(8) prompt before booting the kernel or stored in loader.conf(5). hw.em.rxd Number of receive descriptors allocated by the driver. The default value is 256. The 82542 and 82543-based adapters can handle up to 256 descriptors, while others can have up to 4096. hw.em.txd Number of transmit descriptors allocated by the driver. The default value is 256. The 82542 and 82543-based adapters can handle up to 256 descriptors, while others can have up to 4096. hw.em.rx_int_delay This value delays the generation of receive interrupts in units of 1.024 microseconds. The default value is 0, since adapters may hang with this feature being enabled. hw.em.rx_abs_int_delay If hw.em.rx_int_delay is non-zero, this tunable limits the maximum delay in which a receive interrupt is generated. hw.em.tx_int_delay This value delays the generation of transmit interrupts in units of 1.024 microseconds. The default value is 64. hw.em.tx_abs_int_delay If hw.em.tx_int_delay is non-zero, this tunable limits the maximum delay in which a transmit interrupt is generated. DIAGNOSTICS
em%d: Unable to allocate bus resource: memory A fatal initialization error has occurred. em%d: Unable to allocate bus resource: interrupt A fatal initialization error has occurred. em%d: watchdog timeout -- resetting The device has stopped responding to the network, or there is a problem with the network connection (cable). SUPPORT
For general information and support, go to the Intel support website at: http://support.intel.com. If an issue is identified with the released source code on the supported kernel with a supported adapter, email the specific information related to the issue to <freebsdnic@mailbox.intel.com>. FILES
/dev/led/em* identification LED device nodes EXAMPLES
Make the identification LED of em0 blink: echo f2 > /dev/led/em0 Turn the identification LED of em0 off again: echo 0 > /dev/led/em0 SEE ALSO
altq(4), arp(4), igb(4), led(4), netintro(4), ng_ether(4), polling(4), vlan(4), ifconfig(8) HISTORY
The em device driver first appeared in FreeBSD 4.4. AUTHORS
The em driver was written by Intel Corporation <freebsdnic@mailbox.intel.com>. BUGS
Hardware-assisted VLAN processing is disabled by default. You can enable it on an em interface using ifconfig(8). BSD
May 14, 2010 BSD
All times are GMT -4. The time now is 02:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy