Re: puzzling SELinux alert.

2021-04-13 Thread home user
On 4/13/21 5:20 PM, Ed Greshko wrote: Long zoom meeting done; now I'm back to this. memfd refers to "Memory File Descriptor".  The file in question exists only in RAM and is a temporary file at that. Command such as "restorecon" are useless for this. ok. I'm guessing it may be caused not by

Re: puzzling SELinux alert.

2021-04-13 Thread home user
On 4/13/21 5:06 PM, Roger Heflin wrote: sestatus will show the current status. if enforcing then something may not be functioning as designed. if permissive then it will report it is blocking when it is not, and if you set it enforcing then something would probably break. if you set it permiss

Re: puzzling SELinux alert.

2021-04-13 Thread Ed Greshko
On 14/04/2021 01:40, home user wrote: At least 3 times in the past few days I've seen the same SELinux alert.  I put the text of the details in the attached file "alerts.txt".  All 3 occurrences were while using caja to rename or delete a file, though it does not happen every time I rename or d

Re: puzzling SELinux alert.

2021-04-13 Thread Roger Heflin
sestatus will show the current status. if enforcing then something may not be functioning as designed. if permissive then it will report it is blocking when it is not, and if you set it enforcing then something would probably break. if you set it permissive at one time then it will stay set perm

Re: puzzling SELinux alert.

2021-04-13 Thread home user
On 4/13/21 2:24 PM, Roger Heflin wrote: Are you running permissive or enforcing? > if permissive then it does not block anything, but says it is blocking if enforcing it is blocking something, though it may be a pointless/useless interface feature of some sort that does not matter, and does not

Re: puzzling SELinux alert.

2021-04-13 Thread Roger Heflin
Are you running permissive or enforcing? if permissive then it does not block anything, but says it is blocking if enforcing it is blocking something, though it may be a pointless/useless interface feature of some sort that does not matter, and does not really affect functionality. And it might

Re: puzzling SELinux alert.

2021-04-13 Thread home user
On 4/13/21 12:48 PM, Roger Heflin wrote: I see a lot of /memfd: in lsof it appears to be anonymous files (ie temp files). I am going to guess memfd is memory file descriptor, ie a temp file created in memory. Usually they are going to not actually exist anywhere in a fs. And generally the app

Re: Announcements for manual configuration intervention?

2021-04-13 Thread Matti Pulkkinen
ti, 2021-04-13 kello 14:53 -0400, Matthew Miller kirjoitti: > You may consider enabling the "rpmconf" plugin for DNF. This will by > default > attempt to merge such files -- or you can set the `diff` config > option to > make it just show you the differences. > That's a very good call, thank you.

Re: Announcements for manual configuration intervention?

2021-04-13 Thread Matthew Miller
On Mon, Apr 12, 2021 at 09:59:34PM +0300, Matti Pulkkinen wrote: > configuration is broken, and it can't be fixed automatically. Is there > a list, or some other method, by which I could be notified of these > sorts of things? Not for specific packages necessarily, but just in > general, even if it

Re: systemd-resolved, split dns, & vpn setup

2021-04-13 Thread Ed Greshko
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

Re: puzzling SELinux alert.

2021-04-13 Thread Roger Heflin
I see a lot of /memfd: in lsof it appears to be anonymous files (ie temp files). I am going to guess memfd is memory file descriptor, ie a temp file created in memory. Usually they are going to not actually exist anywhere in a fs. And generally the app that opens/creates them is the app that is

Re: systemd-resolved, split dns, & vpn setup

2021-04-13 Thread Jack Craig
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:

Re: systemd-resolved, split dns, & vpn setup

2021-04-13 Thread Jack Craig
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-resolved, split dns, & vpn setup > > Oh so now I have le

Re: Announcements for manual configuration intervention?

2021-04-13 Thread Matti Pulkkinen
ti, 2021-04-13 kello 19:57 +0800, Qiyu Yan kirjoitti: > "defined in the installation": this means the list of servers is > specifyed by installer. As in Anaconda? > As you see, the difference is only in server/pool settings. Yes, but that's not unexpected because that's where the problem was. >

puzzling SELinux alert.

2021-04-13 Thread home user
At least 3 times in the past few days I've seen the same SELinux alert.  I put the text of the details in the attached file "alerts.txt".  All 3 occurrences were while using caja to rename or delete a file, though it does not happen every time I rename or delete a file in caja.  These alerts co

Re: invisible application after upgrade.

