Two separate problems there:
bigapple:~ root# port contents unbound|head
Port unbound contains:
  /Library/LaunchDaemons/org.macports.unbound.plist
  /opt/local/etc/LaunchDaemons/org.macports.unbound/org.macports.unbound.plist
  /opt/local/etc/LaunchDaemons/org.macports.unbound/unbound.wrapper
...

(Often, MacPorts startups operate via a wrapper that tries to reconcile the 
different behavior of daemons written for other Unix/Linux flavors with the 
expectation of launchd that programs must not background themselves, close and 
reopen stdin, stdout, and stderr, etc; so don't be surprised if that's a bit 
hard to follow.  I haven't always found the wrapper to be the best solution, 
but it usually works.)

As for the permissions, I didn't have that problem:

bigapple:~ root# find /opt/local \( -user unbound -o -group unbound \) -ls
180058793        0 drwxrwxr-x    4 root             unbound               128 
Aug 10 10:20 /opt/local/etc/unbound
180058801        8 -rw-r--r--    1 unbound          unbound               758 
Aug 10 10:20 /opt/local/etc/unbound/root.key
180058794        0 drwxr-xr-x    3 unbound          unbound                96 
Aug 10 10:20 /opt/local/var/run/unbound
180058765        0 -rw-r--r--    1 unbound          unbound                 0 
Jun 17 09:38 /opt/local/var/run/unbound/unbound.pid

but I have sometimes seen MacPorts set some of the groups on some of its files 
oddly (but using a group-id it created for one port or another).  I haven't 
seen that recently, and don't remember the port or the details, so I can't say 
what the cause is or how to get it fixed.  I don't recall it messing those up 
for files outside /opt/local, so I wouldn't worry _too_ much, although IMO it's 
not right.

If you're curious about users or groups created, you can list them with

dscl . -list /Users
or
dscl . -list /Groups

and get specifics with
dscl . -read /Users/unbound
or
dscl . -read /Groups/unbound

etc.  Or use the GUI: System Preferences -> Users&Groups; unlock, click Login 
Options, click Join, click Open Directory Utility..., click Directory Editor.  
Select Users or Groups, find the one you're interested in on the list, click on 
it, etc.  Just be careful and don't change anything by accident.  If it shows a 
lock symbol and "Not Authenticated", it probably won't let you anyway until you 
do that.

> On Aug 10, 2019, at 10:12, Gerben Wierda <[email protected]> wrote:
> 
> I am building a new Mac Mii Server, replacement for one running High Sierra 
> with Server.app that still includes Mail & Web. I want the new server still 
> to run Server.app for DNS, device management, profile management, Open 
> Directory (required for some other stuff) so I will be adding MacPorts mail & 
> web (could be difficult as there already is an Apache server for profile 
> manager and device manager) to a macOS Mojave Server.
> 
> A stretch objective is to connect postfix and dovecot to OpenDirectory for 
> authentication.
> 
> At this point the system is almost pristine (clean OS install, Xcode install, 
> Server.app install and basic config) and MacPorts has been installed and the 
> first port has been installed.
> 
> Anyway, I am documenting everything I have to do and I have run into a 
> situation where I am now stumped and the documentation for searching on the 
> system in /opt does help me out.
> 
> Here is my log snippet:
> Installed unbound using MacPorts
> 
> sudo port install unbound
> 
> which ends with:
> 
>   unbound has the following notes:
>     An example configuration is provided at 
> /opt/local/etc/unbound/unbound.conf-dist.
> 
>     A startup item has been generated that will aid in starting unbound with 
> launchd. It is disabled by default. Execute the following command to start
>     it, and to cause it to launch at startup:
>     
>         sudo port load unbound
> 
> Had some trouble locating unbound documentation to see how I can setup my 
> local zone. Is part of the main configuration. Stumped! Where is the start-up 
> item for unbound so I can check before installing it via port load unbound? 
> Question: Why is so much owned in /opt owned by group unbound?
> 
> ./sources/rsync.macports.org/macports/release/tarballs: 
> <http://rsync.macports.org/macports/release/tarballs:>
> total 327312
> -rw-r--r--   1 root  wheel    12680818 Aug 10 07:36 PortIndex
> -rw-r--r--   1 root  wheel         512 Aug 10 07:48 PortIndex.rmd160
> drwxr-xr-x  29 root  unbound       928 Oct  3  2018 base
> -rw-r--r--   1 root  wheel    85608960 Oct  3  2018 base.tar
> -rw-r--r--   1 root  wheel         512 Oct  3  2018 base.tar.rmd160
> drwxr-xr-x  62 root  unbound      1984 Aug 10 11:20 ports
> -rw-r--r--   1 root  wheel    69277184 Aug 10 07:48 ports.tar
> -rw-r--r--   1 root  wheel         512 Aug 10 07:48 ports.tar.rmd160
> 
> ./sources/rsync.macports.org/macports/release/tarballs/base: 
> <http://rsync.macports.org/macports/release/tarballs/base:>
> total 1352
> -rw-r--r--    1 root  unbound  111011 Oct  3  2018 ChangeLog
> -rw-r--r--    1 root  unbound   99338 Aug 22  2017 Doxyfile.in
> -rw-r--r--    1 root  unbound    3281 May  6  2018 HACKING
> -rw-r--r--    1 root  unbound    1556 May  6  2018 LICENSE
> -rw-r--r--    1 root  unbound    7079 May 28  2018 Makefile.in
> drwxr-xr-x    5 root  unbound     160 Jul  5  2018 Mk
> -rw-r--r--    1 root  unbound   36452 Jul  5  2018 aclocal.m4
> -rwxr-xr-x    1 root  unbound      44 May 28  2018 autogen.sh
> drwxr-xr-x    7 root  unbound     224 Oct  3  2018 config
> 
> I’m stumped and I don’t understand that group ownership. Can anybody explain?
> 
> Gerben Wierda
> Chess and the Art of Enterprise Architecture <http://enterprisechess.com/>
> Mastering ArchiMate <http://masteringarchimate.com/>
> Architecture for Real Enterprises 
> <https://www.infoworld.com/blog/architecture-for-real-enterprises/> at 
> InfoWorld
> On Slippery Ice <https://eapj.org/on-slippery-ice/> at EAPJ
> 

Reply via email to