17.06.2020 07:46, Kamal Rathi пишет:
>> Please take at least some efforts to format mail so that it can be
>> properly understood. Otherwise I am afraid your mails will simply be
>> ignored.
>
>I am sorry for inconvenience, i will try to follow correct approach
> afterwards while replying
>Please take at least some efforts to format mail so that it can be
>properly understood. Otherwise I am afraid your mails will simply be
>ignored.
I am sorry for inconvenience, i will try to follow correct approach
afterwards while replying
> How RemainAfterExit affects *startup* of
Done: https://github.com/systemd/systemd/issues/16193
On Tue, Jun 16, 2020 at 10:50 AM Lennart Poettering
wrote:
> On Mi, 10.06.20 18:24, Stanislav Angelovič (angelovi...@gmail.com) wrote:
>
> > Hi folks,
> >
> > sdbus-c++, a C++ library on top of sd-bus, is based on plain sd-bus
> > messages
On Fr, 05.06.20 15:29, Lennart Poettering (lenn...@poettering.net) wrote:
> On Do, 04.06.20 16:58, Tobias Hunger (tobias.hun...@gmail.com) wrote:
>
> > Poking around a bit more: I have 4096 unused sectors before the first
> > partiton instead of just 2048. Systemd-repart then tries to put all my
On Mo, 15.06.20 03:01, Kamal Rathi (kr30ap...@gmail.com) wrote:
> Hi Team,
>
> I have two services which are dependent on each other and are working fine
> at boot up but at shutdown / reboot , the processes get killed as shutdown
> got initated.
My educated guess is that your services use "su"
On Mo, 01.06.20 19:11, Chris Murphy (li...@colorremedies.com) wrote:
> dmesg shows this:
>
> [ 22.947118] systemd-journald[629]: File
> /var/log/journal/26336922e1044e80ae4bd42e1d6b9099/user-1000.journal
> corrupted or uncleanly shut down, renaming and replacing.
journald itself logs about
On Mi, 10.06.20 18:24, Stanislav Angelovič (angelovi...@gmail.com) wrote:
> Hi folks,
>
> sdbus-c++, a C++ library on top of sd-bus, is based on plain sd-bus
> messages to implement the concept of Variant type. Under plain message here
> I mean one created via `sd_bus_message_new` with the type
On Fr, 05.06.20 14:42, Tomáš Pecka (pecka...@fit.cvut.cz) wrote:
> Hello,
>
> we are currently working on a project where we'd like to let users know
> the health status of the system's services. The health status is
> supposed to be considered as "is every unit in systemd ok?".
> For example,
On 16/06/2020 10:08, Lennart Poettering wrote:
On Mo, 25.05.20 16:19, Thomas HUMMEL (thomas.hum...@pasteur.fr) wrote:
Hello,
the point below has been buried at the end one of a previous thread. So feel
free to ignore it if you find it irrelevant.
With systemd-239 on linux 4.18.0 (CentOS
On Mi, 03.06.20 17:51, seshu pyla (seshu.p...@gmail.com) wrote:
> Hi,
>
>
>
> I am trying the below logind parameters to configure session lock in my
> system.
>
>
>
> /etc/systemd/logind.conf
>
> IdleAction=Lock
>
> IdleActionSec=1min
>
>
>
> But, with above configurations there is no effect, so
On Sa, 30.05.20 18:02, PGNet Dev (pgnet@gmail.com) wrote:
> IS there a backport of this^^ fix available for v234 that popped up in
> the meantime?
>
> If not, as is likely, is there a "safe" workaround for quieting the
> fail, and rm'ing the associated boot delay? Is rm'ing
On Di, 16.06.20 11:22, darkpenguin (darkpeng...@yandex.com) wrote:
> I would be able to figure it out if systemd told me what is going on.
> This is my main point - maybe it should tell us immediately that "this
> process is stalling the shutdown" or "this thing reloads me too much"?
> And
On Fr, 29.05.20 00:31, Nuno Reis (nr...@wavecom.pt) wrote:
> > I've noticed that if I give the same CPUScheduling options to the
> > 'systemd-nspawn@'.service service on the Fedora 32 hosting
> > system I don't have the following error anymore in the container:
> > Failed at step SETSCHEDULER
On Mo, 25.05.20 16:19, Thomas HUMMEL (thomas.hum...@pasteur.fr) wrote:
> Hello,
>
> the point below has been buried at the end one of a previous thread. So feel
> free to ignore it if you find it irrelevant.
>
> With systemd-239 on linux 4.18.0 (CentOS 8.1), why does hostnamectl --static
>
On Sa, 23.05.20 15:07, Antoine Pietri (antoine.piet...@gmail.com) wrote:
> Hi,
>
> I have a setup where my NFS server exports its /export/nfsroot for my
> diskless clients.
> To ease the deployment of this nfsroot, I'd like to be able to run
> ansible roles directly in there to install the
On Mi, 20.05.20 11:15, Robert Kudyba (rkud...@fordham.edu) wrote:
> One more question, any reason for these error messages in the logs after
> restarting systemd-logind?
>
> May 20 11:12:50 secondary systemd-logind[382684]: New seat seat0.
> May 20 11:12:50 secondary systemd-logind[382684]: User
On Sa, 16.05.20 10:31, Jaime (enopa...@gmail.com) wrote:
> I have a simple non-looping shell script that I call every 60 seconds
> using a systemd service and associated timer. My shell script produces
> no output at all. My journal looks like this:
>
> May 15 03:43:00 server systemd[450]:
On Do, 30.04.20 13:40, Reindl Harald (h.rei...@thelounge.net) wrote:
>
> the cpu time of 672ms is wrong, memory is missing in Fedora 31 while it
> was there in previous versions though it's a oneshot service
Is this supposed to be a bug report? Please report bugs along with a
minimal reproducer
On Mi, 13.05.20 08:34, darkpenguin (darkpeng...@yandex.com) wrote:
> I had trouble trying to paste a 70M text file to fpaste.org; here is the
> gzipped log of the shutdown process instead ('zcat journal.gz | less'
> works where other ways don't).
>
> >> Instead of 90 seconds of "Waiting for
On Tue, Jun 16, 2020 at 4:13 AM Roman Odaisky wrote:
> Hi,
>
> I would like to assign a static IP address to a server in a way that
> survives
> hardware replacement. Basically I want the configuration to say: “Find the
> only
> physical interface present and assign this static IP address to it.
On Di, 21.04.20 10:40, Damian Ivanov (damianator...@gmail.com) wrote:
> Hi,
>
> After bootstrapping os and mariadb into $DIR
> I booted the machine with:
> systemd-nspawn -D $DIR -b --resolv-conf=bind-host --capability=all
> I had to remove $DIR/etc/resolv.conf first as bind-host seems to fail
On Sa, 13.06.20 04:56, Ed Strong (onkyonk...@outlook.com) wrote:
> Hello! As of about a week ago udev cannot start, journalctl -xe gives the
> below output. The stack trace references the glibc library but not sure if
> red herring or not. Any ideas on how to troubleshoot this would be most
>
22 matches
Mail list logo
