Bug 1960 - printcap reload after "addprinter command" was executed
Summary: printcap reload after "addprinter command" was executed
Status: RESOLVED INVALID
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: Printing (show other bugs)
Version: 3.0.8
Hardware: All Linux
: P3 normal
Target Milestone: none
Assignee: Gerald (Jerry) Carter (dead mail address)
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-22 15:13 UTC by Björn Jacke
Modified: 2005-02-07 09:18 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

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 (dead mail address) 2005-02-07 09:18:51 UTC 
originally reported against 3.0.8pre1.  Cleaning up 
non-production versions.