Bug 56820 - apmd default kills NIS logins
Summary: apmd default kills NIS logins
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: apmd
Version: 7.2
Hardware: i386
OS: Linux
low
medium
Target Milestone: ---
Assignee: Bernhard Rosenkraenzer
QA Contact: Aaron Brown
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-11-28 09:10 UTC by Andrew Gormanly
Modified: 2007-03-27 03:50 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2002-01-24 23:00:29 UTC


Attachments (Terms of Use)

Description Andrew Gormanly 2001-11-28 09:10:32 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.9-12 i686)

Description of problem:
apmd is enabled by default, and set to shutdown the network after 10
minutes idle.  This logs out users with NIS accounts and automounted home
directories, which seems to be a bad thing for a default set up.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. ypbind at installation time
2. log in with an NIS account
3. wait 10 minutes.
	

Actual Results:  Screen is blank.  On pressing a key see gdm, not user's
work.

Expected Results:  Power saving to not log users out as default setting.

Additional info:

I think the system defaults should not be set in ways which break very
common configurations (i.e. NFS & NIS clusters).  NET_RESTART="yes" can be
very useful I guess, but it can cause pain too.  Default settings should
IMHO be quite conservative + not risk breaking things...

Comment 1 Bernhard Rosenkraenzer 2002-02-26 17:56:36 UTC
 We don't default to shutting down after 10 minutes of idle time. That may be something 
your BIOS does. 
 
NET_RESTART is set to yes by default because that's the more conservative and less risky 
setting - quite a few (from my own experience, I'd say 90%) of all notebook network 
chipsets and PCMCIA network cards don't work after a resume unless they're restarted. 
 
Furthermore, NET_RESTART=no in combiniation with dhcp is a major problem (you can't expect 
to keep the IP over a suspend/resume cycle, so you need to restart the network in this 
case, as well). 
 
Because of these things, I think our current default settings are correct. 



Note You need to log in before you can comment on or make changes to this bug.