On Wed, 22 Sep 1999 [EMAIL PROTECTED] wrote:
> I am currently working on a similar problem. Setting up a system where the
> apache acesses an SMB share as DocumentRoot I came to the point that the
> corrosponding NT-machine wasn't booted up and the automounter tried to
> mount it wich resulted in an error. After booting up the NT-machine it's
> share couldn't be mounted anymore, because the mount-point was alreayd
> mounted to an unresolved SMB share.
I think this could be a smbmount/smbfs error and not necessarily autofs
related. Do this to a machine that isn't running a smb sever:
cola:~#smbmount '//cola/tmp/' /smbfs -N
Added interface ip=192.168.21.123 bcast=192.168.21.255 nmask=255.255.255.0
error connecting to 192.168.21.123:139 (Connection refused)
Connection to cola failed
smbmount: login failed
Could not umount /smbfs: Device or resource busy
smbmount: exit
cola:~#mount
...
//cola/tmp/ on /smbfs type smbfs (0)
cola:~#d /smbfs
ls: /smbfs: Input/output error
That was from samba 2.0.5-pre1 (which happened to be lying around), 2.0.4
does not do that to me. Oh wait, the 2.0.5 test is on a 2.2.12 kernel,
the 2.0.4 is on a 2.3.18 so that could also make a difference. Or simply a
bug in pre1 that was fixed in 2.0.5.
I would try a different samba version if I were you, and if that works
report it to the maintainer. smbmount was changed a lot for 2.0.5.
(You asked a lot about various script ideas. Can't help you much there,
but a good advice when reporting problems is to tell which version you
have of everyhting relevant ... I did miss the beginning of this thread
so apologies if you already did).
/Urban
