Mike McCandless
2003-Apr-12 21:07 UTC
[Samba] Continual lib/access.c:check_access - what's it mean?
When I look at the log file for a particular user, I see the following, about every 11-12 minutes. The only thing I'm using my Samba server for is acting as a master browser, and print server (with CUPS). There are no domain logons. This activity in the log file keeps going well beyond when a print job is complete. [2003/04/12 15:27:25, 2, pid=948, effective(0, 0), real(0, 0)] lib/access.c:check_access(329) Allowed connection from (192.168.1.103) Why am I getting these messages after the print job is done? -------------------------------------------------------- Mike McCandless michael@prismbiz.com Red Hat Linux Certified Technician
Mike McCandless
2003-Apr-12 21:14 UTC
[Samba] Continual lib/access.c:check_access - what's it mean?
As a bit more background info, I switched to log level 3, and now I'm seeing the following continue to repeat itself...This is in a user log file that does not have an entry in /etc/smbpasswd. What's going on? [2003/04/12 17:12:47, 3, pid=960, effective(99, 99), real(0, 0)] smbd/process.c:process_smb(878) Transaction 130466 of length 124 [2003/04/12 17:12:47, 3, pid=960, effective(99, 99), real(0, 0)] smbd/process.c:switch_message(685) switch message SMBtrans (pid 960) [2003/04/12 17:12:47, 3, pid=960, effective(99, 99), real(0, 0)] smbd/ipc.c:reply_trans(520) trans <\PIPE\> data=44 params=0 setup=2 [2003/04/12 17:12:47, 3, pid=960, effective(99, 99), real(0, 0)] smbd/ipc.c:named_pipe(334) named pipe command on <> name [2003/04/12 17:12:47, 3, pid=960, effective(99, 99), real(0, 0)] smbd/ipc.c:api_fd_reply(296) Got API command 0x26 on pipe "spoolss" (pnum 74a6)free_pipe_context: destroying talloc pool of size 0 [2003/04/12 17:12:47, 3, pid=960, effective(99, 99), real(0, 0)] rpc_server/srv_pipe.c:api_pipe_request(1148) Doing \PIPE\spoolss [2003/04/12 17:12:47, 3, pid=960, effective(99, 99), real(0, 0)] rpc_server/srv_pipe.c:api_rpcTNP(1180) api_rpcTNP: pipe 29862 rpc command: SPOOLSS_CLOSEPRINTER [2003/04/12 17:12:47, 3, pid=960, effective(99, 99), real(0, 0)] rpc_server/srv_lsa_hnd.c:close_policy_hnd(205) Closed policy [2003/04/12 17:12:47, 3, pid=960, effective(99, 99), real(0, 0)] rpc_server/srv_pipe_hnd.c:free_pipe_context(444) free_pipe_context: destroying talloc pool of size 0 ----- Original Message ----- From: "Mike McCandless" <michael@prismbiz.com> To: <samba@lists.samba.org> Sent: Saturday, April 12, 2003 5:07 PM Subject: [Samba] Continual lib/access.c:check_access - what's it mean?> When I look at the log file for a particular user, I see thefollowing,> about every 11-12 minutes. The only thing I'm using my Samba serverfor> is acting as a master browser, and print server (with CUPS). Thereare> no domain logons. > > This activity in the log file keeps going well beyond when a print job > is complete. > > [2003/04/12 15:27:25, 2, pid=948, effective(0, 0), real(0, 0)] > lib/access.c:check_access(329) > Allowed connection from (192.168.1.103) > > Why am I getting these messages after the print job is done? > > > -------------------------------------------------------- > Mike McCandless > michael@prismbiz.com > Red Hat Linux Certified Technician > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba