s3:rpc_server/spoolss: remove reload_services check from delete_printer_hook()

As the spoolss code can run embedded or external relative to the
smbd file server process, it's very tricky to verify if a share
is still in use.

Checking the result of the "deleteprinter command" command should
be enough to check for success. We should not return WERR_ACCESS_DENIED
if the share is still in use, by the current client, as the primary
printer definition is already deleted.

metze

0 files changed, 0 insertions, 0 deletions