Re: Creating system users and system groups

2017-02-02 Thread Till Kamppeter
On 02/02/2017 08:49 AM, Mark Shuttleworth wrote: Our general thinking is that we will maintain a standard list of those, and approve user creation for specific snaps. Would you be willing to go with _avahi and _lp and _lpadmin? Backward-looking names might get grandfathered, but we'd prefer

Re: Creating system users and system groups

2017-02-02 Thread Till Kamppeter
On 02/02/2017 08:19 AM, Oliver Grawert wrote: on a side note this is also not necessary, all your services can run as root thanks to confinement, the user will not matter since other processes can only access your services through interfaces that shield them. running as root is fine here ...

Re: Creating system users and system groups

2017-02-02 Thread Till Kamppeter
On 02/02/2017 06:36 AM, Simon Fels wrote: Hey Till, That is (as far as I know) not possible today. Those groups and users have to exist beforehand. A similar problem also exists for LXD. There is a bug at https://bugs.launchpad.net/snappy/+bug/1606510 which has a few more details. OK, I have

Creating system users and system groups

2017-02-01 Thread Till Kamppeter
Hi, I want to snap CUPS and for that also to snap avahi-daemon. A problem I am running into is that these services use special system users and groups. avahi-daemon uses the user "avahi" and CUPS uses the user "lp", and the groups "lp" and "lpadmin". How can I make my snap create such users

Re: CUPS in a snap: avahi-daemon needed

2017-01-25 Thread Till Kamppeter
On 01/25/2017 05:18 PM, Sergio Schvezov wrote: snapweb uses a small mdns implementation written in go; avahi is much more than that. That said, the original versions of snapweb, formerlly known as webdm did have a full blown avahi-daemon inside, but it is really cumbersome if not needed.

Re: CUPS in a snap: avahi-daemon needed

2017-01-25 Thread Till Kamppeter
On 01/25/2017 04:52 PM, Kyle Fazzari wrote: Well there's a difference between using avahi and just broadcasting mDNS yourself, which is what I believe snapweb does, correct? CUPS is not able to broadcast shared printers by itself. It registers them at avahi-daemon and avahi-daemon broadcasts

CUPS in a snap: Using content interface to connect printer driver snaps

2017-01-25 Thread Till Kamppeter
Hi, I am currently snapping CUPS (both for server and for desktop/phone printing needs) and testing it on Ubuntu Core. Another reason to put CUPS into a snap is that one could also snap printer drivers to have them in a distribution-independent package format (so that manufacturers need to

CUPS in a snap: Need to create system group "lpadmin"

2017-01-25 Thread Till Kamppeter
Hi, I am currently snapping CUPS (both for server and for desktop/phone printing needs) and testing it on Ubuntu Core. Here I have found out that there is no "lpadmin" system group. Now I want to know how to create system groups and users out of a snap, so that they get created on

CUPS in a snap: avahi-daemon needed

2017-01-25 Thread Till Kamppeter
Hi, I am currently snapping CUPS (both for server and for desktop/phone printing needs) and testing it on Ubuntu Core. Here I have found out that there is no avahi-daemon (which CUPS needs for sharing local printers and for discovering remote network printers. Now I want to know what I

How to control order of daemon starts in a snap

2016-10-11 Thread Till Kamppeter
Hi, I am making a snap containing both cupsd and cups-browsed, cupsd has to be started first, then cups-browsed, and on shutdown cups-browsed has to stop before cupsd. cups-browsed needs a running cupsd all the time. How do I define the correct startup/shutdown sequence? Till --

CUPS out of a snap: Filters and backends do not have access to system resources

2016-10-11 Thread Till Kamppeter
Hi, I have snapped cups (listening on port 10631 to not interfere with the system's CUPS) and cups-filters into one single snap. The CUPS web interface (http://localhost:10631/) works, one can set up print queues, kill jobs, ... Printing jobs also works, at least when there is no need to