On Wed, Feb 21, 2024 at 10:01:30PM +0100, e9hack wrote:
> Am 21.02.2024 um 01:21 schrieb Daniel Golle:
> >
> > Yep, I didn't think about empty variables when I built this...
> >
> > Can you test this please:
> > https://github.com/openwrt/procd/pull/3
> >
>
> This does fix the issue.
>
> If I
Am 21.02.2024 um 01:21 schrieb Daniel Golle:
Yep, I didn't think about empty variables when I built this...
Can you test this please:
https://github.com/openwrt/procd/pull/3
This does fix the issue.
If I test a modified executable, I replaced it by a link to a link on a
automatically
On Tue, Feb 20, 2024 at 11:47:49PM +0100, e9hack wrote:
> Am 20.02.2024 um 14:14 schrieb Paul D:
> >
> > Could you show an example of this?
> >
>
> I modified /usr/lib/dnsmasq/dhcp-script.sh to see additional variables in the
> syslog:
>
> --- dhcp-script.sh.orig 2024-02-14 16:22:53.0
Am 20.02.2024 um 14:14 schrieb Paul D:
Could you show an example of this?
I modified /usr/lib/dnsmasq/dhcp-script.sh to see additional variables in the
syslog:
--- dhcp-script.sh.orig 2024-02-14 16:22:53.0 +0100
+++ dhcp-script.sh 2024-02-20 22:55:33.0 +0100
@@ -50,4
On 2024-02-17 22:55, e9hack wrote:
Hi,
I face a problem with hotplug calls. To execute hotplug calls, procd
checks given environment variables. If a variable is empty, it is
simply not set by procd. If such a variable is already set by the
shell, the called hotplug script gets a wrong value.
