a part of this problem is still there in 11.04, with samba, just upgraded from proposed-updates (2:3.5.8~dsfg-1ubuntu2.2), despite the log reports
* debian/samba.smbd.upstart: Do not attempt to start smbd until network
device is up, previously smbd was starting too early and often failing.
(LP: #771305)
I'm experimenting it in this "flavour": samba seems to be working, as I'm seeing a shared folder, but _printers only_ are not shared. As usual, a manual restart (sudo service smbd restart) fixes the issue (and the printer magically shows up in the WinVista client), but on reboot it's always the same: I can see the folder shares, not the printer.
Configuration of smbd.conf and nmbd.conf is all default, I also tried the modification of cipher2 (remove the "and net-device-up !loopback" from nmbd.conf) without success. Also, I tried to add a "and started nmbd" to "smbd.conf", as I spotted from the thread that the problem might be due to smbd and nmbd booting up concurrently, again without success.
Something very strange I have in /var/log/boot.log:
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service S20smbd start
Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the start(8) utility, e.g. start S20smbd
start: Unknown job: S20smbd
As you can see, it seems smbd's name is being actually mistaken as "S20smbd", i.e., the rc.d link. However, I double-checked the rc.d links, and I can't see anything irregular:
Hi,
a part of this problem is still there in 11.04, with samba, just upgraded from proposed-updates (2:3.5. 8~dsfg- 1ubuntu2. 2), despite the log reports
* debian/ samba.smbd. upstart: Do not attempt to start smbd until network
device is up, previously smbd was starting too early and often failing.
(LP: #771305)
I'm experimenting it in this "flavour": samba seems to be working, as I'm seeing a shared folder, but _printers only_ are not shared. As usual, a manual restart (sudo service smbd restart) fixes the issue (and the printer magically shows up in the WinVista client), but on reboot it's always the same: I can see the folder shares, not the printer.
Configuration of smbd.conf and nmbd.conf is all default, I also tried the modification of cipher2 (remove the "and net-device-up !loopback" from nmbd.conf) without success. Also, I tried to add a "and started nmbd" to "smbd.conf", as I spotted from the thread that the problem might be due to smbd and nmbd booting up concurrently, again without success.
Something very strange I have in /var/log/boot.log:
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service S20smbd start
Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the start(8) utility, e.g. start S20smbd
start: Unknown job: S20smbd
As you can see, it seems smbd's name is being actually mistaken as "S20smbd", i.e., the rc.d link. However, I double-checked the rc.d links, and I can't see anything irregular:
$ ls -l /etc/rc*/*smb*
lrwxrwxrwx 1 root root 14 2011-05-03 13:08 /etc/rc2.d/S20smbd -> ../init.d/smbd
lrwxrwxrwx 1 root root 14 2011-05-03 13:08 /etc/rc3.d/S20smbd -> ../init.d/smbd
lrwxrwxrwx 1 root root 14 2011-05-03 13:08 /etc/rc4.d/S20smbd -> ../init.d/smbd
lrwxrwxrwx 1 root root 14 2011-05-03 13:08 /etc/rc5.d/S20smbd -> ../init.d/smbd
and the smbd.conf is there in /etc/init/ smbd.conf.
Now I'm going to try this samba4.