>>> Lennart Poettering schrieb am 19.12.2020 um 13:34
in
Nachricht <20201219123435.GJ48346@gardel-login>:
> On Fr, 20.11.20 10:39, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de)
wrote:
>
>> Hi!
>>
>> journactl ‑b is quite fast to display the first lines, but when I
>> want to see the last
Hi Lennart,
Apology for the late reply and wish you happy new year!
We are using Yocto 3.1 dunfell with systemd v244-stable on arm64.
Let me know if any other additional information is needed, I am happy to
share.
Regards,
Aditya Tayade
On Mon, Dec 21, 2020 at 8:53 PM Lennart Poettering
>>> Germano Massullo schrieb am 27.12.2020 um
14:26 in
Nachricht :
> Good day, I recently joined apcupsd (APC UPS Power Control Daemon)
> package maintainers on Fedora/CentOS/RHEL.
> After a power failure, apcupsd shuts down the system with a command
> almost identical to
> shutdown ‑h ‑H now
>
>>> Robert Dahlem schrieb am 20.12.2020 um 12:48 in
Nachricht :
> Hi,
>
> is there a way to NOT run ExecStop, when a service started successfully,
> but ends later without being stopped?
>
> My scenario: I have an ExecStop that should only run after
>
> systemctl stop XXX.service
>
>
>>> Lennart Poettering schrieb am 19.12.2020 um 13:44
in
Nachricht <20201219124443.GM48346@gardel-login>:
> On Mo, 30.11.20 12:08, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de)
wrote:
>
>> Hi!
>>
>> I just made an "interesting" observation: When running "journalctl
>> ‑f" there is no message
>>> Lennart Poettering schrieb am 21.12.2020 um 16:18
in
Nachricht <20201221151821.GC50805@gardel-login>:
> On Fr, 18.12.20 08:44, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de)
wrote:
>
>> Hi!
>>
>> I have a simple question: For a socket‑unit I have:
>> LISTEN
Hello,
I run systemd on a NAS without internal-clock-holding battery, so I think
that
the systemd-timesyncd sets the time to the last known value after restart
and
syncs it from the network when on-line. Is it right?
Now, I have a shutdown timer unit, which powers the NAS off at the given
time.
On Do, 24.12.20 11:27, Mohamed Ali Fodha (fodha.mohamed@gmail.com) wrote:
> Hello,
>
> I have unmounting issues during reboot as mentioned below for
> */etc/machine-id*
> and */etc*, what could be the problem?
> For information, after the boot I got an ID in /etc/machine-id
Most likely
>>> Reindl Harald schrieb am 04.01.2021 um 14:53 in
Nachricht <49b8413f-3131-658f-e21a-a1ee448a0...@thelounge.net>:
>
> Am 04.01.21 um 13:42 schrieb Ulrich Windl:
> Germano Massullo schrieb am 27.12.2020 um
>> 14:26 in
>> Nachricht :
>>> Good day, I recently joined apcupsd (APC UPS Power
On So, 03.01.21 10:39, Dan Tihelka (dtihe...@gmail.com) wrote:
> Hello,
> I run systemd on a NAS without internal-clock-holding battery, so I think that
> the systemd-timesyncd sets the time to the last known value after restart and
> syncs it from the network when on-line. Is it right?
Yes.
>
On Mi, 23.12.20 21:47, John (gray...@archlinux.us) wrote:
> I need to have the following start
> /usr/lib/systemd/user/pulseaudio.service so it can make use of
> pulseaudio. Using a After= or Wants= does not work. What is the
> correct way to have a system service like this run a user service
>
Am 04.01.21 um 13:42 schrieb Ulrich Windl:
Germano Massullo schrieb am 27.12.2020 um
14:26 in
Nachricht :
Good day, I recently joined apcupsd (APC UPS Power Control Daemon)
package maintainers on Fedora/CentOS/RHEL.
After a power failure, apcupsd shuts down the system with a command
almost
On Do, 24.12.20 05:38, John (gray...@archlinux.us) wrote:
> On Thu, Dec 24, 2020 at 3:29 AM Andrei Borzenkov wrote:
> >
> > On Thu, Dec 24, 2020 at 5:48 AM John wrote:
> > >
> > > I need to have the following start
> > > /usr/lib/systemd/user/pulseaudio.service so it can make use of
> > >
Reindl Harald writes:
> topic missed - it makes no difference if it can hold the power 3
> minutes, 3 hours or even 3 days at the point where it decides "i need to
> shutdown everything because the battery goes empty"
It is that point that really should be at least 3 minutes before power
Reindl Harald writes:
> i have seen "user manager" instances hanging for way too long and way
> more than 3 minutes over the last 10 years
The default timeout is 3 minutes iirc, so at that point it should be
forcibly killed.
___
systemd-devel
15 matches
Mail list logo
