Re: suspend doesn't lock

On most keyboards, near the left ALT key, there is a key with a "Windows" logo on it. It is called "Meta" or "Super" key in Linux. Super+L means press "Super" key and the "L" key at the same time. ___ users mailing list -- users@lists.fedoraproject.org

Re: on to letsencrypt

i'll do it first thing in the am and report results. THANKS!!! On Tue, Apr 20, 2021 at 8:02 PM Ed Greshko wrote: > On 21/04/2021 10:27, Jack Craig wrote: > > named.service > > > > it? > > ps -eaf | grep named > > named1263562 1 0 13:59 ?00:00:05 /usr/sbin/named > -

Re: on to letsencrypt

On 21/04/2021 10:27, Jack Craig wrote: named.service it? ps -eaf | grep named named    1263562       1  0 13:59 ?        00:00:05 /usr/sbin/named -u named -c /etc/named.conf -4 root     1280487  311233  0 19:09 pts/0    00:00:00 grep --color=auto named It almost sounds as i

Re: on to letsencrypt

On Tue, Apr 20, 2021 at 4:16 PM Ed Greshko wrote: > On 21/04/2021 03:36, Jack Craig wrote: > > netstat -nap | grep named > > > > tcp0 0 127.0.0.1:53 > 0.0.0.0:* LISTEN 1090819/named > > tcp0 0 127.0.0.1:953 > 0

Re: ncat and resolved

On 21/04/2021 09:25, Todd Zullinger wrote: Do you have a 192.168.122.26 interface on the host? That's the error I see if I try to use an IP which is not assigned to any interface. Sure.  But it didn't help that I forgot I had created a process a few weeks ago that happened to grab that port o

Re: ncat and resolved

Ed Greshko wrote: > On 21/04/2021 08:29, Todd Zullinger wrote: >> Hi Ed, >> >> Ed Greshko wrote: >>> Does anyone know of a way to get ncat to listen on port 53 when using >>> systemd-resolved? >>> >>> [root@meimei ~]# ncat -l -4 -p 53 >>> Ncat: bind to 0.0.0.0:53: Address already in use. QUITTIN

Re: ncat and resolved

On 21/04/2021 08:29, Todd Zullinger wrote: Hi Ed, Ed Greshko wrote: Does anyone know of a way to get ncat to listen on port 53 when using systemd-resolved? [root@meimei ~]# ncat -l -4 -p 53 Ncat: bind to 0.0.0.0:53: Address already in use. QUITTING. You can't bind to the port if it's already

Re: ncat and resolved

Hi Ed, Ed Greshko wrote: > Does anyone know of a way to get ncat to listen on port 53 when using > systemd-resolved? > > [root@meimei ~]# ncat -l -4 -p 53 > Ncat: bind to 0.0.0.0:53: Address already in use. QUITTING. You can't bind to the port if it's already in use. But if you're okay with us

ncat and resolved

Does anyone know of a way to get ncat to listen on port 53 when using systemd-resolved? [root@meimei ~]# ncat -l -4 -p 53 Ncat: bind to 0.0.0.0:53: Address already in use. QUITTING. (no rants, please) -- Remind me to ignore comments which aren't germane to the thread. _

Re: on to letsencrypt

On 21/04/2021 03:36, Jack Craig wrote: netstat -nap | grep named tcp        0      0 127.0.0.1:53            0.0.0.0:*           LISTEN      1090819/named tcp        0      0 127.0.0.1:953           0.0.0.0:*           LISTEN      1090819/named udp

Re: suspend doesn't lock

On Tue, 20 Apr 2021 23:55:35 +0800 Qiyu Yan wrote: > 在 2021-04-20星期二的 10:32 +0200，Frank Elsner via users写道： > > Hi, > > > > running an full updated Fedora 33 I have the following problem: > > > > For a few days I have been observing that the screen isn't locked > > when the system comes up after

Re: on to letsencrypt

