On Mon, Jul 18, 2022 at 10:50:03PM +0200, Peter Boy wrote:
Am 18.07.2022 um 22:18 schrieb Peter Boy :
I got it finally working.
After some tests: It isn’t.
The programs I have to start depend on the existence of some (virtual)
network interfaces. rc.local is ordered after network.target,
On 19/07/2022 07.42, Sam Varshavchik wrote:
Am I the only one lucky enough to have kernel-5.18.11-200.fc36.x86_64 crash
reliably, on particular hardware, after starting a VM in virt-manager?
At least I think it's a crash. One second after a VM start it's brick-city.
Display frozen, no
> Am 18.07.2022 um 23:17 schrieb Garry T. Williams :
>
> and then create a .service file to run whatever program you want to
> start at boot-time.
Yeah, that’s the correct way. But in my case I don’t need a permanent solution
(hopefully). I have to start some systemd containers, which of
sudo inxi with various parameters?
suomi
On 18/07/2022 22.56, Garry T. Williams wrote:
On Saturday, July 16, 2022 2:55:25 PM EDT Joe Zeff wrote:
Recently, my laptop died and I had to buy a new one. Now, I'd like
to take a look at what hardware is inside. I know that there used
to be a
Subject: Is it possible to protect OpenSSH Daemon logins with 2nd
factor authentication (2FA)?
Good day from Singapore,
Is it possible to protect OpenSSH Daemon logins with 2nd factor
authentication (2FA)?
If it is possible, could you give me the links to excellent and
well-written guides on
Just to close this out, and not be "that guy" (https://xkcd.com/979/), I ended
up just rolling the kernel back to the Fedora 35 kernel (5.14.10).
Without a good way to isolate where the problem is (between XFS & LVM), I
really didn't want to waste time tracking this down, and restoring my system
On Mon, 2022-07-18 at 17:42 -0400, Sam Varshavchik wrote:
> But, these days, no more RS-232 ports.
If it's not a laptop, there may still be one. But just on a header
that needs a flylead to an external connector.
--
uname -rsvp
Linux 3.10.0-1160.71.1.el7.x86_64 #1 SMP Tue Jun 28 15:37:28
On Mon, 2022-07-18 at 22:18 +0200, Peter Boy wrote:
> The documentation is inconsistent. Some say /etc/rc.local, some
> /etc/rc.d/rc.local. The latter is correct.
On my other OS, /etc/rc.local is a symlink to the other one, which must
be chmod +x (it starts off without it).
I dare say the
Am 18.07.2022 um 22:18 schrieb Peter Boy: wrote
I got it finally working.
After some tests: It isn’t.
The programs I have to start depend on the existence of some (virtual) network
interfaces. rc.local is ordered after network.target, which doesn’t mean, the
network is functional then.
On 7/18/22 14:44, c. marlow wrote:
I just got a Lenovo ThinkPad 3rd gen
I installed Fedora 36 KDE on it
And I cannot get it to connect to the 2G connection. It only will allow me to
connect to the 5g connection.
From the subject and even that description, I thought you were talking
about a
On 18Jul2022 12:05, lejeczek wrote:
>Won't do for me - fails with any bit more "complex" case when multiple
>nodes are involved and user landing on each such node would have
>unique/different '.local' dir, having whole home dir net mounted.
If the whole homedir is net mountd (shared from a
Hi Ya'll,
I just got a Lenovo ThinkPad 3rd gen
I installed Fedora 36 KDE on it
And I cannot get it to connect to the 2G connection. It only will allow me to
connect to the 5g connection.
I have changed the name of the access point, changed the password several
times
only letters and
Am I the only one lucky enough to have kernel-5.18.11-200.fc36.x86_64 crash
reliably, on particular hardware, after starting a VM in virt-manager?
At least I think it's a crash. One second after a VM start it's brick-city.
Display frozen, no response from the network. I've got nothing: after
On Mon, 18 Jul 2022 22:50:03 +0200
Peter Boy wrote:
> The programs I have to start depend on the existence of some (virtual)
> network interfaces.
Yea, when I was doing stuff with rc.local I had that problem as well.
What I wound up doing was using the "at" command to start the scripts
I really
On Monday, July 18, 2022 4:50:03 PM EDT Peter Boy wrote:
> > Am 18.07.2022 um 22:18 schrieb Peter Boy :
> >
> > I got it finally working.
>
> After some tests: It isn’t.
>
> The programs I have to start depend on the existence of some
> (virtual) network interfaces. rc.local is ordered after
>
On Saturday, July 16, 2022 2:55:25 PM EDT Joe Zeff wrote:
> Recently, my laptop died and I had to buy a new one. Now, I'd like
> to take a look at what hardware is inside. I know that there used
> to be a program to show you all of the hardware, but it's been so
> long since I needed it that I
> Am 18.07.2022 um 22:18 schrieb Peter Boy :
>
> I got it finally working.
After some tests: It isn’t.
The programs I have to start depend on the existence of some (virtual) network
interfaces. rc.local is ordered after network.target, which doesn’t mean, the
network is functional then.
I got it finally working.
> Am 18.07.2022 um 18:08 schrieb Tom Horsley :
>
> Is it really gone, or are they simply not creating the rc.local
> file any longer?
The file is really gone. You have to create it at the right location.
The documentation is inconsistent. Some say /etc/rc.local, some
On Mon, Jul 18, 2022 at 10:52:42AM -0700, Mike Wright wrote:
On 7/18/22 10:47, Tom Horsley wrote:
On Mon, 18 Jul 2022 10:38:03 -0700
Mike Wright wrote:
/etc/rc.local
I think it is some more obscure location like /etc/rc.d/rc.local.
[Unit]
Description=/etc/rc.local Compatibility
On 7/18/22 10:47, Tom Horsley wrote:
On Mon, 18 Jul 2022 10:38:03 -0700
Mike Wright wrote:
/etc/rc.local
I think it is some more obscure location like /etc/rc.d/rc.local.
[Unit]
Description=/etc/rc.local Compatibility
Documentation=man:systemd-rc-local-generator(8)
On Mon, 18 Jul 2022 10:38:03 -0700
Mike Wright wrote:
> /etc/rc.local
I think it is some more obscure location like /etc/rc.d/rc.local.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to
On 7/18/22 09:00, Peter Boy wrote:
I have to run some scripts at the end of the boot process to establish various
workarounds for bugs in systemd. In the days of System V, /etc/rc.d/rc.local
would be the right place for this.
My research revealed several solutions with conflicting
using the rc.local is going to be easier to support than creating your
own systemd service to do exactly the same thing.
I have been using the rc.local stuff for a while for anything that
does not have a native systemd unit file.
I think the comment of not using it is for other developers to not
On Mon, 18 Jul 2022 18:00:30 +0200
Peter Boy wrote:
> Any recommendations and/or experiences?
Is it really gone, or are they simply not creating the rc.local
file any longer? I'm pretty sure I remember it working the last
time I used it, just had to make the file myself and make it
executable.
You might include a full dmesg/messages. This is the sort of error
you get when there is an underlying read failure/breakage on the
device that the data is actually on.
You get scsi errors/block errors first and then that shows up as
filesystem errors similar to these. This sounds like the
I have to run some scripts at the end of the boot process to establish various
workarounds for bugs in systemd. In the days of System V, /etc/rc.d/rc.local
would be the right place for this.
My research revealed several solutions with conflicting recommendations:
(a)
There is - also in Fedora
On Mon, 18 Jul 2022 14:34:13 +0100
Patrick O'Callaghan wrote:
> I just created a new file in the system.conf.d directory. Didn't have
> to touch the SElinux context.
I guess that makes sense, since the file doesn't exist on the system, so
there isn't any selinux rule for it. I was just being
On Mon, 2022-07-18 at 06:08 -0700, stan via users wrote:
> On Sun, 17 Jul 2022 19:14:09 +0200
> francis.montag...@inria.fr wrote:
>
> > Did you specified the [Manager] tag in the drop-in file ?
> >
> > Example:
> >
> > ## Weird: systemd seems to uses internally a ...USec name for that
> >
On Sun, 17 Jul 2022 19:14:09 +0200
francis.montag...@inria.fr wrote:
> Did you specified the [Manager] tag in the drop-in file ?
>
> Example:
>
> ## Weird: systemd seems to uses internally a ...USec name for that
> systemctl show --property=DefaultTimeoutStopUSec
> DefaultTimeoutStopUSec=1min
On Mon, 2022-07-18 at 07:29 -0300, George N. White III wrote:
> Cables and connectors should also be considered. Try swapping cables
> and connections. "Contact enhancer" sometimes solves connection
> problems (now that cars are full of computers, you can buy
> contact enhancer at auto supply
On 15/07/2022 23:25, Cameron Simpson wrote:
On 15Jul2022 16:12, lejeczek wrote:
would anybody know if user's '.local' folder, its path & name are
configurable in some way?
Perhaps by a var or/and os-wide configs?
Maybe not, but nothing stops you making it, or particular things inside
it,
On Mon, Jul 18, 2022 at 12:10 AM Patrick Hemmer
wrote:
> Ever since upgrading to Fedora 36, my root filesystem is getting corrupted
> every few hours. I maintain block level backups, and I have to restore
> every time this happens. xfs_repair can fix the filesystem, but the system
> is typically
32 matches
Mail list logo
