search for: print3

Hello, I configure my PDc as print server. With cups, I configure 3 printers (names : print1 print2 and prinnt3). After that I saw the error in the last printer's name. So I delete prinnt3 and create print3). But if I connect to my print server (using Windows), I have 4 printers : print1 -3 and prinnt3 I restart cups and reload smb daemon several times but the ghost is still there. I have the prob for 2 days now so I supposed that it's not a network neighborhood prob anymore ?

...nly Disk forceuser Disk forcegroup Disk ro-tmp Disk msdfs-share Disk hideunread Disk tmpcase Disk hideunwrite Disk print1 Printer print2 Printer print3 Printer lp Printer print$ Disk IPC$ IPC IPC Service (Samba 4.0.0alpha16) Server Comment --------- ------- Workgroup Master --------- ------...

http://bugzilla.netfilter.org/show_bug.cgi?id=741 Summary: ULOGD segfaults on init Product: ulogd Version: SVN (please provide timestamp) Platform: i386 OS/Version: other Status: NEW Severity: blocker Priority: P5 Component: ulogd_MYSQL AssignedTo: netfilter-buglog at lists.netfilter.org

...smb username is [] tmpcase Disk smb username is [] hideunwrite Disk smb username is [] durable Disk smb username is [] fs_specific Disk smb username is [] print1 Printer smb username is [] print2 Printer smb username is [] print3 Printer smb username is [] lp Printer smb username is [] nfs4acl_simple_40 Disk smb username is [] nfs4acl_special_40 Disk smb username is [] nfs4acl_simple_41 Disk smb username is [] nfs4acl_xdr_40 Disk smb username is [] nfs4acl_xdr_41 Disk...

Thanks for the reply, Besides the problem with source4/lib/messaging/messaging_handlers.c, Good to hear that selftest is actively used, then do I understand it right that 'make test' should succeed? My bigger problem is that it failed with lots of errors. This must be a problem with my build, then, but since this is a fresh tarball I am a bit puzzled. I would appreciate some hint on