Rick Voland <[EMAIL PROTECTED]> wrote:

> Heino Tiedemann wrote:
>> "Bruce A. Mah" <[EMAIL PROTECTED]> wrote:
>> 
>>> If memory serves me right, David MAREC wrote:
>>>> Is there new device policies defined by cups ?
>>>>
>>> I noticed that the cups port now installs a cups user and group.  I
>>> infer from that change that some portion of cups now runs as a
>>> non-privileged user, and that if you're driving a parallel port, it
>>> needs to writable (readable too?) by the new cups user.
>>>
>>> (I encountered this problem on my RELENG_6/i386 print server machine,
>>> made /dev/lpt0 owned by cups:cups, and it worked. 
>> 
>> root:cups is also workig (rw-rw----).
>> 
>> Heino
>> 
>> _______________________________________________
>> freebsd-ports@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
>> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>> 
>
>
>
>
>
> You may want to read
>
> http://groups.google.com/group/lucky.freebsd.ports.bugs/browse_thread/thread/2afcd691d1fa4207/e74721b94f2b02a6?lnk=st&q=freebsd+cups&rnum=7#e74721b94f2b02a6
>
> This message suggests a solution that involves changing permissions on
> /dev/lpt*
> (also an issue for usb printers)
>
> -------------begin quote
>
>
> Add following lines to /etc/devfs.rules:
>
> [system=10]
> add path 'lpt*' mode 0660 group cups
>
> And following to /etc/rc.conf:
>
> devfs_system_ruleset="system"
>
>
> -------------end quote

I found 2 Solutions fpr the permissions:


Solution a)

,----
| I've added the following to /etc/devfs.conf:
| own     lpt0    root:cups
| perm    lpt0    0660 
`----



Solution b)
,----
| Add following lines to /etc/devfs.rules:
|
| [system=10]
| add path 'lpt*' mode 0660 group cups
| 
| And following to /etc/rc.conf:
| 
| devfs_system_ruleset="system"
`----


Is there one way to prefer?

Heino

_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to