w.perplexity.ai/search/show-systemd-services-in-order-4NjYypTrQ0O6Ay6JLjYXVg
poc
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedorapr
ey
>> were stopped?
>>
>
> I'm not on a machine with systemd at the moment but systemd-analyze looks
> like it should help.
>
>
> https://serverfault.com/questions/617398/is-there-a-way-to-see-the-execution-tree-of-systemd
> https://www.baeldung.com/linux/systemd
On Tue, 17 Dec 2024 at 11:13, Dario Lesca wrote:
> What is the best way to show a list of services, in order of they were
> started
>
> And what is the best way to show a list of services, in order of they
> were stopped?
>
I'm not on a machine with systemd at the mom
What is the best way to show a list of services, in order of they were
started
And what is the best way to show a list of services, in order of they
were stopped?
Many thanks
--
Dario Lesca
(Inviato dal mio Linux Fedora 40 Workstation)
--
___
On Wed, Dec 04, 2024 at 08:29:52PM -0500, Jeffrey Walton wrote:
> On Wed, Dec 4, 2024 at 8:16 PM Patrick Mansfield via users
> wrote:
> >
> > On Wed, Dec 04, 2024 at 10:32:48AM -0800, Samuel Sieb wrote:
> > > If you aren't using any containers, then it should be fine to remove. If
> > > it's only
On 5/12/24 12:29, Jeffrey Walton wrote:
On Wed, Dec 4, 2024 at 8:16 PM Patrick Mansfield via users
wrote:
On Wed, Dec 04, 2024 at 10:32:48AM -0800, Samuel Sieb wrote:
If you aren't using any containers, then it should be fine to remove. If
it's only a recommends, then you could probably just u
On Wed, Dec 4, 2024 at 8:16 PM Patrick Mansfield via users
wrote:
>
> On Wed, Dec 04, 2024 at 10:32:48AM -0800, Samuel Sieb wrote:
> > If you aren't using any containers, then it should be fine to remove. If
> > it's only a recommends, then you could probably just uninstall qemu anyway.
> > Why is
On Wed, Dec 04, 2024 at 10:32:48AM -0800, Samuel Sieb wrote:
> If you aren't using any containers, then it should be fine to remove. If
> it's only a recommends, then you could probably just uninstall qemu anyway.
> Why is it a problem to have qemu installed?
I'd rather not have software installed
On 12/4/24 9:59 AM, Patrick Mansfield via users wrote:
On Wed, Dec 04, 2024 at 10:44:00AM -0500, Todd Zullinger wrote:
Dave Close wrote:
Patrick Mansfield wrote:
Why does the most recent systemd update pull in qemu?
That seems excessive.
Currently running Fedora 41 with systemd version
On Wed, Dec 04, 2024 at 10:44:00AM -0500, Todd Zullinger wrote:
> Dave Close wrote:
> > Patrick Mansfield wrote:
> >
> >> Why does the most recent systemd update pull in qemu?
> >> That seems excessive.
> >>
> >> Currently running Fedora 41 with
Dave Close wrote:
> Patrick Mansfield wrote:
>
>> Why does the most recent systemd update pull in qemu?
>> That seems excessive.
>>
>> Currently running Fedora 41 with systemd version 256.8-1,
>> looks like the update moves me to systemd version
>
Patrick Mansfield wrote:
>Why does the most recent systemd update pull in qemu?
>That seems excessive.
>
>Currently running Fedora 41 with systemd version 256.8-1, looks like
>the update moves me to systemd version 256.9-2.
My two systems running F41 include systemd 256.9-2 and
Why does the most recent systemd update pull in qemu?
That seems excessive.
Currently running Fedora 41 with systemd version 256.8-1, looks like the update
moves me
to systemd version 256.9-2.
-- Patrick
--
___
users mailing list -- users
> On 28 Nov 2024, at 14:40, polak...@niif.hu wrote:
>
> This would make restarting less trouble because the system will *work* with
> the old configuration.
I do not think it will allow for this.
Better that you get into the habit of checking the config after any change you
make.
Otherwise a
> On 28 Nov 2024, at 14:40, polak...@niif.hu wrote:
>
> On the one hand, it is possible to check the configuration before starting,
> e.g. "sshd -t".
I am not sure what you expect this to help with.
If the config is bad the service will not start.
That is, I assume, exactly what having the s
Hi,
Novice question: A service that can be run under systemd is given.
On the one hand, it is possible to check the configuration before starting,
e.g. "sshd -t".
I would like a systemd configuration file that contains the configuration check.
For this, the '[Service] ExecStart
points, systemd-resolved stops
working. BUT Trustedqsl works and I need that working..
So, Now my choise is comment those out and use system-resolved
as masked, and use self edited resolv.conf
So, my point of vew, problem SOLVED. Another thing is, vhen TQSL
corrects program to follow these new O
Sun, 10 Nov 2024 07:44:54 -0500
Jonathan Billings kirjoitti:
>> Sadly, your excerpt from the journal starts *just* after anything
> useful might have been recorded. It’s just systemd noise about the
> service not failing and how it isn’t restarting it.
>
> But I can’t comme
On Nov 10, 2024, at 03:04, jarmo wrote:
>
> I see no network, after starting computer, which I do very seldom,
> only when there comes kernel update.
> So network does not start at all and when doing journal query I get
> this, what I sent before...
>
> journalctl -xeu sys
worth running memtest diagnostic to eliminate RAM issues.
>
> Barry
When I upgraded into F41, everything worked fine, no problem.
But afterward came some updates, started this systemd-resolved
problem.
I think, if there is HW problem, it should effect also, when I'm using
th
> On 10 Nov 2024, at 08:04, jarmo wrote:
>
> I see no network, after starting computer
What does `ip addr` report when you have “no network”?
I wonder if you have a hardware problem?
Might be worth running memtest diagnostic to eliminate RAM issues.
Barry
--
__
Fri, 8 Nov 2024 23:14:57 +
Barry kirjoitti:
> > On 8 Nov 2024, at 13:19, jarmo wrote:
> >
> > Had to install inxi first :)
>
> Thanks for the info.
>
> Do you see systemd-resolved failing immediately after you first login?
> Or does if fail after you
> On 8 Nov 2024, at 13:19, jarmo wrote:
>
> Had to install inxi first :)
Thanks for the info.
Do you see systemd-resolved failing immediately after you first login?
Or does if fail after you have been using the system for a little while?
After it fails do you see any journal logs
On Fri, 2024-11-08 at 01:19 -0500, Jeffrey Walton wrote:
> Disabling a service only lasts until the next (re)boot. And it does
> not stop currently executing services, and the service can still be
> started in the current session.
Not quite the full picture, not in general, even if that was a spec
Fri, 8 Nov 2024 12:58:16 +
Barry Scott kirjoitti:
>
> I asked for `inxi -Fzxx` that will provide a lot of info beyond RAM
> can you provide that?
>
> FYI I use `free -h` so that the numbers are easier to read.
>
> Barry
Had to install inxi first :)
Below is with sys
> On 8 Nov 2024, at 09:44, jarmo wrote:
>
> Fri, 8 Nov 2024 09:06:46 +
> Barry kirjoitti:
>
>>> On 8 Nov 2024, at 06:02, jarmo wrote:
>>>
>>> Process: 19413 ExecStart=/usr/lib/systemd/systemd-resolved
>>> (code=exited, status=1/
Fri, 8 Nov 2024 09:06:46 +
Barry kirjoitti:
> > On 8 Nov 2024, at 06:02, jarmo wrote:
> >
> > Process: 19413 ExecStart=/usr/lib/systemd/systemd-resolved
> > (code=exited, status=1/FAILURE) Main PID: 19413 (code=exited,
> > status=1/FAILURE) Error: 12
> On 8 Nov 2024, at 06:02, jarmo wrote:
>
> Process: 19413 ExecStart=/usr/lib/systemd/systemd-resolved (code=exited,
> status=1/FAILURE)
> Main PID: 19413 (code=exited, status=1/FAILURE)
> Error: 12 (Muistin varaaminen ei onnistu)
This is ENOMEM and that implie
ant to permanently disable the service, you must mask it.
>
> Also see the systemctl docs,
> <https://www.freedesktop.org/software/systemd/man/latest/systemctl.html>.
>
> Jeff
Don't get me wrong, I want that service also working, but
I have no idea, how to do.
So I made thi
On Fri, Nov 8, 2024 at 1:02 AM jarmo wrote:
> [...]
>
> So, I disable systemd-resolved and manually create /etc/resolv.conf
> to get my network working.
Disabling a service only lasts until the next (re)boot. And it does
not stop currently executing services, and the service
Thu, 7 Nov 2024 22:10:31 +
Barry kirjoitti:
> > On 7 Nov 2024, at 17:31, Barry wrote:
> >
> > What is the output of systemctl status systemd-networkd?
>
> Sorry i mean the output of systemctl status systemd-resolved !
>
> Barry
>
systemctl
> On 7 Nov 2024, at 17:31, Barry wrote:
>
> What is the output of systemctl status systemd-networkd?
Sorry i mean the output of systemctl status systemd-resolved !
Barry
--
___
users mailing list -- users@lists.fedoraproject.org
To un
> On 7 Nov 2024, at 15:08, jarmo wrote:
>
> Won't start, claims something about memory,
> sorry, can't specify, made local resolv.conf
> to get network running..
What is the output of systemctl status systemd-networkd?
>
> It is enabled by default, I disabled
Won't start, claims something about memory,
sorry, can't specify, made local resolv.conf
to get network running..
It is enabled by default, I disabled to get
self edited dns query working..
Fedora 41 xfce4
Jarmo
--
___
users mailing list -- users@lists
On 10/29/24 14:10, ToddAndMargo via users wrote:
On 10/29/24 14:01, ToddAndMargo via users wrote:
Hi All,
Fedora 39
Which should I have?
systemd-standalone-sysusers or systemd?
Just checked my Xfce Live USB. It is systemd
Cancel the request. It is an issue with lightdm. I replace
it
On 10/29/24 17:27, ToddAndMargo via users wrote:
Hi All,
Fedora 39
systemd-254.19-1.fc39.x86_64 (provides systemd-sysusers)
I can not get lightdm to start Xfc or MATE. After
entering my password into the greeter, I get a black
screen with a mouse pointer, then back to the greeter.
When I
Hi All,
Fedora 39
systemd-254.19-1.fc39.x86_64 (provides systemd-sysusers)
I can not get lightdm to start Xfc or MATE. After
entering my password into the greeter, I get a black
screen with a mouse pointer, then back to the greeter.
When I start lighdm, it see
Failed to start systemd
On 10/29/24 14:01, ToddAndMargo via users wrote:
Hi All,
Fedora 39
Which should I have?
systemd-standalone-sysusers or systemd?
Just checked my Xfce Live USB. It is systemd
--
___
users mailing list -- users@lists.fedoraproject.org
To
Hi All,
Fedora 39
Which should I have?
systemd-standalone-sysusers or systemd?
# dnf install systemd-standalone-sysusers --allowerasing
Last metadata expiration check: 0:14:46 ago on Tue 29 Oct 2024 01:43:41
PM PDT.
Dependencies resolved
> On 16 Sep 2024, at 19:51, Robert McBroom via users
> wrote:
>
> As more and more things get fed into systemd, is there a resource to
> actually follow using it?
You mean documentation?
There are the man pages that are a good reference.
If you start with the this one
h
As more and more things get fed into systemd, is there a resource to
actually follow using it?
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct
On Sat, 10 Aug 2024 15:27:05 -0400
Todd Zullinger wrote:
> I wrote:
> > These files are marked %ghost to prevents them from being
> > removed *if they existed and were modified* prior to commit
> > 4c7acde (Do not remove modified config files, 2023-12-13)¹
> > on th
I wrote:
> These files are marked %ghost to prevents them from being
> removed *if they existed and were modified* prior to commit
> 4c7acde (Do not remove modified config files, 2023-12-13)¹
> on the f40 branch of the systemd package.
>
> ¹ https://src.fedoraproject.org/rpms
k into it more closely...
These files are marked %ghost to prevents them from being
removed *if they existed and were modified* prior to commit
4c7acde (Do not remove modified config files, 2023-12-13)¹
on the f40 branch of the systemd package.
¹ https://src.fedoraproject.org/rpms/systemd/c/4c7acde
--
a crashdump in /var/spool/abrt/ directory after I install the debuginfo
> > package - although it did before...
> >
> > I had an idea that some limits for systemd-coredump might need to be
> > increased. But I'm surprised and I can't explain why the configuration
>
did before...
I had an idea that some limits for systemd-coredump might need to be
increased. But I'm surprised and I can't explain why the configuration
files of the systemd daemon are completely missing in the system - those
under the /etd/systemd/ directory (system.conf, us
My actual problem is other: I want somehow debug program (ISC bind
daemon) crashes. And I'm trying to figure out why abrt doesn't create
a crashdump in /var/spool/abrt/ directory after I install the debuginfo
package - although it did before...
I had an idea that some limits f
. I threw in the towel and just edited
/lib/systemd/system/httpd.service and commented this setting out, entirely,
to finally fix this issue, and happy git pushing resumed.
But how do I fix this so that the next apache update doesn't clobber this?
I think a better choice is to leave the sy
and "false",
>> but if so, what's "ProtectHome=yes" is all about?
>
> I'd suggest reporting a documentation bug. It's the only
> way this will ever be clarified. I think people generally
> don't bother reporting this kind of thing (and I inc
On Wed, 2024-06-05 at 06:41 -0400, Sam Varshavchik wrote:
> Good luck finding where this is documented in the
> man pages, for overrides. There were barrels of laughs in
> systemd.exec(5).
> First, there are several instances of "ProtectHome=yes" sprinkled in
> random
> places. Then, when you
Felix Miata writes:
> I tried using
> systemctl edit httpd
> And putting this in there:
> [Service]
> ProtectHome=
> However this apparently did not work.
Please show us the override file in /etc/systemd* that resulted from your
edits.
Using systemctl edit for for
it tried to write to the git repo.
> Amusing.
> To make a long story short, the culprit was:
> ProtectHome=read-only
> in /lib/systemd/system/httpd.service,(the git repo was in a directory inside
> a mounted /home partition).
> I tried using
> systemctl edit h
it tried to write to the git repo.
>
> Amusing.
>
> To make a long story short, the culprit was:
>
> ProtectHome=read-only
>
> in /lib/systemd/system/httpd.service,(the git repo was in a directory inside
> a mounted /home partition).
>
> I tried using
>
S when it tried to write to the git repo.
>
> Amusing.
>
> To make a long story short, the culprit was:
>
> ProtectHome=read-only
>
> in /lib/systemd/system/httpd.service,(the git repo was in a directory
> inside
> a mounted /home partition).
>
> I tried using
e failing.
>
> Eventually I succeeded in stracing the httpd process sto capture the
> request. It was getting an EROFS when it tried to write to the git repo.
>
> Amusing.
>
> To make a long story short, the culprit was:
>
> ProtectHome=read-only
>
> in /lib/systemd/s
culprit was:
ProtectHome=read-only
in /lib/systemd/system/httpd.service,(the git repo was in a directory inside
a mounted /home partition).
I tried using
systemctl edit httpd
And putting this in there:
[Service]
ProtectHome=
However this apparently did not work. I threw in the towel and
> On 12 Apr 2024, at 05:42, Mike Wright wrote:
>
> Reason is because .socket files will activate their corresponding service
> files REGARDLESS of masking or disabling.
A masked service cannot do anything as masking replaced it with /dev/null.
Barry
--
__
> On 11 Apr 2024, at 12:59, Sam Varshavchik wrote:
>
> What I do see, though, is that we have both NetworkManager-wait-online and
> systemd-networkd-wait-online. Why do we need both of them?
It's odd that both are enabled.
On my kde plasma Vm only NetworkManager-wait-
On 4/11/24 15:08, Jeffrey Walton wrote:
On Thu, Apr 11, 2024 at 6:01 PM Sam Varshavchik wrote:
Tim via users writes:
"The service systemd-networkd-wait-online.service invokes systemd-
networkd-wait-online without any options. Thus, it waits for all
managed interfaces to be configur
On Thu, Apr 11, 2024 at 6:01 PM Sam Varshavchik wrote:
>
> Tim via users writes:
>
> > "The service systemd-networkd-wait-online.service invokes systemd-
> > networkd-wait-online without any options. Thus, it waits for all
> > managed interfaces to be configured or
Tim via users writes:
"The service systemd-networkd-wait-online.service invokes systemd-
networkd-wait-online without any options. Thus, it waits for all
managed interfaces to be configured or failed, and for at least one to
be online."
Could it be that you have some additional
On Thu, 2024-04-11 at 07:59 -0400, Sam Varshavchik wrote:
> What I do see, though, is that we have both NetworkManager-wait-
> online and systemd-networkd-wait-online. Why do we need both of them?
>
> I simply disabled systemd-networkd-wait-online, and that seems to
> so
Roger Heflin writes:
Run this:
systemd-analyze critical-chain network-online.target
Can you explain why you think inspecting dependencies and starting times of
different systemd units would have any bearing on why a single unit, systemd-
network, is blowing chunks? Wasn't it clear fr
Run this:
systemd-analyze critical-chain network-online.target
On Wed, Apr 10, 2024 at 6:20 AM Sam Varshavchik wrote:
>
> Samuel Sieb writes:
>
> > I have a similar problem where the wait-online service suddenly started
> > taking a very long time and then failing. My sys
Samuel Sieb writes:
I have a similar problem where the wait-online service suddenly started
taking a very long time and then failing. My system that used to boot in a
few seconds now takes over a minute. So I have two questions.
What is it waiting for? My main ethernet card gets an addre
dress, and I determined that
> keepalived simply started after quite a bit of time elapsed before systemd
> deemed it necessary to start keepalived. And when I tried to figure out
> why's that, I discovered this to be the culprit.
You say that networking is working, but is whatev
On Tue, 2024-04-09 at 23:20 -0700, Samuel Sieb wrote:
> Perhaps more importantly, why can't that happen in the background? Why
> does gdm care if the network is connected?
It'd need to be *if* people are using a network share for their
homespace, or other "expected to be there" directories.
And
On 4/9/24 19:12, Sam Varshavchik wrote:
I've been made aware that it takes two minutes for
systemd-networkd-wait-online.service to spin its wheels, before giving
up with a squeal:
Apr 09 22:03:30 shorty.email-scan.com systemd[1]: Starting
systemd-networkd-wait-online.service - Wai
On Tue, 2024-04-09 at 22:12 -0400, Sam Varshavchik wrote:
> I've been made aware that it takes two minutes for systemd-networkd-wait-
> online.service to spin its wheels, before giving up with a squeal:
>
> Apr 09 22:03:30 shorty.email-scan.com systemd[1]: Starting
> s
I've been made aware that it takes two minutes for systemd-networkd-wait-
online.service to spin its wheels, before giving up with a squeal:
Apr 09 22:03:30 shorty.email-scan.com systemd[1]: Starting
systemd-networkd-wait-online.service - Wait for Network to be Configured…
Apr 09 22:
> On 8 Mar 2024, at 07:39, Michael D. Setzer II via users
> wrote:
>
> Long ago use to use multiple name servers including 8.8.8.8, but
> then at somepoint it changed to the 127.0.0.53 thing.
That means that systemd-resolved is being used.
Have you configured systemd-resolved
Currently in Nevada accessing 4 of my computers back in Guam.
Has been working fine, until earlier today.
VNC into the machines using same name of router, but different
ports mapped to machines.
Generally login to each one, and then next with no problem.
But today, got error messages that couldn
On Fri Sep29'23 11:44:08PM, Samuel Sieb wrote:
> From: Samuel Sieb
> Date: Fri, 29 Sep 2023 23:44:08 -0700
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users
> Subject: Re: F38: systemd-resolved.service oddity
>
> On 9/29/23 20:58, Ranja
On Fri Sep29'23 11:44:08PM, Samuel Sieb wrote:
> From: Samuel Sieb
> Date: Fri, 29 Sep 2023 23:44:08 -0700
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users
> Subject: Re: F38: systemd-resolved.service oddity
>
> On 9/29/23 20:58, Ranja
On 9/29/23 20:58, Ranjan Maitra wrote:
Thanks!
On 9/28/23 19:03, Ranjan Maitra wrote:
On Thu Sep28'23 10:32:55AM, Samuel Sieb wrote:
The problem is that the VPN is setting its options on the global state
instead of the tunnel where they should be. Normally, when the tunnel goes
away, so do
Thanks!
> On 9/28/23 19:03, Ranjan Maitra wrote:
> > On Thu Sep28'23 10:32:55AM, Samuel Sieb wrote:
> > > The problem is that the VPN is setting its options on the global state
> > > instead of the tunnel where they should be. Normally, when the tunnel
> > > goes
> > > away, so do the special s
On 9/28/23 19:03, Ranjan Maitra wrote:
On Thu Sep28'23 10:32:55AM, Samuel Sieb wrote:
The problem is that the VPN is setting its options on the global state
instead of the tunnel where they should be. Normally, when the tunnel goes
away, so do the special settings for it, but here they're globa
On Thu Sep28'23 10:32:55AM, Samuel Sieb wrote:
> From: Samuel Sieb
> Date: Thu, 28 Sep 2023 10:32:55 -0700
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users
> Subject: Re: F38: systemd-resolved.service oddity
>
> On 9/28/23
On Thu Sep28'23 10:32:55AM, Samuel Sieb wrote:
> From: Samuel Sieb
> Date: Thu, 28 Sep 2023 10:32:55 -0700
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users
> Subject: Re: F38: systemd-resolved.service oddity
>
> On 9/28/23
2 (enp57s0u2u1u1): [ISP]
After $ sudo systemctl restart systemd-resolved.service
$ resolvectl dns
Global:
Link 2 (enp57s0u2u1u1): [Same as {**}]
$ resolvectl domain
Global:
Link 2 (enp57s0u2u1u1): [ISP]
Seems to me there is something "sticky" about the VPN connection?
The
Thank you!
On Wed Sep27'23 03:04:53PM, Samuel Sieb wrote:
> From: Samuel Sieb
> Date: Wed, 27 Sep 2023 15:04:53 -0700
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users
> Subject: Re: F38: systemd-resolved.service oddity
>
> On 9/27/23
On 9/27/23 09:14, Ranjan Maitra wrote:
From the past week, I have had an issue in that after several hours, some
particular sites become inaccessible to me, and can only be accessed if I use
restart using sudo systemctl restart systemd-resolved.service
What particular issues cause this? Why
wrote:
> From: Joe Zeff
> Date: Wed, 27 Sep 2023 10:24:00 -0600
> To: users@lists.fedoraproject.org
> Reply-To: Community support for Fedora users
> Subject: Re: F38: systemd-resolved.service oddity
>
> On 09/27/2023 10:14 AM, Ranjan Maitra wrote:
> > From the past week, I
On 09/27/2023 10:14 AM, Ranjan Maitra wrote:
From the past week, I have had an issue in that after several hours, some
particular sites become inaccessible to me, and can only be accessed if I use
restart using sudo systemctl restart systemd-resolved.service
Before any of us can help you
Dear friends,
From the past week, I have had an issue in that after several hours, some
particular sites become inaccessible to me, and can only be accessed if I use
restart using sudo systemctl restart systemd-resolved.service
What particular issues cause this? Why did it start a week ago
ich lines journalctl wants to highlight, but not their
> > status. That isn't optimal, but the horrible dark blue on black
> > background is gone, so I can live with it.
>
> I would be nice to be able to configure the colours used. Would need
> a PR against systemd I expec
or color then seems to
> highlight the ESC in light red, so I know which lines journalctl wants
> to highlight, but not their status. That isn't optimal, but the
> horrible dark blue on black background is gone, so I can live with it.
I would be nice to be able to configure the col
ng to
> priority: lines of level ERROR and higher are colored red;
> lines of level NOTICE and higher are highlighted;
> lines of level DEBUG are colored lighter grey; other lines are
> displayed normally.
>
> would be nice to be able to customize those & if &#x
vel NOTICE and higher are highlighted;
lines of level DEBUG are colored lighter grey; other lines are
displayed normally.
would be nice to be able to customize those & if 'systemd'
delegates declaration of that 'highlighting' colour then
these below do not do it:
a) t
On Wed, 28 Jun 2023 11:10:05 -0700
stan wrote:
> On Wed, 28 Jun 2023 10:17:45 -0700
> stan via users wrote:
>
> > On Wed, 28 Jun 2023 17:08:38 +0100
> > Patrick O'Callaghan wrote:
>
> > > See also 'man journalctl' and search for PAGER.
> >
> > This is also relevant. Unfortunately, it
On Wed, 28 Jun 2023 10:17:45 -0700
stan via users wrote:
> On Wed, 28 Jun 2023 17:08:38 +0100
> Patrick O'Callaghan wrote:
> > See also 'man journalctl' and search for PAGER.
>
> This is also relevant. Unfortunately, it seems that journalctl
> ignores the input of SYSTEMD_LESS. It is hard
eczek via users wrote:
> > > > Hi guys.
> > > >
> > > > I wonder if somebody might know how to customize, to change
> > > > systemd journal's colours?
> > > > I'm specifically thinking of changing 'WARN' warnings wh
On Wed, 2023-06-28 at 08:37 -0700, stan via users wrote:
> On Wed, 28 Jun 2023 15:01:06 +0100
> Patrick O'Callaghan wrote:
>
> > On Wed, 2023-06-28 at 15:32 +0200, lejeczek via users wrote:
> > > Hi guys.
> > >
> > > I wonder if somebody might
On Wed, 28 Jun 2023 15:01:06 +0100
Patrick O'Callaghan wrote:
> On Wed, 2023-06-28 at 15:32 +0200, lejeczek via users wrote:
> > Hi guys.
> >
> > I wonder if somebody might know how to customize, to change
> > systemd journal's colours?
> > I'm s
On Wed, 28 Jun 2023 15:32:12 +0200
lejeczek via users wrote:
> Hi guys.
>
> I wonder if somebody might know how to customize, to change
> systemd journal's colours?
> I'm specifically thinking of changing 'WARN' warnings which
> get - in my opinion u
On Wed, 2023-06-28 at 15:32 +0200, lejeczek via users wrote:
> Hi guys.
>
> I wonder if somebody might know how to customize, to change
> systemd journal's colours?
> I'm specifically thinking of changing 'WARN' warnings which
> get - in my opinion u
Hi guys.
I wonder if somebody might know how to customize, to change
systemd journal's colours?
I'm specifically thinking of changing 'WARN' warnings which
get - in my opinion unfortunate, for I use other than white
background colours - painted in yell
On 4/30/23 14:25, Jonathan Ryshpan wrote:
Here is an extract from the system log (a fuller extract is attached):
Mar 18 07:57:56 OaklandWeather.localdomain systemd[1]: Started
noip-duc.service - No-IP Dynamic Update Client.
Mar 18 07:57:58 OaklandWeather.localdomain systemd[1]: noip-duc.service
s
rc.local to a systemd unit which "helpfully" killed things that
were taking "too long", so I switched to an "at" command to run
a different script "now", and moved all my delays into the different
script (which is now running out from under the thumb of systemd)
I have something like this in my rc.local for similar reasons.
( sleep 30 ; cd /someplace ; ) &
On Mon, May 1, 2023 at 4:41 PM Tom Horsley wrote:
>
> On Mon, 01 May 2023 13:39:29 -0700
> Jonathan Ryshpan wrote:
>
> > And the problem remains. Further advice would be welcome.
>
> Without ever mana
1 - 100 of 1489 matches
Mail list logo
