I want to use Samba to debug a program. It is trying to open a file or directory that does not exist, and I can't figure out what the name of it is. Is there a way to make Samba log file access that fails (file not found, directory not found, etc.)? Thanx, John -=+=- The Good, Clean Funnies List: Good, clean funnies five times a week, for free! To subscribe or unsubscribe send email with "add" or "remove" in the subject line (without the quotes) to "gcfl-request@usa.net". Send submissions and comments to "gcfl@usa.net". Or go to the web page: http://www.angelfire.com/al/GCFL A cheerful heart is good medicine... Prov 17:22a (NIV)
Hi> I want to use Samba to debug a program. It is trying to open a file or > directory that does not exist, and I can't figure out what the name of > it is. > > Is there a way to make Samba log file access that fails (file not found, > directory not found, etc.)?Besides the normal way of adding debugging printfs you can choose another (simpler) ways: 1. Use some of the file-open tracking utility under pure DOS. I wrote some tracker but it needs another hercules/MDA monitor. (another chance are several lines of ASM code to catch INT21/3Dh and print it out to screen. Unfortunately it sometimes collides with normal program output - especially in graphics modes.) 2. Use some equivalent of tcpdump or another packet sniffing tool. The best would be some with SMB disassembly capabilities (such as tcpdump found on samba.anu.edu.au). 3. Use some equivalent of strace (under Linux) to track kernel calls of smbd as user level process under UNIX. Happy hacking, Jan "Lace" Kratochvil
On Tue, 27 Jan 1998 05:20:37 +1100, you wrote:> >I want to use Samba to debug a program. It is trying to open a file or >directory that does not exist, and I can't figure out what the name of >it is. > >Is there a way to make Samba log file access that fails (file not found, >directory not found, etc.)? > >Thanx, >John >Try hiking up the debug level (debug level = in your smb.conf), this should solve your problem.
I changed the debug level to 9, but it still did not seem to output failed file access attempts. What else? On Monday, January 26, 1998 5:00 PM, shyde@poboxes.com wrote:> On Tue, 27 Jan 1998 05:20:37 +1100, you wrote: > > > > >I want to use Samba to debug a program. It is trying to open a file or > >directory that does not exist, and I can't figure out what the name of > >it is. > > > >Is there a way to make Samba log file access that fails (file not found, > >directory not found, etc.)? > > > >Thanx, > >John > > > Try hiking up the debug level (debug level = in your smb.conf), this > should solve your problem. >
Hi> Number 1 sounds like something I could use. I don't have the source > code. It's an old accounting package.You can download it from following place: ftp://k332.feld.cvut.cz/pub/local/short/doswatch.zip - the main full-featured watches - REQUIRES MDA/HERCULES ADAPTER (as the secondary one - preferred, although not needed) ftp://k332.feld.cvut.cz/pub/local/short/openptch.com - very simple INT21/3D -> INT21/09 converter ftp://k332.feld.cvut.cz/pub/local/short/openwait.com - just as openptch.com but waits for keypress after each file> Maybe you could email me the program you refer to.Sorry, I hate binary->mail encapsulations... Jan "Lace" Kratochvil> > > I want to use Samba to debug a program. It is trying to open a file or > > > directory that does not exist, and I can't figure out what the name of > > > it is. > > > > 1. Use some of the file-open tracking utility under pure DOS. I wrote > > some tracker but it needs another hercules/MDA monitor. (another chance > > are several lines of ASM code to catch INT21/3Dh and print it out to > > screen. Unfortunately it sometimes collides with normal program output > > - especially in graphics modes.) > > > > Happy hacking, > > Jan "Lace" Kratochvil
I am running Samba on Solaris 2.51 and accessing it on NT 4.0 workstations. It has worked beautifully for over a year now !UNTIL! recently we received the new MS Office suite which requires NT service pack 3. Since installing NT SP3 i get a message "the account is not authorized to login from this station" when I try to map a (previously used wnad working) samba-shared drive on my PC. I have since unistalled NT SP3 and tried again, and then it worked fine, so something loaded with SP3 is the problem. Any idea what? Anyone solved this problem? A solution would be oh so appreciated. Thanks-- John Hintz Nez Perce Tribe Lapwai, ID