On Tue, Apr 20, 2021 at 5:47 AM Tim via users wrote: > On Tue, 2021-04-20 at 03:09 -0700, Jack Craig wrote: > > attached named.conf > > It has the following lines in it: > > listen-on port 53 { 127.0.0.1; 10.0.0.1; 108.220.213.121; }; > allow-query { localhost; 10.0.0.1; 108.220.213.1

Re: on to letsencrypt

On Tue, Apr 20, 2021 at 6:24 AM Ed Greshko wrote: > On 20/04/2021 20:47, Tim via users wrote: > > I can see reasons to be your own webserver (e.g. not having to pay more > > for someone else to do it, you can configure your server any that way > > you like, etc). But when you register a domain n

Re: on to letsencrypt

On Tue, Apr 20, 2021 at 4:30 AM Ed Greshko wrote: > On 20/04/2021 18:09, Jack Craig wrote: > > attached named.conf > > Well a quick look and it doesn't seem too bad. First a couple of > questions. > > 1. Why did you use "acl" statements and then not refer to them? > This file has been the side

Re: puzzling SELinux alert.

This morning, I was able to get SELinux alerts when running totem-video-thumbnailer. I submitted a bug. Here's the link: "https://bugzilla.redhat.com/show_bug.cgi?id=1951668";. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe sen

Re: suspend doesn't lock

在 2021-04-20星期二的 10:32 +0200，Frank Elsner via users写道： > Hi, > > running an full updated Fedora 33 I have the following problem: > > For a few days I have been observing that the screen isn't locked > when the system comes up after suspend. What could I have changed > unintentionally or is a gene

Re: suspend doesn't lock

On Tue, 20 Apr 2021 01:56:29 -0700 Samuel Sieb wrote: > On 4/20/21 1:32 AM, Frank Elsner via users wrote: > > running an full updated Fedora 33 I have the following problem: > > > > For a few days I have been observing that the screen isn't locked > > when the system comes up after suspend. What c

Re: on to letsencrypt

On 20/04/2021 20:47, Tim via users wrote: I can see reasons to be your own webserver (e.g. not having to pay more for someone else to do it, you can configure your server any that way you like, etc). But when you register a domain name, you're already paying for someone to host your DNS records,

Re: on to letsencrypt

On 20/04/2021 20:47, Tim via users wrote: I can see reasons to be your own webserver (e.g. not having to pay more for someone else to do it, you can configure your server any that way you like, etc). But when you register a domain name, you're already paying for someone to host your DNS records,

Re: on to letsencrypt

On Tue, 2021-04-20 at 03:09 -0700, Jack Craig wrote: > attached named.conf It has the following lines in it: listen-on port 53 { 127.0.0.1; 10.0.0.1; 108.220.213.121; }; allow-query { localhost; 10.0.0.1; 108.220.213.121; }; Does your computer actually recognise one of its WAN ports

Re: on to letsencrypt

On 20/04/2021 18:09, Jack Craig wrote: attached named.conf Well a quick look and it doesn't seem too bad.  First a couple of questions. 1.  Why did you use "acl" statements and then not refer to them? 2.  Did you mean this?     /* allow-recursion { 10.0.0.0/24; };     allow-recursio

Re: on to letsencrypt

attached named.conf registrar = network solutions where they reference => ns3.attdns.com & ws.llinuxlighthouse.com On Tue, Apr 20, 2021 at 12:02 AM Ed Greshko wrote: > On 20/04/2021 13:32, Jack Craig wrote: > > > > the second problem is the secondary IP as identified by AT&T to be my > sec

Re: suspend doesn't lock

On 4/20/21 1:32 AM, Frank Elsner via users wrote: running an full updated Fedora 33 I have the following problem: For a few days I have been observing that the screen isn't locked when the system comes up after suspend. What could I have changed unintentionally or is a general problem? Have yo

suspend doesn't lock

Hi, running an full updated Fedora 33 I have the following problem: For a few days I have been observing that the screen isn't locked when the system comes up after suspend. What could I have changed unintentionally or is a general problem? Regards, Frank ___

Re: on to letsencrypt

On 20/04/2021 13:32, Jack Craig wrote: the second problem is the secondary IP as identified by AT&T  to be my secondary refusing to reply  is refusing to provide answers BTW, this may have been answered but I can't find it in the 2 threads. Who is your registrar? -- Remind me to ignore comm