![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
I compiled the latest version of Samba yesterday afternoon to save myself being bored to death while listening in on a telecon. Prior to doing so, I went and reinstalled CUPS, then forced a complete reinstall of the standard SysV and Impressario print subsystems over top of it, which means I have working printing, and Samba can now lock files again.
It still spews this crap continuously:
Apr 7 11:17:45 3D:dragon smbd[775649]: [2006/04/07 11:17:45, 0] printing/print_cups.c:(84)
Apr 7 11:17:45 3D:dragon smbd[775649]: Unable to connect to CUPS server localhost - Connection refused
Apr 7 11:17:45 3D:dragon smbd[775649]: [2006/04/07 11:17:45, 0] printing/print_cups.c:(84)
Apr 7 11:17:45 3D:dragon smbd[775649]: Unable to connect to CUPS server localhost - Connection refused
to syslog, but at least it's no longer spewing oplock errors.
It still pisses me off that despite explicitly telling samba to not use CUPS, it insists on trying anyway.
The new version still won't auth via AD properly, and falls back to RPC. But hey, the answer to all those samba issues is sitting on the floor of my office.
It still spews this crap continuously:
Apr 7 11:17:45 3D:dragon smbd[775649]: [2006/04/07 11:17:45, 0] printing/print_cups.c:(84)
Apr 7 11:17:45 3D:dragon smbd[775649]: Unable to connect to CUPS server localhost - Connection refused
Apr 7 11:17:45 3D:dragon smbd[775649]: [2006/04/07 11:17:45, 0] printing/print_cups.c:(84)
Apr 7 11:17:45 3D:dragon smbd[775649]: Unable to connect to CUPS server localhost - Connection refused
to syslog, but at least it's no longer spewing oplock errors.
It still pisses me off that despite explicitly telling samba to not use CUPS, it insists on trying anyway.
The new version still won't auth via AD properly, and falls back to RPC. But hey, the answer to all those samba issues is sitting on the floor of my office.
