Regarding Samba and Winbind again: I've killed my server. While copying some files to a mapped network drive from a Windows 2000 Pro client to a Mandrake server, using the Windows Explorer, I received the notice that the drive was no longer available. The mapped drives were no longer accessible, and my X session on the console was non-responsive.
After killing the X server, it hung at the Waiting for X server to shutdown note. Normally, this is a split second process. I tried alt-X, to no avail. Alt-Z stopped the process, and returned me to the shell, but after issuing a 'ps', nothing happened. I attempted to login to the second console (using alt-F2). Everything looked okay, but I was never given a password prompt after typing the logon name. The syslog info on terminal 12 never displayed any data as to what might have happened. Can anyone suggest some ways to diagnose what went wrong? It appears that I'll have to force a reboot, but I really hate to do this due to the problems that causes on Linux boxes. Is anyone familiar with this happening? For some background: Running Mdk 8.2 with the enterprise kernel. The machine is a 1.26Ghz PIII Tualatin with 1 gig of ECC ram. There are two 120 gig HDs, setup in a RAID 1 config with software RAID configured at install time with diskdrake. I'm fairly confident it's software related, as the board is an Intel SAI2, and all the internal components were selected for maximum reliablity, with price not being an issue at all. The problem occurred while running Gnome 1.4 on the console, with a SSH session running on the Win2k box, and I was copying files from one machine to an XFS partition on the server. Regards, Nathan PS: sorry about requesting a 'read' receipt on the previous post about winbind and samba. If nothing else, it should be interesting to see what order email receipts come in, and in what order on a Saturday evening.
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
