search for: sys_adminlog

Hi Kurt, I've read the new document. It's a very fine piece of technical documentation. However, it doesn't help me in the present predicament. Going now by this book I'm only getting more frustrated. What are your versions of Samba, CUPS(?), OS, and Printer again? 2.2.8a, 1.1.18, SuSE 8.2 w/2.4.20-62, Lexmark C720 I'm stuck! I would

The samba log files leave something to be desired in both format and management. I'd like to propose a change if I could. Format: Previously, a log entry is cut with date and timestamp and action on a SINGLE line. Now the date and timestamp is on a separate line from the information that you'd look for in a log file (machine name, ip address, connection status for service, etc.) This is

Hello, I have installed cups on a linux server (running with RH 9.0). When executing "cupsaddsmb -a -v", I get an error: NT_STATUS_UNSUCCESSFULL, when attemping to execute adddriver". Can someone help on the meaning of this error, and on its reason (cause) ? Please find hereafter a file with result (and the error) of this commmand "cupsaddsmb", for a printer:

Hi Matt, the problem you referred to is discussed in detail as bug #82 in Samba's bug tracking tool. It consists of 2 bugs. One prevents the registration of drivers and is due to a NULL-pointer passed from that part of code in rpc_server/srv_spoolss_nt.c which calls sys_adminlog function. It begins with the comment /* BEGIN_ADMIN_LOG */ and ends with the comment /* END_ADMIN_LOG */ The comments surround the code which should log that a printer driver has been added, listing driver's name, its OS, and admin's name. Since this sys-admin-logging is non-essen...

I've not been able to get Samba to print to a Lexmark Z53. If I call it a Z52, the driver uploads (to where, I have no idea so I can't check it) but I still can't get anything out of the printer.

Hello I try to install drivers from CD to print$ share. I use the APW for that, but when the system have finish to copy drivers, w2k says that he cannot complete the process. And the log of the machine says : [2003/03/26 11:56:41, 0] passdb/pdb_ldap.c:ldap_connect_system(316) ldap_connect_system: Binding to ldap server as "cn=manager,dc=corman,dc=be" [2003/03/26 14:26:53, 0]