Very strange, couldn't stat ".": another question...

[Bruce Tenison]

Hi Skip.  Sorry haven't responded sooner.  What I did was found the line
in the source that was generating this code and added the path=%s\n",path
section at (or around) line 414 in source/lib/doscalls.c
For example:  The line read:
    DEBUG(0,("Very strange, couldn't stat \".\"\n"));
and I changed it to:
    DEBUG(0,("Very strange, couldn't stat \".\" path=%s\n",path));

What this told me was that for some reason, samba was trying to stat the
directory /root and /root was not executable (and readable?) by anyone else
but root, so samba couldn't stat it.  Once I changed permissions on that
directory, samba didn't complain anymore.

Bruce


> Bruce:
>
> Posted the following message to the 2 samba newsgroups but did not receive
> any responses:
>
> =======================================================================
> Have 27 Win95 workstations running on Samba 2.0.5a on Red Hat 6 Linux.
>
> Did much testing (with 2 or 3 workstations) before putting server into
> production setting over Thanksgiving weekend and never saw the following
> error, which appears in the samba log files for several workstations which
> run 2 medical vertical market DOS applications (workstations running only
> Win95 apps do not seem to have this error).
>
> All workstations have all MS TCP/IP and MS network client patches that I
> know of applied.
>
> Error follows:
>
> [1999/11/30 10:27:57]  lib/doscalls.c:dos_GetWd(414)
> Very Strange, couldn't stat "."
>
> This error varies in time and date, but appears in the log files
> for several
> workstations, sometimes repeatedly over a short period of time, and then
> again not for hours.
>
> It does not seem to cause any problems, but if anyone knows what it means
> and why, I would appreciate a response.  All other workstations
> not getting
> any weird messages in their respective log files.
>
> ===========================================================
>
> Came to the samba.org archives and searched for "Very strange..."
> and found
> your post from December 1998.  (Your post follows...)
>
> Did you ever figure out what was causing the "Very strange, couldn't stat
> "."  " messages from the Samba clients that you posted to the samba.org
> lists back in December 1998?
>
> I am experiencing this on 5 or 6 workstations out of 27 in a new
> production
> setting.  I did not see any of these during testing with 2 or 3
> workstations
> before putting the server into full use.  I am not having any
> other problems
> and these messages do not seem to affect the workstations adversely.
>
> Thanks
>
> Skip Harrison
> skiph at newportnet.com
> Online Computer Supply
> 152 NE 70th
> Newport, OR  97365
> 541-265-9612
>
>
>
> Posted by Bruce:
> ========================================================
> Very strange, couldn't stat ".": another question...
>
> Should I be concerned about getting the
> [1998/12/18 07:15:07, 0] lib/doscalls.c:dos_GetWd(405)
>   Very strange, couldn't stat "."
>
>
> error in the logs? I've noticed that it is occuring in some of the log
> files for users and not in others. I've looked in the source as to where
> this is occuring and added a path=%s\n",path to the DEBUG line to maybe
> see which UNIX directory is the culprit.
>
>
> Am I correct in my reading of the source that all this is doing is seeing
> if the current directory exists, and if so, grabbing the inode?
>
>
> One more... Could this be related to my previous oplock problem?
>
>
> Thanks!
> Bruce
>
>
> BTW, Samba version 2.0.0Beta4 and Linux RedHat 5.2
>