seatd support is enabled by default, but I have added it as a port OPTION (SEATD) and you can disable it during builds if you want to. So yes it will take in sysutils/seatd by default.
That doesn't match my experience. When launched via a login manager such as dtlogin it runs as user nobody while still trying to write its logs in /var/logs, failing miserably of course unless I change the permissions to 777.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.