Hi,
I'm playing systemd-nspawn, and something interesting happens.
Try 1: host CentOS 8 Stream, systemd-nspawn to Debian Trixie
everything goes well.
Try 2: host CentOS 8 Stream , kvm guest CentOS 8 Stream
a: in guest systemd-nspawn to Debian Trixie , nspawn is OK to start without
—boot
b: in gues
HI
timedatectl set-ntp false
what is the diff between this and
systemctl disable ntp
Thanks
>
> should stop and disable it.
>
>
> Kind regards,
>
> Paul
> ___
> systemd-devel mailing list
> systemd-devel@lists.freedesktop.org
> https://lists.fr
[user@host ~]$ systemctl poweroff
>>
>> AUTHENTICATING FOR org.freedesktop.login1.set-wall-message
>>
>> Authentication is required to set a wall message
>>
>> Authenticating as: root
>>
>> Password
>>
>
UPDATED:
some of folks just kindly remind me that polkit configuration will be the
ke
Hi,
>
> > Is it default behavior by design? I dont think a non-privileged user
> > could reboot the system as he/she wishes.
> >
> > btw, I'm in an HPC related domain, if this behavior of systemctl is
> > allowed, every single user could reboot the whole cluster as they wish,
> > it's a disaster.
Hi,
> It really depends on the policykit setup.
>
it is, I'm sure even i'm not good at polkit (or even i didn't know polkit,
i still believe there is some config
control over this)
i'm saying of the default behavior after installation.
>
> e.g. if the user is in the wheel group, they may have add
Hi, folks,
I used to type systemctl reboot with non-privileged users, and to my
surprise, the system goes down for the reboot.
I've tested in both debian and centos 7, they act the same, however,
systemctl halt will prompt you to enter administrator password to continue.
Is it default behavior b
