as it should only run as postfwd user / postfwd group
This is the point they want to convey: <Vierdo> so why is acct-group/postfwd / acct-user/postfwd in portage ? :( <Vierdo> openrc should not start it as root <Vierdo> postfwd should not be coded with need to start as root They want to run it non-root, and they say this is happening: Apr 18 00:38:37 tux postfwd3/master[4214]: postfwd3 2.03 starting [daemons: server] Apr 18 00:38:37 tux postfwd3/master[4214]: Started server at pid 4307 Apr 18 00:38:37 tux postfwd3/policy[4307]: 2022/04/18-00:38:37 postfwd3::server (type Net::Server::Multiplex) starting! pid(4307) Apr 18 00:38:37 tux postfwd3/policy[4307]: Binding to TCP port 10040 on host 127.0.0.1 with IPv4 Apr 18 00:38:37 tux postfwd3/policy[4307]: Setting gid to "65534 65534" Apr 18 00:38:37 tux postfwd3/policy[4307]: FATAL: Couldn't become gid "65534": Operation not permitted? Apr 18 00:38:37 tux postfwd3/policy[4307]: Couldn't become gid "65534": Operation not permitted Apr 18 00:38:37 tux postfwd3/policy[4307]: ready for input I cannot confirm or deny what is going wrong , but I am trying to bridge a language barrier from IRC to bugzilla to help understand this persons bug. GL
What is your problem? The ebuild defaults to let postfwd run as postfwd user. Ths only thing I can spot: The systemd service uses postfwd's "--user" and "--group" options on start the daemon whereas the OpenRC init script uses start-stop-daemons facility to change UID/GID and does not use postfwds options at all (so there is not need to change uid/gid).
