I had been doing some work recently with trying to set up a time-limit for ssh connections. I wanted sessions to automatically disconnect if there was no activity for 20 minutes. I can't even begin to think what would stay connected for 40 hours. I look at the logwatch reports every day and haven't seen anything that would lead me to believe this was a person connecting. But then, I'm probably overlooking something. I'll keep researching. Thanks, Tom, for the response. Kelley C (am I sinning by top-posting?) -----Original Message----- From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Tom Callahan Sent: Monday, February 06, 2006 10:46 AM Maybe has to do with SELINUX and password age requirements? Thanks, Tom Callahan Coleman, Kelley (HAC) wrote: >userhelper[32200]: pam_timestamp: timestamp file >`/var/run/sudo/oracle/unknown:root' has unacceptable age (143385 >seconds), disallowing access to system-config-users for UID 500 > >userhelper[32200]: pam_timestamp: updated timestamp file >`/var/run/sudo/oracle/unknown:root' > >userhelper[32208]: running >'/usr/share/system-config-users/system-config-users' with root >privileges on behalf of 'oracle' > >I'm particularly curious about the 'unacceptable age' part. I do often >su to root from oracle, but I don't understand where the 143385 seconds >comes from. It works out to like 40 hours. I'm not aware of any >continuous connection I would have that would be open that long. And >actually, now I see it says 'sudo', which I never use interactively. >Maybe it's an internal Oracle thing? Any thoughts? > >Kelley Coleman >Database Administrator -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
