On 16/08/21 7:46 pm, Michael Biebl wrote:
How exactly do you rename your interfaces? Do you use a udev rule? Can
you post those scripts/rules?
I had already posted this in PS of my first email. It is two step process.
Here it is again:
Little about tmpeth* naming.
Some old scripts that we
On Tue, 17 Aug 2021, Dave Close wrote:
> I'm trying to run "systemctl show" in a cron script. It works but I get
> a huge number of extra lines in my log for each run. Why? Can this be
> suppressed. I don't want to overfill the log.
>
> There is nothing in the man page (that I noticed) indicating
I'm trying to run "systemctl show" in a cron script. It works but I get
a huge number of extra lines in my log for each run. Why? Can this be
suppressed. I don't want to overfill the log.
There is nothing in the man page (that I noticed) indicating that "show"
causes anything to be logged. But her
On 16.08.2021 18:20, Gildas Bayard wrote:
> Hello,
>
> I've first posted on stackoverflow but couldn't get any usefull answer
> (gomenasai 😅)
>
> I'm trying to start a task when bluetooth is ready on a raspi (running
> raspbian 10 - buster) with systemd. I've added the file
> /etc/systemd/system/
How exactly do you rename your interfaces? Do you use a udev rule? Can
you post those scripts/rules?
On 16/08/21 5:09 pm, Ulrich Windl wrote:
Hi!
Actually I wonder (even before the upgrade) what that nonsense is about:
eth1: Interface name change detected, eth1 has been renamed to eth0.
No. If you see two journal logs that I posted. This message was not
coming before upgrade. Issue seems t
On 16/08/21 5:39 pm, Lennart Poettering wrote:
On Mo, 16.08.21 17:31, Amish (anon.am...@gmail.com) wrote:
On 16/08/21 5:25 pm, Lennart Poettering wrote:
On Mo, 16.08.21 16:09, Amish (anon.am...@gmail.com) wrote:
Some old scripts that we have expect interface names starting with eth. But
tho
On Mo, 16.08.21 17:31, Amish (anon.am...@gmail.com) wrote:
>
> On 16/08/21 5:25 pm, Lennart Poettering wrote:
> > On Mo, 16.08.21 16:09, Amish (anon.am...@gmail.com) wrote:
> >
> > > Some old scripts that we have expect interface names starting with eth.
> > > But
> > > those names are not predic
On 16/08/21 5:25 pm, Lennart Poettering wrote:
On Mo, 16.08.21 16:09, Amish (anon.am...@gmail.com) wrote:
Some old scripts that we have expect interface names starting with eth. But
those names are not predictable.
So to get predictable names starting with eth*, first I temporarily rename
al
On Mo, 16.08.21 16:09, Amish (anon.am...@gmail.com) wrote:
> Some old scripts that we have expect interface names starting with eth. But
> those names are not predictable.
>
> So to get predictable names starting with eth*, first I temporarily rename
> all interface with tmpeth*. This is done via
Hi!
Actually I wonder (even before the upgrade) what that nonsense is about:
eth1: Interface name change detected, eth1 has been renamed to eth0.
Regards,
Ulrich
>>> Amish schrieb am 16.08.2021 um 12:39 in Nachricht
<83597df0-fef1-049e-3707-2aa2a3819...@gmail.com>:
> Hello everyone,
>
> So I h
Hello everyone,
So I have around seven Arch Linux based systems.
All systems have 2 or 3 network cards.
eth0 is LAN side (192.168.x.x/24 range). eth1 and eth2 has WAN (public
internet) connectivity.
Today I upgraded all systems to systemd 249.3 and Linux kernel
5.13.10.arch1-1.
Everything
12 matches
Mail list logo
