On Wed, 8 Jan 2014, Daniel Hedlund wrote: > You would also want to grep the /etc/cups for 192.168.55.1, just in case > it's hard-coded and the 'salmo' lookup I saw in strace was not related. I > saw a dns lookup of salmo, but it could've been to obtain the client IP > address so it could embed it in a cups message and not part of the > connection it established. strace doesn't tell you how things are > inter-related, only the order that kernel system calls occur.
Now, this finds the printer configurations: [root@salmo ~]# grep -R 192.168.55.1 /etc/cups/ /etc/cups/printers.conf:DeviceURI socket://192.168.55.194:9100 /etc/cups/printers.conf:DeviceURI socket://192.168.55.192:9100 /etc/cups/printers.conf:DeviceURI socket://192.168.55.192:9100 /etc/cups/printers.conf:DeviceURI socket://192.168.55.192:9100 /etc/cups/printers.conf:DeviceURI socket://192.168.55.192:9100 /etc/cups/printers.conf.O:DeviceURI socket://192.168.55.194:9100 /etc/cups/printers.conf.O:DeviceURI socket://192.168.55.192:9100 /etc/cups/printers.conf.O:DeviceURI socket://192.168.55.192:9100 /etc/cups/printers.conf.O:DeviceURI socket://192.168.55.192:9100 /etc/cups/printers.conf.O:DeviceURI socket://192.168.55.192:9100 /etc/cups/client.conf:ServerName 192.168.55.1 Changed client.conf to read ServerName salmo but that did not fix the problem. Thanks, Rich _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
