pstrcpy( smb_login_passwd );
to
pstrcpy( password, pass );
smb_login_passwd does not appear anywhere else,
so i assume this to be a very safe little hack.
attaching gdb shows that password and got_pass
are both good (when password is entered at Password:
prompt) in the forked smbmount. everything
looks good for it to reconnect properly.
brent waiting-for-NT-to-close-the-socket-so-i-can-see-
if-this-hack-worked verner
[BTW, the reason i was able to reconnect w/o problems
(the 20+hours) is that there was a NULL password.]
Matthew Vanecek wrote:
> pstrcpy( password, pass );
> "Michael H. Warfield" wrote:
> >
> > Matthew Vanecek enscribed thusly:
> > > I upgraded to samba 2.0.3 as suggested, and the kernel still is
> > > returning errors when I try to access the mounted share after a large
> > > amount of times (less than the 20 hours someone reported).
> >
> > > >From the mount/unmount end, I get the following:
> > > root:reliant me2v$ mount | grep WINNT
> > > //WINNT/C$ on /home/me2v/mounts type smbfs (0)
> > > root:reliant me2v$ ls mounts
> > > ls: mounts: Input/output error
> > > root:reliant me2v$ smbumount mounts
> > > Could not open mounts: Input/output error
> > > root:reliant me2v$ umount mounts
> > > root:reliant me2v$
> >
> > > As you see, umount works, but smbumount, I had thought was what normal
> > > users (as opposed to root) were supposed to use. I did all the above
> > > (except the umount) as a normal user, also, with the same results.
> >
> > > >From /var/log/messages:
> > > Mar 25 10:12:18 reliant kernel: smb_retry: signal failed, error=-3
> > > Mar 25 10:12:45 reliant last message repeated 3 times
> >
> > Uh oh... I know this is going to sound condensending but please
> > bear with me and understand that this has happened before (hell, its
> > happened to me before). The "Signal failed, error=-3" is indicative of
> > an earlier version of smbmount that would give all of the symptoms exactly
> > as you have described. That makes me suspicious that you may not have
> > successfully updated the smbmount binary.
> >
>
> Well, I used rpm, and I built the rpm for all my samba 2.x's, heavily
> customizing the spec file of course, to get all the files I needed (like
> smbmount, for instance).
>
> > 1) Double check that you ran configure with the "-with-smbmount"
> > option before building and installing samba. You can check the Makefile
> > in the source directory for a define for "MPROGS". If that define is
> > empty, you didn't build smbmount.
> >
>
> Here is the configure I used:
> ./configure --prefix=%{prefix} --exec-prefix=%{prefix} --libdir=/etc \
> --with-lockdir=/var/lock/samba --with-privatedir=/etc \
> --with-swatdir=%{prefix}/share/swat --with-smbwrapper \
> --with-automount --with-quotas --with-smbmount
>
> > 2) Make sure that you don't have more than one smbmount in your path.
> >
> > "whereis smbmount" will tell you were all the versions are.
> >
> > "which smbmount" will tell you which one got executed.
> >
> > Do an "ls -l" on the smbmount indicated by which and verify that
> > it was updated by your build.
> >
>
> me2v:reliant me2v$ whereis smbmount
> smbmount: /usr/bin/smbmount /usr/bin/smbmount.old /usr/sbin/smbmount
> /usr/man/man8/smbmount.8
> me2v:reliant me2v$ which smbmount
> /usr/sbin/smbmount
> me2v:reliant me2v$ ls -l /usr/sbin/smbmount
> lrwxrwxrwx 1 root root 17 Feb 28 17:30
> /usr/sbin/smbmount -> /usr/bin/smbmount*
>
> As you can see, there is one binary and one softlink for smbmount.
> There was some reason for putting the link in /usr/sbin, but I can't
> quite remember what it was. Some RedHat thing, I'm sure...
>
> > 3) If you are running RedHat, make sure that you applied the
> > RedHat package patches out of "packaging/RedHat/*.patch" before doing
> > the configure and build (Actually, I think the patch to Makefile.in
> > is the only important one. The other one is for smbsh and doesn't
> > affect smbmount).
> >
>
> These are the two patches that get applied:
> Patch: makefile-path.patch
> Patch1: smbw.patch
>
> which are all that come with the package.
>
> Last, but not least, is the version check, of a sort:
> me2v:reliant me2v$ smbmount -v
> smbmount: invalid option -- v
> Usage: smbmount service <password> [-p port] [-d debuglevel] [-l log]
> Version 2.0.3
> -p port connect to the specified port
>
> Well, there *should* be a -v or --version switch!! Not a kernel
> problem, though....
>
> One last thing, to make sure it's not user error: Does it matter where
> you enter the password? i.e., enter it on the command line or wait for
> the Password prompt? For some perverse reason I seem to prefer typing
> my password at the password prompt, because it's not echoed back to the
> screen.
>
> --
> Matthew Vanecek
> Studies in Business Computers at the University of North Texas
> http://www.unt.edu/bcis
> *****************************************************************
> Visit my Website at http://people.unt.edu/~mev0003
> *****************************************************************
> For 93 million miles, there is nothing between the sun and my shadow
> except me. I'm always getting in the way of something...
>
> -
> 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/
-- \ _|_ / GNU \/ | \/ Certified \_|_/ Professional \ / Linux -= rYo =-- 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/