[Samba] spoolss back connections to client

[Tim Potter]

On Wed, Jun 12, 2002 at 09:11:12AM +0200, Tom Vandepoel wrote:

> # diff srv_spoolss.c srv_spoolss.c.orig
> 1415,1416c1415,1416
> < /* {"SPOOLSS_RFFPCNEX",                  SPOOLSS_RFFPCNEX, 
>       api_spoolss_rffpcnex                  }, */
> < /* {"SPOOLSS_RFNPCNEX",                  SPOOLSS_RFNPCNEX, 
>       api_spoolss_rfnpcnex                  }, */
> ---
> >  {"SPOOLSS_RFFPCNEX",                  SPOOLSS_RFFPCNEX, 
>      api_spoolss_rffpcnex                  },
> >  {"SPOOLSS_RFNPCNEX",                  SPOOLSS_RFNPCNEX, 
>      api_spoolss_rfnpcnex                  },
> 
> Running this since yesterday now. All printing functionality that worked 
> before still seems to work. Might even have speeded up connecting to 
> printers; it seems to me anyway, but that might be purely psychological ;-)

What happens to a port monitor when you print a document from another machine?
I'm curious to find out whether it falls back to polling or whether you
have to hit f5 to refresh all the time.

> Anyway, an smb.conf option for this would be nice. I guess a lot of 
> people have been wondering how to disable this annoying behavior ;-)

Something like 'disable spoolss notify'?


Tim.