On Thu, Sep 01, 2005 at 07:42:36AM +0200, Gregor Ibic wrote: > Here is a process list and strace to smbclient and tar. You can see that > is stalled at some opening of the file. > I modified share name and file name for security reasons. > > regards, > gregor > > 19432 ? S 0:00 /bin/sh /usr/sbin/amdump tape > 19442 ? S 0:20 /usr/libexec/amanda/driver tape > 19443 ? S 21:31 taper tape > 19444 ? S 69:20 dumper0 tape > 19445 ? S 5:36 dumper1 tape > 19446 ? S 3:26 dumper2 tape > 19447 ? S 17:10 taper tape > 24836 ? S 0:00 /usr/libexec/amanda/sendbackup > 24838 ? S 0:00 /bin/gzip --best > 26743 ? S 0:01 /usr/libexec/amanda/sendbackup > 26761 ? S 0:00 pickup -l -t fifo -u > 26747 ? S 0:00 sed -e s/^\.// > 26746 ? S 0:00 /bin/tar -tf - > 26745 ? S 0:00 sh -c /bin/tar -tf - 2>/dev/null | sed -e > 's/^\.//' > 26744 ? S 0:07 smbclient \\server\sharename -U username -E > -d0 -Tqca > 26778 pts/15 R 0:00 ps ax > > > [EMAIL PROTECTED] root]# strace -p 26744 > Process 26744 attached - interrupt to quit > write(2, "NT_STATUS_ACCESS_DENIED opening "..., 134 <unfinished ...> > Process 26744 detached >
Slightly different interpretation of this trace: smbclient on the samba server seems to have asked to access some resource on the pc client, possibly a file or a share, and has already received a denial. What is happening in the above trace is smbclient trying to note that information to its own standard error stream (the file descriptor "2" in the write system call is stderr). Why would a write to stderr hang? Not sure, is it connected to a pipe which could block if there are no readers? Is it writing to a file that has reached some max size or file system full? What is smbclient's normal error log file? How is that file system? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road (609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
