[CS-FSLUG] local lan file sharing

[David Aikema]

If you use autofs as a layer overtop of the smbmounting, then that
should take care of the issues with timeouts (see
http://www.greenfly.org/talks/autofs/autofs.html for details). 
Basically with something mounted with autofs, the underlying
filesystem you wish to access will only be mounted when you need to
access it, and after no one has access the filesystem for a while,
this would be unmounted.

You don't necessarily need to mount the filesystem in everyone's home
directory, you could just go and create a symlink from the user's
directory to it.

I kind of like the web page idea though.

David

On Thu, 27 Jan 2005 11:56:24 -0500, Frank Bax <fbax at sympatico.ca> wrote:
> At the office, a new Kyocera KM-3035 was installed last week - this is a
> fast network printer/fax/copier/scanner all-in-one unit.  There is a
> scan-to-pc option (imagine scanning multiple pages as fast as a
> photocopier) that only works with a Windows client.  It's a small office,
> and security is not a big concern, so yesterday I setup the Windows client
> on a selected workstation to deposit the scans on a samba server
> (OpenBSD).  This allows all windows clients to pick up scanned documents in
> the same place.  I plan to write a script which deletes scans after some
> hard-coded time period (a month or two).  The office has a few Linux
> workstations (Mandrake 9.1).  What's the best way for these Linux
> workstations to access the scanner files deposited on OpenBSD system?  Do I
> access them via the samba share that Windows clients use, or is there
> another alternative?  If you suggest an option, please include some
> pros/cons.  I have done some access to samba shares from Linux/OpenBSD
> before, but it has always been a script that does the mount, some file
> transfers, then unmount.  I've never had a share "open" for extended
> periods.  Tim's recent issues with unmounting a share that got disconnected
> has me cautious about how to proceed.  If a permanent mount point is needed
> it will need to be in every users home directory, because users of these
> Linux machines don't know anything else.