It seems that apt has some odd behaviours that I am not expecting in regards to handling process ownership, and it's not entirely clear how it handles DPkg [Pre|Post]-Invoke events.
Steps to reproduce:
Using the script '/usr/local/share/iptables/host-updates' by calling from
'/etc/apt/apt.conf.d/30firewall-host-updates' with the contents of
DPkg { Pre-Invoke { "/usr/local/share/iptables/host-updates --add" }; Post-Invoke { "/usr/local/share/iptables/host-updates --remove" }: };
And then issuing the command of 'sudo apt update' will shoot 'Ign' messages as the host names for each listed repository returns unresolved.
Questions:
- When does apt draw Pre-Invoke stanzas as configured by the powers that be, and what user/group is used to handle the identities of the [sub-]processes?
- If I have 'root', and '_apt' in the dialout group, why am I not getting DNS responses?
It seems that apt has some odd behaviours that I am not expecting in regards to handling process ownership, and it's not entirely clear how it handles DPkg [Pre|Post]-Invoke events.
Steps to reproduce:
Using the script '/usr/local/share/iptables/host-updates' by calling from
'/etc/apt/apt.conf.d/30firewall-host-updates' with the contents of
DPkg { Pre-Invoke { "/usr/local/share/iptables/host-updates --add" }; Post-Invoke { "/usr/local/share/iptables/host-updates --remove" }: };And then issuing the command of 'sudo apt update' will shoot 'Ign' messages as the host names for each listed repository returns unresolved.
Questions: