My condolances on your loss.
As for Samba, I've had a different but similar problem, if I'm reading your message correctly, and although I can't say why it happened, or how to fix it, perhaps I can still help a bit with a work around. Our Samba install originally would not seem to log people out if they just shut down their PCs. So Samba would hold open connections, including their roaming profiles, which meant that they recieved errors during logins. What I ended up doing was restarting Samba to resolve it, but this sucked because it killed ALL samba connections. I quickly became a fan of smbstatus. smbstatus will show you all of the smb connections a particular PC has with the Linux box, including quite a bit of detail. You can narrow it down using the -u switch which will allow you to see just an individual username. If this is your problem (per user, rather than per server), as it was for me, then you can see the pid for a person's connection, and kill JUST THAT ONE pid rather than all of Samba. The user will then be able to sign in normally. It's not really a solution, because I don't exactly know why the problem occurred, but hopefully it's a start towards finding a solution, or at least a decient workaround... There is a Global variable available in SMB.CONF to automatically disconnect dead connections (deadtime, I believe). I know about it but I'm not using it, because I worry about it screwing up MS Access databases, PST files and other open files when it just drops the connections if people leave their machines on overnight. Better to have data integrity with a slight administrative increase, then unreliable data. Like I said, this hasn't happened to me in months, so I assumed it was just some first day screwiness, and haven't given it any thought since then. Kev. ----- Original Message ----- From: "Trevor Lauder" <[EMAIL PROTECTED]> To: "CLUG" <[EMAIL PROTECTED]> Sent: Tuesday, October 08, 2002 11:19 AM Subject: Samba > First off, I would like to apologize for missing the last meeting and ignoring the > list for this past week and a bit. Our second child, a little girl was stillborn > on October 1st and I have been busy planning the funeral, and spending time with my > wife. I only started work up yesterday, I've been off since the 1st. > > Anyways, I've been having an issue with one of the servers I admin. Samba needs to > be restarted once in a while or it won't allow anyone to log into the domain, > however people already logged in work just fine. I think this problem has to do > with the motherboard chipset (It's VIA, yes I know VIA is crap but this is the > hardware I was given to work with :( The server was throwing DMA errors which I > couldn't fix without disabling DMA on the harddrives. I had a feeling that DMA was > causing file system corruption so I disabled DMA and reinstalled Samba. The > problem seemed to have gone away for a bit but it's happening again. Besides > having to restart samba to allow people to log in, Samba also shares out / as > whatever user is set as the guest account in samba. So anyone can go > to file://servername/nobody and browse the root of the server. This for lack of a > better word is annoying. I've already tried all the obvious things to fix it and > probably most of the not so obvious things. I have about 25 linux servers out > there, about half of them running Samba with the exact same basic config and I've > never had this problem. I was just wondering if anyone else has seen this type of > issue before? It's an AMD processor with a VIA chipset, I think it's the VIA > chipset that is the problem here because I can use the exact same config files for > samba on a Intel processor using a SiS or Intel chipset and it works just fine. > Any ideas? > > Thanks, > > Trevor > > >
