Ragnar Wisloff wrote:

they have local home directories, but
have a subdirectory which is automatically mounted from the NT
file/print server, allowing them to use the same files under both
Windows and Linux.

This magic is performed using pam_smb for authentication and pam_mount
for the directory mounting.

We do the same thing and it works well for the most part. But the SMB mounts are the weak link in an otherwise excellent solution. Ocasionally StarOffice crashes and the mount point ends up completely hosed.

Unmount (and any other command) fails with : Input/output error
Killing the smb processes, logging the user off, running "fuser" and umounting the file system sometimes works, but every so often, the only way to umount the filesystem and clear the problem is to reboot the entire server.

It's frustrating that the M$$ connection is dragging down the rock solid LTSP solution and giving the impression of instability -- but in order to tightly integrate thin clients and PCs, I'm stuck with using NT file shares (at least for now).

Has anybody else had similar processes with hosed SMB mounts?
--
Carrie Coy
S&S Worldwide
(860) 537-3451 x2357
www.ssww.com





-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net

Reply via email to