Thank you
Amish.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
op nscd process actually
> 2.execute: /usr/bin/nscd
> start nscd by shell command
Why dont you (or your script) start it with:
systemctl start nscd
Then status and stop will also work as expected.
Amish.
___
systemd-devel maili
Resending my previous email as I would really want this feature.
I asked for help on IRC channel too but it hardly appears active.
Amish.
On Friday 16 June 2017 01:06 PM, Lennart Poettering wrote:
On Thu, 15.06.17 18:22, Amish (anon.am...@gmail.com) wrote:
Hmm, that wasn't the actual
On Thursday 15 June 2017 03:07 PM, Mantas Mikulėnas wrote:
On Thu, Jun 15, 2017 at 11:21 AM, Lennart Poettering
<lenn...@poettering.net <mailto:lenn...@poettering.net>> wrote:
On Tue, 13.06.17 21:44, Amish (anon.am...@gmail.com
<mailto:anon.am...@gmail.com>) w
On Friday 16 June 2017 01:06 PM, Lennart Poettering wrote:
On Thu, 15.06.17 18:22, Amish (anon.am...@gmail.com) wrote:
Hmm, that wasn't the actual question though, was it? The point was just
to make networkd ignore carrier status (i.e. often there's no need to
remove addresses just because
ut none worked.
Any idea / suggestions? Something similar to - CriticalConnection for DHCP?
Or may be we can have Persistent=true in "[Network]" OR "[Address]" section?
Thanks in advance,
Regards
Amish.
___
systemd-devel mailing
On Friday 06 October 2017 07:36 PM, Susant Sahani wrote:
On Fri, Oct 6, 2017 at 3:03 PM, Amish <anon.am...@gmail.com
<mailto:anon.am...@gmail.com>> wrote:
Hello,
Thank you. I am curious to know if this new setting:
ConfigureWithoutCarrier=1 would resolve my quer
t (eg. cable removed / network issues) then
link_update() function would go ahead and call link_carrier_lost()
and unconfigure the device.
i.e. it will not obey ConfigureWithoutCarrier=1 which I believe it should.
Thanks and regards,
Amish.
On Friday 06 October 2017 01:54 PM, Lennart Poettering wrote
On Friday 16 June 2017 01:06 PM, Lennart Poettering wrote:
On Thu, 15.06.17 18:22, Amish (anon.am...@gmail.com) wrote:
Hmm, that wasn't the actual question though, was it? The point was just
to make networkd ignore carrier status (i.e. often there's no need to
remove addresses just because
[Network]
DHCP=yes
This is how Android and iOS work i.e. they allow to set IP address per
AP. I think Windows allows it too. (not sure though)
Thanks and regards,
PS: Hope I have not overlooked any existing setting or an easier way to
do it.
Amish
ootCommand=/usr/bin/systemctl reboot
So I believe something is not right or I am doing something wrong in an
unexpected way.
Case 2) may be KDE related issue but case 1) should atleast have worked
as expected.
Can anyone else test?
Thank you,
Amish.
___
sy
applicable
only for /tmp or /var/{cache,run,tmp} only?
I could not locate anything on man page.
Thanks in advance,
Amish
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
On 16/10/18 7:03 PM, Lennart Poettering wrote:
On Di, 16.10.18 18:14, Amish (anon.am...@gmail.com) wrote:
Does systemd have a way of specifying that R and D should be applicable only
for /tmp or /var/{cache,run,tmp} only?
When you invoke the systemd-tmpfiles binary you could specify
--prefix
ail id can be created on Github.
And that user activates "Watch" feature with "Releases only" mode set.
So Github will automatically send email to mailing list. (needs some
testing by mailing list administrator)
Regards,
Amish.
___
syst
On 18/01/19 2:29 am, Lennart Poettering wrote:
On Do, 17.01.19 07:05, Amish (anon.am...@gmail.com) wrote:
On 16/01/19 11:52 pm, Lennart Poettering wrote:
On Mi, 16.01.19 09:46, Colin Guthrie (gm...@colin.guthr.ie) wrote:
Jérémy ROSEN wrote on 16/01/2019 08:24:
yes... adding
) supports:
IgnoreCarrierLoss=true.
This way routes should not vanish when cable is unplugged.
Regards,
Amish
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Started Download files.
Nov 26 13:50:37 foo systemd[1]: dnld.service: Succeeded.
So how do I allow systemd-inhibit call when a script is called via
systemd instead of directly?
Is this systemd bug or am I missing something in dnld.service file?
Amish
__
ucceeded.
So how do I allow systemd-inhibit call when a script is called via
systemd instead of directly?
Is this systemd bug or am I missing something in dnld.service file?
Amish.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
On 13/01/20 3:03 pm, Lennart Poettering wrote:
On Di, 26.11.19 13:55, Amish (anon.am...@gmail.com) wrote:
If I change code to not call systemd-inhibit:
$ cat /home/foo/downloads/dnld.sh
#!/bin/bash
/home/foo/downloads/dnld.pl
Then service file runs fine.
# systemctl start dnld.service
er and systemd-devel mailing list, as they
are fully public.
(There should be no hyperlink to issue tracker or systemd-devel mailing
list to discourage accidental clicking)
Amish
___
systemd-devel mailing list
systemd-devel@lists.f
On 13/07/20 2:07 am, Uoti Urpala wrote:
On Sun, 2020-07-12 at 17:13 +0300, Andrei Borzenkov wrote:
12.07.2020 16:21, Amish пишет:
I have a timer file like this:
[Unit]
Description=Foo
After=multi-user.target
[Timer]
OnCalendar=*:0/5
Persistent=false
[Install]
WantedBy=timers.target
timers.target runs before multi-user.target. But here
something inside timers.target waits for multi-user.target.
So how does systemd resolve this loop?
Thanks in advance
Amish
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https
On 11/03/21 7:39 pm, Alvin Šipraga wrote:
Hi,
On 3/11/21 11:01 AM, Reindl Harald wrote:
Am 11.03.21 um 06:36 schrieb Amish:
Hello
So I have a wireguard setup which I use to connect to my server.
But I do not connect to it daily, just once a in a while.
I have setup wg0.netdev file and wg0
On 11/03/21 7:39 pm, Alvin Šipraga wrote:
Hi,
On 3/11/21 11:01 AM, Reindl Harald wrote:
Am 11.03.21 um 06:36 schrieb Amish:
Hello
So I have a wireguard setup which I use to connect to my server.
But I do not connect to it daily, just once a in a while.
I have setup wg0.netdev file and wg0
. And then when I want it up. I rename it to .netdev and do:
#networkctl reload.
But thats an inefficient workaround.
I would like a solution where I can bring it up or down on demand with
single command:
#networkctl up wg0
#networkctl down wg0
Thank you
Amish
pe l
-printf "%f\n" | while read tmpiface; do /usr/bin/ip link set dev
"$tmpiface" name "$(echo $tmpiface | sed s/tmpeth/eth/)"; done
This ensures that I have predictable names starting with eth*. And it is
working fine from 2-3 years. Even with current issue, name assignment is
working fine.
Amish.
h2: Gained carrier
All interfaces are now up and running as expected.
Please check as I do not believe that this issue is causing any race but
to me it looks like some logical change in systemd-networkd which is
causing the issue.
Thank you and regards,
Amish
On 17/08/21 3:18 pm, Colin Guthrie wr
is breaking my system.
And if it does not exist that means, I can expect it to fix my issue.
Regards,
Amish.
On 18/08/21 11:42 am, Amish wrote:
Hello,
Thank you for your reply.
I can understand that there can be race.
*But when I check logs, there is no race happening*.
*Let us see
On 18/08/21 12:24 pm, Amish wrote:
Hello
Further to my previous email:
I see that there is already an *extremely similar issue* reported on
July 12, 2021 and it has been fixed.
https://github.com/systemd/systemd/issues/20203
But I do not know if this fix exists in systemd v249.3 (Arch
to be related to this message.
Regards,
Amish.
Amish schrieb am 16.08.2021 um 12:39 in Nachricht
<83597df0-fef1-049e-3707-2aa2a3819...@gmail.com>:
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
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
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
to eth0 at system startup?
All systems are production systems and after today's long downtime, I
can not downgrade any system to check what is wrong as management would
be on fire if there is another downtime.
Thank you in advance,
Amish
PS:
Little about tmpeth* naming.
Some old scripts
then is there any configuration which I can tweak to
allow foo.service.d as symlinks?
Otherwise I will have to replan whole structure and create symlinks for
each 10-custom1.conf, 20-custom2.conf, so on.
I use Arch Linux.
Regards,
Amish.
Just an update, this bug was reported on github (by someone else)
https://github.com/systemd/systemd/issues/21920
And related PR for the fix is at:
https://github.com/systemd/systemd/pull/21925
Amish
On 28/12/21 09:32, Amish wrote:
Hello
Something changed in systemd v250 with respect
35 matches
Mail list logo
