https://bugzilla.novell.com/show_bug.cgi?id=401354 Lars Müller changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |samba-maintainers@SuSE.de AssignedTo|samba-maintainers@SuSE.de |lmuelle@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=401354 User jnelson-suse@jamponi.net added comment https://bugzilla.novell.com/show_bug.cgi?id=401354#c2 Jon Nelson changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | --- Comment #2 from Jon Nelson 2008-06-19 06:46:49 MDT --- No disrespect intended, but that is incorrect. The init scripts have nothing to do with /etc/hosts.{allow,deny}. However, they do have to do with accepting or rejecting TCP connections somewhat later in the connection cycle than iptables, for example. In any case, this remains an issue and is very easy to confirm. Fixing, however, may be a more involved task. To test: install samba (server) and cups (server) on the same machine. It doesn't need to be the same machine but it's easier. configure samba to look at localhost and use cups by default. NOTE: normally this is the default (shipped!) configuration! Configure cups to start. Make sure you don't have anything in /etc/hosts.allow for cupsd, or that if you do it does not contain 127.0.0.0/24 Start cups Start smb You will notice that, while the init script *says* smb started, it has not bound to any ports (use netstat -planetu | grep smb) and an strace (such as strace -p $(pidof smbd) ) shows it looping forever on connections to 631 (cups) but being rejected by the tcp_wrapper functionality. Without doing anything else, edit /etc/hosts.allow and add the 127.0.0.1 host or network to the cupsd entry. As soon as you save, smbd will complete starting. You will also see errors in /var/log/cups/error_log that look like this: W [19/Jun/2008:07:45:08 -0500] tcp_wrappers refused connection from 127.0.0.1, ip=127.0.0.1. See /etc/hosts.allow and /etc/hosts.deny. But no errors in /var/log/messages or the samba logs. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=401354 User jnelson-suse@jamponi.net added comment https://bugzilla.novell.com/show_bug.cgi?id=401354#c4 Jon Nelson changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED Info Provider|jnelson-suse@jamponi.net | --- Comment #4 from Jon Nelson 2008-06-19 09:10:34 MDT --- The package I am using uses libwrap: turnip:~ # ldd $(which cupsd) | grep wrap libwrap.so.0 => /lib64/libwrap.so.0 (0x00002ae954794000) turnip:~ # rpm -qf $(which cupsd) cups-1.2.12-22.15 turnip:~ # rpm -V cups S.5..U.T c /etc/cups/cupsd.conf ....U.. /etc/cups/ppd M...U.. /etc/cups/ssl turnip:~ # rpm -qi cups Name : cups Relocations: (not relocatable) Version : 1.2.12 Vendor: SUSE LINUX Products GmbH, Nuernberg, Germany Release : 22.15 Build Date: Thu Apr 17 17:58:58 2008 Install Date: Wed Jun 18 09:49:30 2008 Build Host: icecream.suse.de Group : Hardware/Printing Source RPM: cups-1.2.12-22.15.src.rpm Size : 8106998 License: GPL v2 or later Signature : DSA/SHA1, Thu Apr 17 18:01:29 2008, Key ID a84edae89c800aca Packager : http://bugs.opensuse.org URL : http://www.cups.org/ Summary : The Common UNIX Printing System Description : The Common UNIX Printing System provides a portable printing layer for UNIX� operating systems like BSD lp or lprng. CUPS provides some additional features. http://www.cups.org Authors: -------- Easy Software Products Distribution: openSUSE 10.3 (X86-64) turnip:~ # -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=401354 User jnelson-suse@jamponi.net added comment https://bugzilla.novell.com/show_bug.cgi?id=401354#c6 --- Comment #6 from Jon Nelson 2008-06-19 16:18:22 MDT --- I disagree. It's a bug if samba doesn't start because some /other/ daemon is disallowing connections. Set your cups server to 127.0.0.1 (or whatever is appropriate) in smb.conf (this is the only configuration change I've made, as far as I can tell). Otherwise, the value from /etc/cups/client.conf is used. Since I don't have an /etc/cups/client.conf, I have to use a cups server configuration param. Even if it is a configuration error, it is not one that should cause samba to not start (especially since the init script thinks it has started successfully). A non-working cups should not also create a non-working samba. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=401354 User lmuelle@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=401354#c8 Lars Müller changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |INVALID --- Comment #8 from Lars Müller 2008-06-20 02:56:30 MDT --- It is still your setup. You're starting services in a different and unsupported way. And it is still not clear in which way you start them. This is a configuration issue of your system. Again: This is not Samba nor CUPS. There is nothing a system vendor is able to fix. Check your system how services get started. This is only your obligation. This is nothing a developer can help you. This is no bug. Sure. You can reopen it again and it will get closed as soon. And we can do this for several weeks. But this approach will not change the state of your system nor will it show you what you did wrong. Instead I suggest to perform a fresh install, configure /etc/samba/smb.conf and /etc/cups/cupsd.conf, start the services cups, nmb, and smb and check if even then a service fails to start. If this would be the case it would be a openSUSE bug. Anything else is cause between chair and keyboard. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=401354 User lmuelle@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=401354#c10 Lars Müller changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsmeix@novell.com, kssingvo@novell.com Status|REOPENED |NEEDINFO Info Provider| |jsmeix@novell.com --- Comment #10 from Lars Müller 2008-06-23 10:37:38 MDT --- It looks like cups honors /etc/hosts.deny in the case cupsd is connected on 127.0.0.1. As soon as 'cups server = 127.0.0.2' everything works as expected. I still don't know why this should be a defect of Samba if /etc/hosts.deny is configured to deny any access and CUPS honors this setting. Not to honor the same setting if 127.0.0.2 is used as address of the CUPS server might be a CUPS defect. MIGHT be as I'm not a CUPS expert. Johannes or Klaus: Is this a feature of CUPS? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=401354 User lmuelle@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=401354#c12 Lars Müller changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |WORKSFORME --- Comment #12 from Lars Müller 2008-06-24 06:25:44 MDT --- Then this is a feature and not a bug. We might consider to improve Samba in the direction not to wait for CUPS being ready. I doubt this is worth the effort as I don't see the benefit. Instead an administrator using this SUSE CUPS feature has to configure /etc/hosts.{deny,allow} in an appropriate way not to block access from locahost to CUPS. It is a configuration issue of /etc/hosts.{deny,allow} causing trouble to Samba if CUPS includes the feature to honor /etc/hosts.{deny,allow}. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.