On 26/01/2022 00:35, Robert Nichols wrote:
In a Fedora 35 VM, all users and groups in an NFS mounted filesystem are mapped to
"nobody" even though the names and numeric IDs are the same on the server and
client. The messages logged are of the form:
"name '@local' does not map into dom
On Thu, Jan 27, 2022 at 4:04 PM Doug Herr wrote:
>
> > With XFCE, we can set a window to always be on top of all other
> > windows. However, I am looking for a variant of such a feature: Always
> > on top of the window I specify, say always on top of the Firefox
> > window.
> >
> > Is such a tool
On 1/26/22 11:32, Matthew Miller wrote:
On Tue, Jan 25, 2022 at 11:55:03AM -0600, Thomas Cameron wrote:
This may be the resolution, is to just disable systemd-resolved. I
hate to do it, though. I still don't understand why the hostname
isn't being set correctly.
Can you file a bug for this plea
On 1/26/22 11:32, Matthew Miller wrote:
On Tue, Jan 25, 2022 at 11:55:03AM -0600, Thomas Cameron wrote:
This may be the resolution, is to just disable systemd-resolved. I
hate to do it, though. I still don't understand why the hostname
isn't being set correctly.
Can you file a bug for this plea
On 1/27/22 01:21, Samuel Sieb wrote:
What are these plenty of things? This is the first that I know of.
And the question still remains. Is the OS looking up the hostname at
runtime or was it always the installer setting it at install time?
Historically it's looked up its hostname at boot t
On 1/26/22 16:48, Samuel Sieb wrote:
I think I figured out what he's doing and I'm kind of surprised that
it works at all. He's expecting the system to use its IP address to
lookup its hostname. That seems wrong. Maybe what is working is that
the installer does that lookup and sets the hostn
On 1/26/22 16:17, Peter Boy wrote:
Disabling systemd-resolved might not be the best idea. That makes you a good
candidate for surprise follow-up problems elsewhere.
I’m wondering, if something is wrong with your DHCP / DNS service.
I mean, I guess it could be, but I've used ISC dhcpd and name
On Thu, Jan 27, 2022, at 5:25 AM, Paul Smith wrote:
> Dear All,
>
> With XFCE, we can set a window to always be on top of all other
> windows. However, I am looking for a variant of such a feature: Always
> on top of the window I specify, say always on top of the Firefox
> window.
>
> Is such a too
Hi.
On Thu, 27 Jan 2022 08:10:53 -0600 Robert Nichols wrote:
> On 1/26/22 7:15 PM, Gordon Messmer wrote:
>> What does the entry for that filesystem in /proc/mounts look like? It
>> should have negotiated mount options that shed some light.
>> Maybe add the "sec=sys" mount option to the clien
On 1/26/22 7:15 PM, Gordon Messmer wrote:
On 1/25/22 08:35, Robert Nichols wrote:
In a Fedora 35 VM, all users and groups in an NFS mounted filesystem are mapped to
"nobody" even though the names and numeric IDs are the same on the server and
client. The messages logged are of the form:
https://koji.fedoraproject.org/koji/buildinfo?buildID=1909308
On Thu, Jan 27, 2022 at 2:16 PM Luna Jernberg wrote:
> jforbes is working on packing the 5.16.13 kernel that just dropped, will
> be out to test later today :)
>
> On Thu, Jan 27, 2022 at 1:16 PM Sumantro Mukherjee
> wrote:
>
>> Hey
Dear All,
With XFCE, we can set a window to always be on top of all other
windows. However, I am looking for a variant of such a feature: Always
on top of the window I specify, say always on top of the Firefox
window.
Is such a tool available on Fedora?
Thanks in advance,
Paul
_
jforbes is working on packing the 5.16.13 kernel that just dropped, will be
out to test later today :)
On Thu, Jan 27, 2022 at 1:16 PM Sumantro Mukherjee
wrote:
> Hey All,
>
> Kernel 5.16 Test week is happening from 2022-01-23 to 2022-01-29. It's
> fairly simple, head over to the wiki [0] and re
Hey All,
Kernel 5.16 Test week is happening from 2022-01-23 to 2022-01-29. It's
fairly simple, head over to the wiki [0] and read in detail about the
test week and simply run the test case mentioned in[1] and enter your
results. Justin Forbes, has added a new Kernel Image for testing.
For folks, u
New behavior,
fcontext -a -t condor_log_t '/etc/sysctl.d'
restorecon -v '/etc/sysctl.d'
ausearch -c 'linux_kernel_tu' --raw | audit2allow -M my-linuxkerneltu
semodule -i my-linuxkerneltu.pp
systemctl status condor.service
systemctl status condor.service
● condor.service - Condor Distributed High
> Am 27.01.2022 um 06:59 schrieb Tim via users :
>
> ….
>
> * DHCP can accept a hostname from a client, but it doesn't have to.
> * DHCP can give a hostname to a client, but it doesn't have to, and
> the client doesn't have to accept it.
> * A host can find out its hostname from its IP address
Complementary information
SELinux is preventing condor_master from getattr access on the filesystem
/sys/fs/cgroup.
* Plugin catchall (100. confidence) suggests **
If you believe that condor_master should be allowed getattr access on the
cgroup filesystem by def
On 1/26/22 23:45, Tim via users wrote:
Tim:
I don't see why that's wrong, there were plenty of things that
discover their hostname by doing a reverse look-up of their IP. And
he demonstrated several releases that worked exactly that way.
Samuel Sieb:
What are these plenty of things? This is
18 matches
Mail list logo
