unbound want start / change from root to

[macuserguru]

after installing I use

sudo port load unbound

but unbound want seen as daemon - only daemondo

What could I do to change from running under root user to the running under the unbound user? And using chroot too?

How could I use my own unbound.conf - must I insert the path in the default installed org.macports.unbound.plist?

Dec 12 16:41:50 mymbp sudo[64406]: admin : TTY=ttys000 ; PWD=/Users/xxxx ; USER=root ; COMMAND=/opt/local/bin/port load unbound
Dec 12 16:41:51 mymbp com.apple.xpc.launchd[1] (org.macports.unbound): The Debug key is no longer respected. Please remove it.
Dec 12 16:41:51 mymbp com.apple.xpc.launchd[1] (org.macports.unbound): This service is defined to be constantly running and is inherently inefficient.
Dec 12 16:41:52 mymbp mdworker[64261]: iWork MDI raised an exception: Could not find the end of central directory record
Dec 12 16:42:55 mymbp sudo[64422]: admin : TTY=ttys000 ; PWD=/Users/xxxx ; USER=root ; COMMAND=/opt/local/bin/port unload unbound

[macuserguru]

Cc Me!

[danielluke (Daniel J. Luke)]

unbound works fine for me. Like most/all macports startup items, daemondo is used. Is daemondo not actually starting unbound (via the unbound.wrapper script) for you? You don't include any information indicating an issue.

As for configuration, you need to create an unbound.conf file (you can use the one installed as unbound.conf-dist as a reference). See port notes unbound

[macuserguru]

In the Activity Monitor I see only the daemondo daemon - is the unbound hidden behind?

Did read unbound the unbound.conf file per default?

man unbound
 -c cfgfile
              Set  the  config  file  with  settings  for  unbound  to  read  instead  of  reading  the  file  at  the  default  location,
              /opt/local/etc/unbound/unbound.conf.

What could I do to use the unbound user (instead of root) - and using chroot too? Are changing the owner of the unbound binaries a way? After installing I found a new unbound user and group.

I found in the org.macports.unbound.plist no path to the unbound.conf

<array>
	<string>/opt/local/bin/daemondo</string>
	<string>--label=unbound</string>
	<string>--start-cmd</string>
	<string>/opt/local/etc/LaunchDaemons/org.macports.unbound/unbound.wrapper</string>
	<string>start</string>
	<string>;</string>
	<string>--stop-cmd</string>
	<string>/opt/local/etc/LaunchDaemons/org.macports.unbound/unbound.wrapper</string>
	<string>stop</string>
	<string>;</string>
	<string>--restart-cmd</string>
	<string>/opt/local/etc/LaunchDaemons/org.macports.unbound/unbound.wrapper</string>
	<string>restart</string>
	<string>;</string>
	<string>--pid=none</string>
</array>

[ryandesign (Ryan Carsten Schmidt)]

Replying to fritzs@…:

In the Activity Monitor I see only the daemondo daemon - is the unbound hidden behind?

I am not aware of a way to hide a process.

Did read unbound the unbound.conf file per default?

man unbound
 -c cfgfile
              Set  the  config  file  with  settings  for  unbound  to  read  instead  of  reading  the  file  at  the  default  location,
              /opt/local/etc/unbound/unbound.conf.

unbound should read that config file by default, yes.

What could I do to use the unbound user (instead of root) - and using chroot too? Are changing the owner of the unbound binaries a way? After installing I found a new unbound user and group.

If unbound starts as root and not as the unbound user, that sounds like a bug in the portfile that its maintainer should fix.

I found in the org.macports.unbound.plist no path to the unbound.conf

There should be no need to specify the path to the unbound.conf, as long as you place it in its default location as shown above.

[macuserguru]

Replying to ryandesign@…:

This messages I seen in the console at each load of unbound:

 COMMAND=/opt/local/bin/port load unbound
Dec 12 17:55:42 mymac com.apple.xpc.launchd[1] (org.macports.unbound): The Debug key is no longer respected. Please remove it.
Dec 12 17:55:42 mymac com.apple.xpc.launchd[1] (org.macports.unbound): This service is defined to be constantly running and is inherently inefficient.
Dec 12 17:55:45 mymac mdworker[64899]: iWork MDI raised an exception: Could not find the end of central directory record

[danielluke (Daniel J. Luke)]

This looks like you just don't know how to / haven't configured unbound yet / need support (ie. it's not a bug). You'd be better served posting to the mailing list.

[macuserguru]

you could close this!