2021-04-13 Thread home user
On 4/13/21 5:02 AM, Tim via users wrote: On Mon, 2021-04-12 at 14:37 +0930, Tim via users wrote: What doesn't change, though, are user settings. Any program that stores its settings in your homespace is unaffected by RPM updates. Your configurations carry over. However, some applications chang

Re: dangling symlinks and upgrades (was "invisible application after upgrade").

2021-04-13 Thread home user
On 4/12/21 11:12 AM, home user wrote: (context) In the "invisible application after upgrade" thread, Ed did not know how I did my upgrade to f33.  I responded that I mostly followed the Fedora upgrade instructions from here: "https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/"

Re: dangling symlinks and upgrades (was "invisible application after upgrade").

2021-04-13 Thread home user
On 4/13/21 3:17 AM, Patrick O'Callaghan wrote: On Mon, 2021-04-12 at 11:12 -0600, home user wrote: Isn't a dangling symlink a file system parallel to a dangling pointer in a C/C++ program? A dangling pointer always points at something and is a clear and present danger if it's ever dereferenced

Re: dangling symlinks and upgrades (was "invisible application after upgrade").

2021-04-13 Thread home user
On 4/12/21 1:47 PM, Andras Simon wrote: 2021-04-12 19:12 UTC+02:00, home user : [... snip ...] What good, valid purpose is there for a package to have a dangling symlink? Or maybe "hunspell" needs a little clean-up? Probably no and yes. But it's not just hunspell. Far from it! I was assumin

Re: dangling symlinks and upgrades (was "invisible application after upgrade").

2021-04-13 Thread home user
On 4/12/21 1:15 PM, George N. White III wrote: On Mon, 12 Apr 2021 at 14:13, home user > wrote: [... snip ...] (question 2) In a later post, Andras provided and example of a dangling symlink (in the "hunspell" package) that should not be deleted. When I w

Re: dangling symlinks and upgrades (was "invisible application after upgrade").

2021-04-13 Thread Patrick O'Callaghan
On Tue, 2021-04-13 at 08:14 -0400, Jonathan Billings wrote: > On Tue, Apr 13, 2021 at 10:17:56AM +0100, Patrick O'Callaghan wrote: > > > What good, valid purpose is there for a > > > package to have a dangling symlink? > > > > I could imagine it being used as a kind of placeholder, but I > > woul

Re: dangling symlinks and upgrades (was "invisible application after upgrade").

2021-04-13 Thread Jonathan Billings
On Tue, Apr 13, 2021 at 10:17:56AM +0100, Patrick O'Callaghan wrote: > > What good, valid purpose is there for a > > package to have a dangling symlink? > > I could imagine it being used as a kind of placeholder, but I wouldn't > call it elegant. Firefox, for example, uses a dangling symlink to

Re: Announcements for manual configuration intervention?

2021-04-13 Thread Qiyu Yan
在 2021-04-13星期二的 11:18 +0300,Matti Pulkkinen写道: > ti, 2021-04-13 kello 11:39 +0800, Qiyu Yan kirjoitti: > > I think it's not due to a broken configuration, maybe a broken NTP > > server is specified? Can you diff those two configurations? > > Sure: > > 1,5d0 > < # These servers were defined in th

Re: systemd-resolved, split dns, & vpn setup

2021-04-13 Thread Ed Greshko
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

Re: invisible application after upgrade.

2021-04-13 Thread Tim via users
On Mon, 2021-04-12 at 14:37 +0930, Tim via users wrote: > What doesn't change, though, are user settings. Any program that > stores its settings in your homespace is unaffected by RPM updates. > Your configurations carry over. However, some applications change > their configuration format over t

Re: systemd-resolved, split dns, & vpn setup

2021-04-13 Thread Tim via users
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

Re: dangling symlinks and upgrades (was "invisible application after upgrade").

2021-04-13 Thread Patrick O'Callaghan
On Mon, 2021-04-12 at 11:12 -0600, home user wrote: > Isn't a dangling symlink a file system parallel to a dangling > pointer in a C/C++ program?  A dangling pointer always points at something and is a clear and present danger if it's ever dereferenced. A dangling symlink doesn't point at anythin

Re: Announcements for manual configuration intervention?

2021-04-13 Thread Matti Pulkkinen
ti, 2021-04-13 kello 11:39 +0800, Qiyu Yan kirjoitti: > I think it's not due to a broken configuration, maybe a broken NTP > server is specified? Can you diff those two configurations? Sure: 1,5d0 < # These servers were defined in the installation: < server 49.57.50.46 iburst < server 56.57.46.49