debugging smbd
Marty Leisner
leisner at sdsp.mc.xerox.com
Fri Apr 17 20:55:18 GMT 1998
I traditionally hacked up the code where I want to break, but in a
printf
and a
pause
and then attach the debugger to it (enabling it with an environment variable).
Is there a better/easier way to do this?
Unfortuneably, sticking this after the fork breaks smb clients, since they
expect the protocol negotiation to happen in a few seconds (is there any
way to tell the clients not to time out so fast?)
Anyway, in lanman1, the lpq shows for print jobs:
14th leisner 13 /tmp/LEISNER.a00550 43429 bytes
15th leisner 14 /tmp/LEISNER.a00550 43429 bytes
16th leisner 15 /tmp/LEISNER.a00550 43429 bytes
17th leisner 16 /tmp/LEISNER.a00550 43429 bytes
18th leisner 17 /tmp/LEISNER.a00940 43429 bytes
19th leisner 18 /tmp/LEISNER.a00940 43429 bytes
20th leisner 19 /tmp/LEISNER.a00940 43429 bytes
21st leisner 20 /tmp/LEISNER.a00940 43429 bytes
22nd leisner 21 /tmp/LEISNER.a00940 43429 bytes
23rd leisner 22 /tmp/LEISNER.a00997 16769 bytes
24th leisner 23 /tmp/LEISNER.a00997 15916 bytes
It probably would be useful to give each a distinct name
like USER.PID.1
USER.PID.2
etc.
(I wanted to debug print_file).
Since we already have the account, would it make sense to encode the
netbios machine in the file name? (i.e. netbios name instead of user name?)
marty leisner at sdsp.mc.xerox.com
Don't confuse education with schooling.
Milton Friedman to Yogi Berra
More information about the samba-technical
mailing list