control: tags -1 + moreinfo
thanks

On 16-Dec-2014, martin f krafft wrote:
> It seems impossible to daemonise a programme with python-daemon
> without overwriting additional groups defined for the user that
> should run the daemon.

Evidently this isn't necessary for daemonising; I think “impossible to
daemonise” is a mischaracterisation of this behaviour. The process
daemonises just fine, it can only do what the OS allows it to do.

> but even if I do not pass the gid value to DaemonContext, then then
> process is unable to read this file:
> 
>   -rw-r----- 1 root ssl-cert 1704 Dec 16 14:08 
> /etc/ssl/private/ssl-cert-snakeoil.key

Right, AFAIK a process that began as non-superuser has no way of adding
supplementary groups. So, a process which daemonises itself is no
exception to this.

Do you know of a Posix feature that you expect a non-superuser process
to use when daemonising, in order to gain groups it did not have
before daemonising?

-- 
 \       “During the Middle Ages, probably one of the biggest mistakes |
  `\   was not putting on your armor because you were ‘just going down |
_o__)                                    to the corner.’” —Jack Handey |
Ben Finney <b...@benfinney.id.au>

Attachment: signature.asc
Description: Digital signature

Reply via email to