Comment 2 for bug 1182655

Noticed today as well on 13.04 (64-bit).

The "reload-smbd" upstart script already exists to handle this per the prior bugs, but apparently something's still racing.

-rw-r--r-- 1 root root 213 Nov 23 08:55 /etc/init/reload-smbd.conf

smbd.log appears to suggest that the reload isn't happening (boot at 13:00; manual restart of smbd when printing issue noticed at 14:23):

[2013/05/21 13:00:07, 0] smbd/server.c:1026(main)
  smbd version 3.6.9 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2011
[2013/05/21 13:00:07.819348, 0] smbd/server.c:1082(main)
  standard input is not a socket, assuming -D option
[2013/05/21 13:00:07.828557, 0] printing/print_cups.c:151(cups_connect)
  Unable to connect to CUPS server localhost:631 - Transport endpoint is not connected
[2013/05/21 13:00:07.829032, 0] printing/print_cups.c:528(cups_async_callback)
  failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL
[2013/05/21 13:00:09.208510, 0] printing/print_cups.c:151(cups_connect)
  Unable to connect to CUPS server localhost:631 - Transport endpoint is not connected
[2013/05/21 13:00:09.209564, 0] printing/print_cups.c:528(cups_async_callback)
  failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL
[2013/05/21 14:23:11, 0] smbd/server.c:1026(main)
  smbd version 3.6.9 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2011
[2013/05/21 14:23:12.160294, 0] smbd/server.c:1082(main)
  standard input is not a socket, assuming -D option