On 2020-07-01 17:45, Kai Peter wrote:
Hi,
I'm curious why the option -pidfile creates a file with mode 0600.
Usually I drop root privileges with the -runas parameter. The pidfile
is then owned by root:root and there is no chance to read it with the
new uid. Running a post command to change the
On 2020-07-01 18:00, Ottavio Caruso wrote:
On Wed, 1 Jul 2020 at 16:59, Ottavio Caruso
wrote:
On Wed, 1 Jul 2020 at 16:45, Kai Peter wrote:
>
> Hi,
>
> I'm curious why the option -pidfile creates a file with mode 0600.
It doesn't :
Sorry, I meant it does, but not owned by root:
On Wed, 1 Jul 2020 at 16:59, Ottavio Caruso
wrote:
>
> On Wed, 1 Jul 2020 at 16:45, Kai Peter wrote:
> >
> > Hi,
> >
> > I'm curious why the option -pidfile creates a file with mode 0600.
>
> It doesn't :
Sorry, I meant it does, but not owned by root:
>
> oc@e130:~$ cat
On Wed, 1 Jul 2020 at 16:45, Kai Peter wrote:
>
> Hi,
>
> I'm curious why the option -pidfile creates a file with mode 0600.
It doesn't :
oc@e130:~$ cat opt/bin/boot-openbsd-virtio
#!/bin/sh
qemu-system-x86_64 \
-drive if=virtio,file=/home/oc/VM/img/openbsd.image,index=0,media=disk \
-M
Hi,
I'm curious why the option -pidfile creates a file with mode 0600.
Usually I drop root privileges with the -runas parameter. The pidfile is
then owned by root:root and there is no chance to read it with the new
uid. Running a post command to change the mode is a bit annoying. And in
