Hello,
on 10.3.2, for all processes dhcpcd creates
i see in /proc/ that stdout/stderr are /dev/null:
ls -lah /proc/<pid>/fd
...
l-wx------ 1 root root 64 Aug 28 16:58 1 -> /dev/null
l-wx------ 1 root root 64 Aug 28 16:58 2 -> /dev/null
However with 10.5.2 i see
l-wx------ 1 root root 64 Aug 27 18:20 1 -> pipe:[54494]
l-wx------ 1 root root 64 Aug 27 18:20 2 -> pipe:[54495]
for the initial process (started via a script), or
lrwx------ 1 root root 64 Aug 27 18:52 1 -> /dev/ttymxc2
lrwx------ 1 root root 64 Aug 27 18:52 2 -> /dev/ttymxc2
when called more directly for testing purposes.
That has caused issues in our deployment due to some other process ending up in a blocking read on the pipe. Used to work fine up to 10.3.2 inclusively.
Now i tried to follow the code and i assume for some reason dhcpcd_daemonise hasn't been called.
Parameters for dhcpcd are -b -qq -f </path/to/the/config> <interface>.
Hello,
on 10.3.2, for all processes dhcpcd creates
i see in
/proc/that stdout/stderr are/dev/null:However with 10.5.2 i see
for the initial process (started via a script), or
when called more directly for testing purposes.
That has caused issues in our deployment due to some other process ending up in a blocking read on the pipe. Used to work fine up to 10.3.2 inclusively.
Now i tried to follow the code and i assume for some reason
dhcpcd_daemonisehasn't been called.Parameters for dhcpcd are
-b -qq -f </path/to/the/config> <interface>.