For those, who tried to help me, big hand.
I think I found reason. OPENSSL.
I had to edit openssl.conf, to get TRUSTEDQSL work.
/etc/pki/tls/openssl.conf, There
# Uncomment the sections that start with ## below to enable the legacy provider.
# Loading the legacy provider enables support for the f
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 comment further because ap
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 systemd-resolved.service
>
Sun, 10 Nov 2024 09:27:46 +
Barry kirjoitti:
> > 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 t
> 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 have been using the system for a lit
> 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 about the oo
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 systemd-resolved
System:
> 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/FAILURE) Main PID: 19413 (code=exited,
>>> status=1/FAILURE
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 (Muistin varaaminen ei onnistu)
>
> T
> 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 implies your do not have enough
Fri, 8 Nov 2024 01:19:34 -0500
Jeffrey Walton kirjoitti:
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 can still be
> started in the current session.
>
> If you want to permanently disa
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 can still be
started
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 status systemd-resolved
× systemd-resolved.se
> 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 unsubscribe sen
> 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 to get
> self edited dns query
On 14/04/2021 02:38, Jack Craig wrote:
On Tue, Apr 13, 2021 at 3:52 AM Tim via users mailto:users@lists.fedoraproject.org>> wrote:
On Mon, 2021-04-12 at 12:06 -0700, Jack Craig wrote:
> Oh so now I have learned something new.
>
> I thought that because I was a Domain owner, I had
On Tue, Apr 13, 2021 at 3:52 AM Tim via users
wrote:
> On Mon, 2021-04-12 at 12:06 -0700, Jack Craig wrote:
> > Oh so now I have learned something new.
> >
> > I thought that because I was a Domain owner, I had to do the
> > translation from my public IP to my local DNS name
>
> Just to be clear:
On Mon, Apr 12, 2021 at 11:54 PM J.Witvliet--- via users <
users@lists.fedoraproject.org> wrote:
>
>
>
> *From: *"Jack Craig"
> *Date:* Monday, 12 April 2021 at 21:07:07
> *To: *"Community support for Fedora users"
> *Subject:* Re: systemd-resolv
On 13/04/2021 18:52, Tim via users wrote:
You can see that sort of thing with the "dig" tool. If you do a "dig
example.com" you'll get a collection of responses. The "answer"
section is the domain name and numerical IP address for it, that you
queried. The "authority" section will be the autho
On Mon, 2021-04-12 at 12:06 -0700, Jack Craig wrote:
> Oh so now I have learned something new.
>
> I thought that because I was a Domain owner, I had to do the
> translation from my public IP to my local DNS name
Just to be clear:
By "your public IP" do mean the IP for your server that the worl
From: "Jack Craig"
mailto:jack.craig.ap...@gmail.com>>
Date: Monday, 12 April 2021 at 21:07:07
To: "Community support for Fedora users"
mailto:users@lists.fedoraproject.org>>
Subject: Re: systemd-resolved, split dns, & vpn setup
Oh so now I have learned so
Oh so now I have learned something new.
I thought that because I was a Domain owner, I had to do the translation
from my public IP to my local DNS name
in as much as networksolutions.com, my domain registrar provider, has
already the IP and host name then
I don't need to provide that so let me t
I'm answering this with a separate response because it goes off in a
different direction. You can decide which way to go without mixing up
all the information together.
On Sat, 2021-04-10 at 12:03 -0700, Jack Craig wrote:
> I think I understand that the primary name server for domain must be
> in
On Sat, 2021-04-10 at 12:03 -0700, Jack Craig wrote:
> OK time to share the real problem here ,it is me. that is to say
> after several decades of computer work I got Parkinson's and that
> forced me to stop working commercially. I didn't want to give up my
> networking all the way so I keep thi
On Sat, Apr 10, 2021 at 1:20 AM Tim via users
wrote:
> On Thu, 2021-04-08 at 13:37 -0700, Jack Craig wrote:
> > I have tried at length to get bind 9 to support proper a split
> > horizon configuration without success.
>
> I remember going through that with you last year. It definitely works,
> a
On Thu, 2021-04-08 at 13:37 -0700, Jack Craig wrote:
> I have tried at length to get bind 9 to support proper a split
> horizon configuration without success.
I remember going through that with you last year. It definitely works,
as I did it on my system as I went through it with you.
Do you hav
hi Peter,
thx very much for your time & expertise.
very much appreciated, jackc...
On Thu, Apr 8, 2021 at 4:11 PM Peter Boy wrote:
>
>
> > Am 08.04.2021 um 22:37 schrieb Jack Craig :
> >
> > This was looking like a good solution until I got down to the end of the
> second article
> > where it
> Am 08.04.2021 um 22:37 schrieb Jack Craig :
>
> This was looking like a good solution until I got down to the end of the
> second article
> where it said, if I understand this correctly, the systemD-resolveD is not
> appropriate for the primary DNS server of a domain.
Indeed, systems-reso
On 11/01/2021 03:25, Jerome Lille wrote:
On Sun, 2021-01-10 at 15:44 +0800, Ed Greshko wrote:
On 06/01/2021 00:10, Jerome Lille wrote:
I've just updated a desktop from Fedora 32 to 33 and after that the
logs are flooded with the following message
systemd-resolved[]: Using degraded feature set
On Sun, 2021-01-10 at 15:44 +0800, Ed Greshko wrote:
> On 06/01/2021 00:10, Jerome Lille wrote:
> > I've just updated a desktop from Fedora 32 to 33 and after that the
> > logs are flooded with the following message
> >
> > systemd-resolved[]: Using degraded feature set TCP instead of UDP
> > for
Ed Greshko writes:
Networkmanager must be checking if /etc/resolv.conf is a symbolic link and
only updating its own private resolver configs, otherwise it'll update them
and /etc/resolv.conf
I have no idea of what "private configs" you speak. I also can't think of
The configs in /var/run
On 10/01/2021 14:50, Ed Greshko wrote:
I also can't think of why NM would ever check if
/etc/resolv.conf was a symlink.
I actually meant to say there would be no need to check if systemd-resolved is
masked.
But, either way, that was not a very well thought out statement.
---
The key to gettin
On 06/01/2021 00:10, Jerome Lille wrote:
I've just updated a desktop from Fedora 32 to 33 and after that the
logs are flooded with the following message
systemd-resolved[]: Using degraded feature set TCP instead of UDP for
DNS server 127.0.0.1.
systemd-resolved[]: Using degraded feature set UDP
On 10/01/2021 11:04, Tim via users wrote:
Ed Greshko:
When I tested reverting to the previous behavior I simply started
with an empty /etc/resolv.conf.
No symlink. No selinux troubles. Everything just worked.
Sam Varshavchik:
Well, then how do the apps that need to talk to the DNS server fin
On 10/01/2021 12:24, Sam Varshavchik wrote:
Tim via users writes:
Ed Greshko:
>> When I tested reverting to the previous behavior I simply started
>> with an empty /etc/resolv.conf.
>> No symlink. No selinux troubles. Everything just worked.
Sam Varshavchik:
> Well, then how do the apps that
Tim via users writes:
Ed Greshko:
>> When I tested reverting to the previous behavior I simply started
>> with an empty /etc/resolv.conf.
>> No symlink. No selinux troubles. Everything just worked.
Sam Varshavchik:
> Well, then how do the apps that need to talk to the DNS server find
> it? M
Ed Greshko:
>> When I tested reverting to the previous behavior I simply started
>> with an empty /etc/resolv.conf.
>> No symlink. No selinux troubles. Everything just worked.
Sam Varshavchik:
> Well, then how do the apps that need to talk to the DNS server find
> it? Maybe something in the gli
Ed Greshko writes:
When I tested reverting to the previous behavior I simply started with an
empty /etc/resolv.conf.
No symlink. No selinux troubles. Everything just worked.
Well, then how do the apps that need to talk to the DNS server find it?
Maybe something in the glibc resolver know
On 10/01/2021 09:17, Ed Greshko wrote:
On 10/01/2021 09:12, Sam Varshavchik wrote:
Doug H. writes:
>
> Created bug 1913276 to fix no-stub-resolv.conf, the selinux policy needs to
> be fixed.
Thanks for opening that bug.
Note that my outbound e-mail was being blocked by this. I am using post
On 10/01/2021 09:12, Sam Varshavchik wrote:
Doug H. writes:
>
> Created bug 1913276 to fix no-stub-resolv.conf, the selinux policy needs to
> be fixed.
Thanks for opening that bug.
Note that my outbound e-mail was being blocked by this. I am using postfix for outbound and the smtp alerts
we
Doug H. writes:
>
> Created bug 1913276 to fix no-stub-resolv.conf, the selinux policy needs to
> be fixed.
Thanks for opening that bug.
Note that my outbound e-mail was being blocked by this. I am using postfix
for outbound and the smtp alerts were triggering for each outbound e-mail
att
On Wed, Jan 6, 2021, at 4:15 AM, Sam Varshavchik wrote:
> Jerome Lille writes:
>
> > On Tue, 2021-01-05 at 18:10 -0500, Sam Varshavchik wrote:
> > > Chris Murphy writes:
> > >
> > > > On Tue, Jan 5, 2021 at 10:32 AM Chris Murphy
> > > > wrote:
> > > > >
> > > > > Maybe this bug:
> > > >
> > > > h
Michael H. Warfield writes:
> What I do is disable systemd-resolved and fix the resolv.conf file
> to put back the original and get rid of systemd's symlink.
ALSO! Remove the "resolve [!UNAVAIL=return]" stanza for hosts in
/etc/nsswitch.conf! That seems to have been part of my problems.
Thi
On Tue, 2021-01-05 at 11:35 -0500, Tom Horsley wrote:
> On Tue, 05 Jan 2021 17:10:06 +0100
> Jerome Lille wrote:
> > What can be done?
>
> What I do is disable systemd-resolved and fix the resolv.conf file
> to put back the original and get rid of systemd's symlink.
ALSO! Remove the "resolve [!
Jerome Lille writes:
On Tue, 2021-01-05 at 18:10 -0500, Sam Varshavchik wrote:
> Chris Murphy writes:
>
> > On Tue, Jan 5, 2021 at 10:32 AM Chris Murphy
> > wrote:
> > >
> > > Maybe this bug:
> >
> > https://github.com/systemd/systemd/issues/13432
>
> "opened this issue on Aug 29, 2019"
>
> I w
On Tue, 2021-01-05 at 18:10 -0500, Sam Varshavchik wrote:
> Chris Murphy writes:
>
> > On Tue, Jan 5, 2021 at 10:32 AM Chris Murphy
> > wrote:
> > >
> > > Maybe this bug:
> >
> > https://github.com/systemd/systemd/issues/13432
>
> "opened this issue on Aug 29, 2019"
>
> I would not expect thi
Chris Murphy writes:
On Tue, Jan 5, 2021 at 10:32 AM Chris Murphy wrote:
>
> Maybe this bug:
https://github.com/systemd/systemd/issues/13432
"opened this issue on Aug 29, 2019"
I would not expect this to be fixed any time soon. The only solution is:
systemctl stop systemd-resolved
systemct
On Tue, 2021-01-05 at 10:33 -0700, Chris Murphy wrote:
> On Tue, Jan 5, 2021 at 10:32 AM Chris Murphy
> wrote:
> >
> > On Tue, Jan 5, 2021 at 9:10 AM Jerome Lille
> > wrote:
> > >
> > > Hi
> > >
> > > I've just updated a desktop from Fedora 32 to 33 and after that
> > > the
> > > logs are floo
On Tue, 2021-01-05 at 11:37 -0500, Tim Evans wrote:
> On 1/5/21 11:10 AM, Jerome Lille wrote:
>
> > This machine uses a VPN service that is always on. The file
> > /etc/resolver.conf has just one line with the nameserver from the
> > VPN
>
> You do mean /etc/resolv.conf, right?
Right
___
On Tue, Jan 5, 2021 at 10:32 AM Chris Murphy wrote:
>
> On Tue, Jan 5, 2021 at 9:10 AM Jerome Lille wrote:
> >
> > Hi
> >
> > I've just updated a desktop from Fedora 32 to 33 and after that the
> > logs are flooded with the following message
> >
> > systemd-resolved[]: Using degraded feature set
On Tue, Jan 5, 2021 at 9:10 AM Jerome Lille wrote:
>
> Hi
>
> I've just updated a desktop from Fedora 32 to 33 and after that the
> logs are flooded with the following message
>
> systemd-resolved[]: Using degraded feature set TCP instead of UDP for
> DNS server 127.0.0.1.
> systemd-resolved[]: Us
On 1/5/21 11:10 AM, Jerome Lille wrote:
This machine uses a VPN service that is always on. The file
/etc/resolver.conf has just one line with the nameserver from the VPN
You do mean /etc/resolv.conf, right?
--
Tim Evans | 5 Chestnut Court
On Tue, 05 Jan 2021 17:10:06 +0100
Jerome Lille wrote:
> What can be done?
What I do is disable systemd-resolved and fix the resolv.conf file
to put back the original and get rid of systemd's symlink.
___
users mailing list -- users@lists.fedoraproject.
There is another thread re systemd-resolved and adguard.
Ed Greshko had a solution to use /etc/resolve.conf instead of the stub file
systemd-resolved uses.
"To revert to the previous behavior you need to remove the symbolic link
lrwxrwxrwx. 1 root root 39 Sep 1 17:52 resolv.conf ->
On Sun, 15 Nov 2020 at 20:22, Tom H wrote:
> On Sun, Nov 15, 2020 at 10:15 AM Anthony F McInerney
> wrote:
>
>
> > Can someone explain why systemd-resolved needs to symlink
> > /etc/resolv.conf to 4(or more) different places, instead of just
> > having those 'detected things' as options in
> > /
On Sun, Nov 15, 2020 at 10:15 AM Anthony F McInerney
wrote:
> Can someone explain why systemd-resolved needs to symlink
> /etc/resolv.conf to 4(or more) different places, instead of just
> having those 'detected things' as options in
> /etc/systemd/resolved.conf ?
The different symlinks/files p
On Sat, 14 Nov 2020 at 19:35, Sam Varshavchik wrote:
> Anthony F McInerney writes:
>
> >Note that the selected mode of operation for this file is
> detected
> > fully automatically, depending on whether /etc/resolv.conf is a symlink
> to
> >/run/systemd/resolve/resolv.conf or list
Anthony F McInerney writes:
Note that the selected mode of operation for this file is detected
fully automatically, depending on whether /etc/resolv.conf is a symlink to
/run/systemd/resolve/resolv.conf or lists 127.0.0.53 as DNS server.
Again: why does anything have to be "det
> It is a malignant carcinoma.
Okay, seriously y'all. This over-the-top animosity is not welcome here. This
is a Fedora list, and we expect discourse to remain civil. If you don't like
it, fine.
You have a number of options, including working on a Fedora spin which
configures things differently.
No.
It is a malignant carcinoma.
From: "Tom Horsley" mailto:horsley1...@gmail.com>>
Date: Saturday, 14 November 2020 at 15:16:35
To: "users@lists.fedoraproject.org"
mailto:users@lists.fedoraproject.org>>
Subject: Re: systemd-resolved breakage
On Sat, 14 Nov
On Fri, 13 Nov 2020 at 23:42, Sam Varshavchik wrote:
> Petr Menšík writes:
>
> > Am I missing something?
>
> Yes, system is being shoved down your gullet, whether you like it or not.
>
> > would NetworkManager.conf:
> > dns=default
> >
> > Write resolv.conf again? Can I make it rewrite after disa
On Sat, 14 Nov 2020 11:56:01 +0100
Tom H wrote:
> > Yes, system is being shoved down your gullet, whether you like it
> > or not.
>
> Whichever distribution you use, you're at the mercy of its developers.
> In this particular case, the developer responsible for the change
> didn't care about br
On Sat, Nov 14, 2020 at 12:42 AM Sam Varshavchik
wrote:
> Petr Menšík writes:
>>
>> Am I missing something?
>
> Yes, system is being shoved down your gullet, whether you like it
> or not.
Whichever distribution you use, you're at the mercy of its developers.
In this particular case, the developer
Petr Menšík writes:
Am I missing something?
Yes, system is being shoved down your gullet, whether you like it or not.
would NetworkManager.conf:
dns=default
Write resolv.conf again? Can I make it rewrite after disabling
systemd-resolved? Why doesn't it restore /etc/resolv.conf on
systemd-re
On Fri, Nov 13, 2020 at 3:17 PM Petr Menšík
wrote:
>
> Sad thing is, I want Network Manager to write my resolv.conf as it
> did before. I just want systemd-resolved disabled and keep simple
> text file in /etc/resolv.conf.
>
> I haven't found automatic way to recover my system, after I do:
> syste
On Fri, Nov 13, 2020 at 2:22 PM Tom Horsley wrote:
> systemctl stop systemd-resolvd
> systemctl disable systemd-resolvd
resolved
> Edit /etc/NetworkManager/NetworkManager.conf And in the [main]
> section stick this:
>
> [main]
> dns=none
Since "/etc/NetworkManager/NetworkManager.conf" is
"%c
Sad thing is, I want Network Manager to write my resolv.conf as it did
before. I just want systemd-resolved disabled and keep simple text file
in /etc/resolv.conf.
I haven't found automatic way to recover my system, after I do:
systemctl disable --now systemd-resolved
It keep broken /etc/resolv.c
(Relatively) simple fix:
systemctl stop systemd-resolvd
systemctl disable systemd-resolvd
Edit /etc/NetworkManager/NetworkManager.conf And in the [main]
section stick this:
[main]
dns=none
Now rm -f /etc/resolv.conf
Now create your own /etc/resolv.conf file from scratch with
the nameserver and
On Tue, Nov 03, 2020 at 09:08:04AM -0600, Ian Pilcher wrote:
> On 11/2/20 10:37 AM, Jonathan Billings wrote:
> > I have a similar configuration, and at first I tried to get the
> > dnsmasq to be used by systemd-resolved but it kept "forgetting" it and
> > switching back to what DHCP used, so I just
On 11/2/20 10:37 AM, Jonathan Billings wrote:
I have a similar configuration, and at first I tried to get the
dnsmasq to be used by systemd-resolved but it kept "forgetting" it and
switching back to what DHCP used, so I just stopped, disabled and
masked systemd-resolved.service, deleted /etc/reso
On Mon, Nov 02, 2020 at 09:18:00AM -0600, Ian Pilcher wrote:
> I've been using NetworkManager's dnsmasq plugin (dns=dnsmasq) on my
> laptop for years. After upgrading to Fedora 33, I see that
> systemd-resolved is running (as expected), but the NetworkManager-
> spawned dnsmasq instance is also ru
That worked! Thanks!
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https
On 10/31/20 9:00 AM, lancelasset...@gmail.com wrote:
On 28/10/2020 11:10, Lance Lassetter wrote:
To revert to the previous behavior you need to remove the symbolic link
lrwxrwxrwx. 1 root root 39 Sep 1 17:52 resolv.conf ->
../run/systemd/resolve/stub-resolv.conf
What is the absolute path of
> On 28/10/2020 11:10, Lance Lassetter wrote:
>
> To revert to the previous behavior you need to remove the symbolic link
>
> lrwxrwxrwx. 1 root root 39 Sep 1 17:52 resolv.conf ->
> ../run/systemd/resolve/stub-resolv.conf
What is the absolute path of "resolv.conf" and
"../run/systemd/resolve/s
On 28/10/2020 11:10, Lance Lassetter wrote:
On Tue, Oct 27, 2020, 7:55 PM Neal Becker mailto:ndbeck...@gmail.com>> wrote:
Since updating to f33 today, adguard stopped working. Any thoughts on how
to configure a system to take advantage of both systemd-resolved and adguard
(or similar)?
On Tue, Oct 27, 2020, 7:55 PM Neal Becker wrote:
> Since updating to f33 today, adguard stopped working. Any thoughts on how
> to configure a system to take advantage of both systemd-resolved and
> adguard (or similar)?
>
> Thanks,
> Neal
> __
>
I don't see how adgua
> So, outside of classic Unix/Linux /etc/resolv.conf... most software does
> not treat a list of multiple DNS servers as explicitly "primary" and
> "secondary" (and so on).
Both network manager and systemd-resolved ostensibly support ordering of DNS
servers. I'm not sure why you have decided to
Once upon a time, Tom Seewald said:
> Yeah I'm not very happy that systemd-resolved seemingly does this silently
> and that I have to just restart the service for it to try again. My server is
> just a consumer router running OpenWRT which uses Dnsmasq.
So, outside of classic Unix/Linux /etc/re
I could just disable it, but given that systemd-resolved is now a default of
Fedora I thought I'd bring this up as this is having a negative impact on my
experience with Fedora 33.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe s
On Mon, 26 Oct 2020 20:30:31 -
Tom Seewald wrote:
> Yeah I'm not very happy that systemd-resolved seemingly does this silently
> and that I have to just restart the service for it to try again.
You could just disable that service, then systemd wouldn't try to
cache dns. There are about a doz
Yeah I'm not very happy that systemd-resolved seemingly does this silently and
that I have to just restart the service for it to try again. My server is just
a consumer router running OpenWRT which uses Dnsmasq.
___
users mailing list -- users@lists.fed
On 26/10/2020 18:09, Patrick O'Callaghan wrote:
At the risk of beating a dead horse, I'll be "that guy" again and point
out that F33 is as yet unreleased and any issues should be sent to the
Fedora Test list until it is released.
Well, since F33 is a GO for release on Tuesday the 27th, I think
On Mon, 2020-10-26 at 02:30 +, Tom Seewald wrote:
> After upgrading to F33 I've noticed that sometimes my current DNS server
> switches to 1.1.1.1 instead of my local DNS (192.168.1.1). This has happened
> both immediately after system boot, and once after several hours of use. For
> my conn
On 26/10/2020 10:30, Tom Seewald wrote:
After upgrading to F33 I've noticed that sometimes my current DNS server switches to 1.1.1.1 instead of my
local DNS (192.168.1.1). This has happened both immediately after system boot, and once after several hours
of use. For my connection in Network Man
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/18/2011 12:36 PM, Fedora User wrote:
> After all my kvetching, it turns out that systemd is really pretty easy
> to administer. SOME techs have a tendency to write documentation that
> is rather esoteric. I think that I likened the 49 man pages f
Uau... Good...
Em 18-11-2011 19:03, Deron Meranda escreveu:
> On Fri, Nov 18, 2011 at 3:16 PM, Tom Horsley wrote:
>> On Fri, 18 Nov 2011 15:02:11 -0500
>> Deron Meranda wrote:
>>
>>> systemctl status pcscd.service
>>>
>>> grep pcscd /lib/systemd/system/*.service
>>>
>>>
>>> Does that work, or are
On Fri, Nov 18, 2011 at 3:16 PM, Tom Horsley wrote:
> On Fri, 18 Nov 2011 15:02:11 -0500
> Deron Meranda wrote:
>
>> systemctl status pcscd.service
>>
>> grep pcscd /lib/systemd/system/*.service
>>
>>
>> Does that work, or are you asking something more?
>
> [root@zooty ~]# systemctl status pcscd.s
On Fri, 18 Nov 2011 15:02:11 -0500
Deron Meranda wrote:
> systemctl status pcscd.service
>
> grep pcscd /lib/systemd/system/*.service
>
>
> Does that work, or are you asking something more?
[root@zooty ~]# systemctl status pcscd.service
pcscd.service - PC/SC Smart Card Daemon
Loaded:
On Fri, Nov 18, 2011 at 2:55 PM, Tom Horsley wrote:
> On Fri, 18 Nov 2011 14:42:52 -0500
> So, speaking of systemd, is there any way to ask the question:
>
> "Why the heck is this service running?"
>
> If I look at my system, I see the pcscd (smartcard) service
> running.
>
> It isn't "wanted" in
On Fri, 18 Nov 2011 14:42:52 -0500
Deron Meranda wrote:
> Yes, the man pages are pretty dense to just jump into.
So, speaking of systemd, is there any way to ask the question:
"Why the heck is this service running?"
If I look at my system, I see the pcscd (smartcard) service
running.
It isn't
> is rather esoteric. I think that I likened the 49 man pages for systemd
> to Talmudic study.
Yes, the man pages are pretty dense to just jump into.
There are other easier documentation though:
The Fedora online manual:
http://fedoraproject.org/wiki/Systemd
The SysV to Systemd cheat sheet:
On 11/19/2011 12:06 AM, Fedora User wrote:
> This could use a graphical application to create the necessary links. I
> was lost because of being accustomed to SysV for more than a decade. My
> concern is that a new user migrating from windows would be equally
> lost. This could also use a SIMPLE g
On 11/18/2011 10:36 AM, Fedora User wrote:
> I think that I likened the 49 man pages for systemd
> to Talmudic study.
I wouldn't go quite that far. I haven't examined those pages, yet,
because I haven't moved from F 14 to F 16, yet. (I'll probably do my
laptop on Sunday, followed by the desk
95 matches
Mail list logo
