Bug 1960 - printcap reload after "addprinter command" was executed
printcap reload after "addprinter command" was executed
Product: Samba 3.0
Classification: Unclassified
Component: Printing
All Linux
: P3 normal
: none
Assigned To: Gerald (Jerry) Carter
Samba QA Contact
Depends on:
  Show dependency treegraph
Reported: 2004-10-22 15:13 UTC by Björn Jacke
Modified: 2005-02-07 09:18 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Björn Jacke 2004-10-22 15:13:12 UTC
after remote printer installation with a valid "addprinter command" Windows (I
tested with XP) claims that access is denied. The reason is that the just 
installed printer is not visible after that, it's just visible after the next
printcap reload of if you expictly send SIGHUP in the addprinter command script.
We should probably add a printcap reload after every addprinter call.
Comment 1 Guenther Deschner 2004-10-22 15:32:03 UTC
Hey Bjoern!

Were you giving back a port-name from the script?
Samba does send a SIGHUP if so.
Comment 2 Björn Jacke 2004-10-22 15:54:39 UTC
I just saw it, yes. I should better go to bed.
Comment 3 Gerald (Jerry) Carter 2005-02-07 09:18:51 UTC
originally reported against 3.0.8pre1.  Cleaning up 
non-production versions.