Re: /etc/dbus-1/systemd/cups.conf and /usr/lib/systemd/system/cups.socket files

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



On Wed, Aug 22, 2012 at 1:37 PM, Tom Gundersen <teg@xxxxxxx> wrote:
> On Wed, Aug 22, 2012 at 7:31 PM, Myra Nelson <myra.nelson@xxxxxxxxxx> wrote:
>> After my research on sysvinit, the simple version, I'm working my way
>> through systemd. Two things I noticed about the cups configuration:
>>
>> 1: The cups.conf file in /etc/dbus-1/systemd reads
>
> Notice that this should have been "system.d" and not "systemd". These
> are the dbus configuration files (for the system bus), and not the
> systemd ones.
>
>> <!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
>>  "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd";>
>> <busconfig>
>>   <!-- Only root can send this message -->
>>   <policy user="root">
>>     <allow send_interface="com.redhat.PrinterSpooler"/>
>>   </policy>
>>
>>   <!-- Allow any connection to receive the message -->
>>   <policy context="default">
>>     <allow receive_interface="com.redhat.PrinterSpooler"/>
>>   </policy>
>> </busconfig>
>>
>> Do the allow send and allow receive interfaces need to be changed, or
>> is this taken into account by the rest of systemd?
>
> Sorry that I can't help you with more details, don't know cups/dbus that well.
>
>> 2. The /usr/lib/systemd/system/cups.socket reads
>> [Unit]
>> Description=CUPS Printing Service Sockets
>>
>> [Socket]
>> ListenStream=/var/run/cups/cups.sock
>> ListenStream=631
>> ListenDatagram=0.0.0.0:631
>> BindIPv6Only=ipv6-only
>>
>> [Install]
>> WantedBy=sockets.target
>
> Again, I don't know much about CUPS, so can't answer your question.
> However, just in case it was not clear, the above socket  file gives
> you:
>
> # ss -l -u -t | grep ipp
> udp    UNCONN     0      0                    *:ipp                   *:*
> tcp    LISTEN     0      128                 :::ipp                  :::*
>
> Where the tcp socket only accepts ipv6 connections. Please see
> systemd.socket(5) and ipv6(7) for more details.
>
>> With the
>> newer version of cups depending on avahi and the differences in the
>> avahi hosts file and the hosts file, avahi uses gandalf.local while
>> hosts still uses .localdomain.
>
> Not sure I got this last bit. Avahi defaults to using the "local"
> domain, but this can be configured if you prefer something else (at
> least I seem to remember doing that at some point).
>
> HTH,
>
> Tom

Cool. I was just trying to make both the domains come out the same.
I've tried it both ways, but can't get cups to work between the two
boxes. Let me rephrase that. I have the printer set up on my SO's box
and working. Then sudo firefox localhost:631, find/discover printers,
finds the printer, attempt to connect and test the printer with a test
page, "error can't find printer at arwen.localdomain". The pemissions
on her box are about as lenient as you can get "Allow all" everywhere.

Since all my network connections are static, and all the documentation
I've ever read pointed to setting up the hosts file at 127.0.0.1
localhost.localdomain localhost gandalf and ::01
localhost.localdomain, and after reading the LWN article, I thought
that might be the problem hence my question. On to more research.

Thanks for you time and assistance.

Myra

-- 
Life's fun when your sick and psychotic!


[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux