dustin/metricspi/pipeline/head This commit looks goodDetails
By default, Buildroot creates `/etc/resolv.conf` as a symlink to
`/tmp/resolv.conf`. This allows it to be modified at runtime, even if
`/` is on a read-only filesystem (assuming `/tmp` is not).
Unfortunately, this causes problems for systemd units with
`PrivateTmp=yes`, because they are not able to read the `resolv.conf`
file.
A more appropriate location for the writable `resolv.conf` is `/run`.
This filesystem is not affected by the `PrivateTmp` setting, and is
always available to units.
dustin/metricspi/pipeline/head This commit looks goodDetails
When I originally added the *victoriametrics* user to the `users` file,
I did not realize that it was possible for a package to define a user.
It makes much more sense to define it there.
dustin/metricspi/pipeline/head This commit looks goodDetails
Now that *dhcpcd.service* and *dhcpcd-wait-online.service* correctly
activate *network.target* and *network-online.target*, respectively, the
hack to fix the *collectd* *wait_prometheus* plugin binding to the TCP
socket is no longer needed.
The *dhcpcd.service* systemd unit file that ships with Buildroot is
broken. It orders the unit after *network.target*, which makes no
sense. It also configures the process to fork, but incorrectly
configures the PID file. Finally, by relying on the fork to indicate
that the network is "online," it does not distinguish between "an
interface is up" and "the network is reachable." As most daemons only
need the former, they only rely on *network.target*, and thus can fail
to start correctly.
To correct this brokenness, we provide our own unit file for
*dhcpcd.service*, based on the one included in the Fedora *dhcpcd* RPM
package. For "online" signalling, we provide a pair of shell scripts:
one reads from a named pipe waiting for a message and the other sends a
message to the pipe when configuration is complete.
Ansible's `user` module *requires* that the `usermod` command be
present, even if it would not actually create or modify the specified
user. It does not actually execute it unless it needs to, so we can
stub it out. Making it a symlink to `false` ensures that it will never
do anything, and will fail if its actually run.
Dustin