> Hannu Koivisto wrote:
>
[snip]
> > the same story: I can use those mounts fine for some time, but
> > then the smbmount that was left on background says it got a
> > signal, tries to get a new socket and then tries to ask password
> > (sometimes I manage to give it, but usually the tty is pretty
> > messed up).
> >
[snip]
>
> Getting the "signal failed" message means that your smbmount process has
> apparently died.
>
[snip]
>
> My guess is that you have your security options require a password, and if
> this fails the smbmount process is terminating. Try changing your mount
> command to include a password, or change the samba options to not require
> one.
>
I get the same kind of messages:
% dmesg
smb_retry: signal failed, error=-3
...
smb_retry: new pid=1621, generation=5
smb_request: result -32, setting invalid
smb_request: result -32, setting invalid
smb_retry: caught signal
Trying to open MFT
smb_retry: caught signal
I include the password on the commandline, and smbmount then tries to
remount with a message:
smbmount: got signal, getting new socket
But for mounts from one machine I get:
smbmount: can't open /smbfs/se-conf
smbmount: exit
It is still mounted, but not accesible:
% mount
...
//BACCHUS/SE-CONF on /smbfs/se-conf type smbfs (0)
...
% ls /smbfs/se-conf
/smbfs/se-conf: Input/output error.
There is no problem unmounting it
% umount /smbfs/se-conf
%
All NTs are NT4+SP3, and I can't see why they should behave
differently ...
Bug, feature, misconfiguration, ...? Is there something smbmount could do
cleaner? Like unmounting if it fails to open the mountpoint?
/Urban, otherwise very happy with:
Linux 2.1.127, samba-1.9.18p10, glibc 2.0.7, mutated RedHat5.0
--- Urban Widmark urban@svenskatest.se Svenska Test AB +46 90 71 71 23
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/