Hello --

One of our workstations is running the Fedora Core 2 32-bit distribution, and has two issues.

The first issue has to do with the splash screen, or window, that appears after the user logs into the system, and displays the services that are being loaded for use. The window does not automatically disappear, but requires the user to left click on it in order for it to be removed from the desktop.

The second issue concerns logging out of the workstation. There is a significant delay, approximately two minutes, between the time the user clicks on the Fedora icon on the toolbar and when the logout window appears on-screen.

The common denominator in both issues is the user account being NIS, or domain, as opposed to local. Has anyone seen these situations, and know what can be done to correct them?

Thanks.

Not a direct answer to your question, but have you considered backing up the end-user's important files and planning an upgrade to a supported Fedora?

Fedora Core 2 is fourteen major versions ago.

Hello --

Believe me, I would like nothing more than to go to a latter day version of the Fedora or CentOS distribution. Unfortunately, Fedora Core 2 is what I have to work with in this scenario.

sounds like something might have been "cracked" on this 7 year out of date system
every known and fixed hole is wide open on it ( eol on April 11 2005 )

from a live cd run "rkhunter" and "chrootkit"

or
bit rot ,after 7 years it happens
or
after 7 years of running there is a hardware issue

the fedora 2 files are in this historical archives
you could reinstall it

see the "end of life" section on the "fedoraforum"
http://forums.fedoraforum.org/forumdisplay.php?f=75


as to the two issues
the first i have never seen ? and have no idea as to even how to recreate it

a guess ?????
it almost sounds like a text boot or rescue mode boot
if so add " rhgb quiet" ( without the "" ) to the end of the grub.conf boot line


as to loging out
some service is not dieing there is a 350 sec time out as default but might have been changed to 120


how BIG are the system logs ? 100+gig if they are not rotated after 7 years ......


also check the system services
there is no documentation anymore for 2 ( for 14 yes )
the oldest
http://www.mjmwired.net/resources/mj...-services.html

Hello --

I checked the /var/log directory, and its total size is about sixty, 60, megabytes. I am doubtful that would be the cause of the problem. As far as thes services running on the system are concerned, there are a fair amount of them. What is the easiest way to determine what service(s) is/are taking longer to time out?

Thanks.

read the boot log and massages log
use the fedora 14 services link i posted as a starting point
turn off what is not needed

and get the "higher up's " to install CentOS 6.2 or RHEL6.2

was snort ever installed on the network
fedora 2 has 7 years of unfixed and KNOWN holes