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.
Were you giving back a port-name from the script?
Samba does send a SIGHUP if so.
I just saw it, yes. I should better go to bed.
originally reported against 3.0.8pre1. Cleaning up