Hi Philippe ,
Sorry to take a while to reply to your post .
I have been doing a bit of fiddling with FC2 to find out what is happening to my system.
From what you have said and from what I have checked out , I seem to have 2 main problems.
1) A network problem
From your suggestions , I decided to try shutting down my client machine first before I shut down the host FC 2 box and this resulted in a clean shutdown without any hanging.
I have also discovered that I can shutdown my FC 2 box while I have the client box running RH 9 without any problems also , but if I try to shut down the FC 2 while I have Windows 98 SE running on the other box , then that's when my FC 2 box hangs on shutdown.
Also , if I stop the samba service before I shutdow the FC 2 box , with Windows 98 running on the other machine then the FC 2 box also shuts down cleanly without any hanging.
So essentially , it's the network setup with the Windows 98 box that is causing all the shutdown problems on the FC 2 box.
The set-up I have is that I have samba running on the FC2 and have set up my other machine with samba when running Windows 98.
I also have the FC 2 box setup with NFS while I am running RH 9 on the other box.
2) A bug in FC2 with SELinux
With the error messages that I have been getting ,
1) Failed to bind key 255 to value 2379
2) KDSKBENT : Invalid argument.
These errors messages both relate to the keyboard , SELinux and to Loadkeys and it is a common occurance with a lot of people.
I did a search on the word KDSKBENT and came up with a whole lot of info about these error messages and there is also a bug report with Bugzilla.
https://bugzilla.redhat.com/bugzilla....cgi?id=125133
So all I have got to do now is to fix the network problem and see if I can find a patch / workaround with the keyboard problem.
Thanks for your interest and replies.