well, i would expect that the reboot in the scond ssh-session is
refused...
[root@master:~]$ /usr/bin/systemd-inhibit --what=shutdown --who=root
--why="Backup in progress" --mode=block sleep 600
[root@master:~]$ /usr/bin/systemd-inhibit; systemctl reboot
WHO UID USER PID COMM
On Mo, 10.08.20 15:05, Reindl Harald (h.rei...@thelounge.net) wrote:
> well, i would expect that the reboot in the scond ssh-session is
> refused...
>
> [root@master:~]$ /usr/bin/systemd-inhibit --what=shutdown --who=root
> --why="Backup in progress" --mode=block sleep 600
>
>
Hi David.
On Thu, Aug 06, 2020 at 01:59:03PM +1200, David Cunningham
wrote:
> The systemd file is as below, and we've confirmed that the PIDFile contains
> the correct PID when the stop is attempted. Would anyone have any
> suggestions on how to debug this? Thank you in advance.
Is the given
On Do, 06.08.20 13:59, David Cunningham (dcunning...@voisonics.com) wrote:
> Hello,
>
> I'm developing a service called product_routed which is managed by systemd.
> The service can normally be stopped with "service product_routed stop" or
> "systemctl stop product_routed", however for some
On Mo, 03.08.20 10:31, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) wrote:
> Hi!
>
> While examining a scheduling problem that might have resulted from
> restrictions imposed by cgroups, I examined my machine using systemd-cgtop
> and systemd-cgls (systemd-228-157.12.5.x86_64 of SLES12).
>
On So, 09.08.20 00:20, Vini Harimoorthy (vini6...@gmail.com) wrote:
> Hi Team,
>
>
> Is there a way to specify the "start date & time" of the timer unit with
> calendar timer ?
>
> For example, the below timer units runs every weekly from the service is
> activated.My requirement is that I need
Greetings,
I am using systemd-networkd and I am wondering how/why the interface names
get chosen.
Scenario:
I am expecting an interface name to be enp1s0. Instead I get eth1.
It appears that eth1 is being referenced in things like:
/etc/default/isc-dhcp-server
/etc/default/minissdpd
If I
On Fr, 17.07.20 14:38, Xogium (cont...@xogium.me) wrote:
> Hi,
> as the subject says, I am trying to use repart to add a partition on a block
> device, from inside the initramfs. I also make use of overlayfs via
> systemd-volatile-root to make it possible to write temporarily on the
> root
On Mo, 10.08.20 19:46, Böszörményi Zoltán (zbos...@pr.hu) wrote:
> Is there a way to describe optional mounts via such Conditions* options?
No.
.mount units automatically gain dependencies on the devices they are
mounted from. Only after all dependencies are fulfilled (i.e. the
backing device
Is anyone able to help with this issue ? Is this even supported/supposed to
work, or expected to fail ? I was hoping to use repart because the system I
have
to add a partition to is litterally 5000 km away, but so far this completely
fails.
Any help would be appreciated
On Tue Jul 28, 2020 at
On So, 09.08.20 15:56, Dave Howorth (syst...@howorth.org.uk) wrote:
> Is there anywhere that explains the rationale for systemd timers?
Probably somewhere in the git logs.
> What's their USP? Why was it necessary to invent the facility?
It kinda makes sense to invoke cronjobs the same way as
Hello.
On Mon, Aug 03, 2020 at 10:31:28AM +0200, Ulrich Windl
wrote:
> Why is systemd-cgtop outputting much less slices than systemd-cgls
> does? Specifically I don't see the slice for the process I'm examining
> ("system-iotwatch.slice"). systemd-cgls shows it with three services.
systemd-cgls
On Mo, 10.08.20 19:36, Lennart Poettering (lenn...@poettering.net) wrote:
> On Fr, 17.07.20 14:38, Xogium (cont...@xogium.me) wrote:
>
> > Hi,
> > as the subject says, I am trying to use repart to add a partition on a block
> > device, from inside the initramfs. I also make use of overlayfs via
>
On Do, 06.08.20 01:14, Arian Van Putten (ar...@wire.com) wrote:
> Hey List,
>
> I am reading
> https://systemd.io/BOOT_LOADER_SPECIFICATION/
> and
> https://systemd.io/AUTOMATIC_BOOT_ASSESSMENT/
>
> I want to use Type 2 unified images because of SecureBoot. But I want a
> 2-partition model a-la
On Mon, 10 Aug 2020 20:21:51 +0200
Lennart Poettering wrote:
> On So, 09.08.20 15:56, Dave Howorth (syst...@howorth.org.uk) wrote:
>
> > Is there anywhere that explains the rationale for systemd timers?
>
> Probably somewhere in the git logs.
Thanks, Lennart. I'll happily poke through the
2020. 08. 10. 20:08 keltezéssel, Lennart Poettering írta:
On Mo, 10.08.20 19:46, Böszörményi Zoltán (zbos...@pr.hu) wrote:
Is there a way to describe optional mounts via such Conditions* options?
No.
.mount units automatically gain dependencies on the devices they are
mounted from. Only
On Mon, 2020-08-10 at 20:19 +0100, Dave Howorth wrote:
> On Mon, 10 Aug 2020 20:21:51 +0200
> Lennart Poettering wrote:
> > i.e. it unifies how system programs are invoked, and that's a good
> > thing. it turns time-based activation into "just another type of
> > activation".
>
> Most of that
Hi,
I have to use the same OS image tarball (created by Yocto)
on several machines with different specifications.
Where they differ is the disk size and partitioning. On the smaller
machine (a Sicom SL20 POS hardware, boots from CF card) the disk size
is too small to have separate partitions
On Mon, 2020-08-10 at 15:37 +0200, Lennart Poettering wrote:
> On Mo, 10.08.20 15:05, Reindl Harald (h.rei...@thelounge.net) wrote:
>
> > well, i would expect that the reboot in the scond ssh-session is
> > refused...
> >
> > [root@master:~]$ /usr/bin/systemd-inhibit --what=shutdown
That seems to be working as expected.
The initial, kernel-assigned name is always going to be an incrementing
eth#, wlan#, or something similar. It's up to the userspace (i.e. udev) to
rename it to something custom.
However, interfaces can only be renamed while they're *not* up, otherwise
the
On 8/10/2020 12:19 PM, Dave Howorth wrote:
Most of that has gone over my head so some examples would probably help
me to understand. Perhaps they're in the git logs?
The key word is "activation". Modern systems are event-driven. Events
include hardware plugging in, powering up, another
Hi,
I have to use the same OS image tarball (created by Yocto)
on several machines with different specifications.
Where they differ is the disk size and partitioning. On the smaller
machine (a Sicom SL20 POS hardware, boots from CF card) the disk size
is too small to have separate partitions
Hello Lennart and Michal,
Thank you for your replies. The cgroup file is below - can you please
advise what is the relevant part to check?
The problem is most likely with systemd thinking the program is stopped
because "systemctl status" reports:
Aug 10 03:57:32 myhost systemd[1]:
23 matches
Mail list logo
