On Sat, Jan 04, 2020 at 12:35:46PM -0600, Matthew Martin wrote:
> For what it's worth most daemons currently print "configuration OK":
> bgpd dvmrpd eigrpd httpd ifstated iked ldpd npppd ntpd ospf6d ospfd rad
> radiusd relayd ripd sasyncd smtpd switchd unwind vmd.
Yup, hence my addition.
> ldapd
On Sat, Jan 04, 2020 at 04:08:47PM +0100, Mark Kettenis wrote:
> I don't think this should print "configuartion OK" when there are no
> errors. The UNIX way is to just return 0 and be done.
For what it's worth most daemons currently print "configuration OK":
bgpd dvmrpd eigrpd httpd ifstated
> Date: Fri, 3 Jan 2020 21:46:29 +0100
> From: Klemens Nanni
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
>
> With the hv_config() now in, `ldomctl init-system -n ldom.conf' to only
> parse configuration is trivial.
>
> It is usable as unprivileged user, no devices
On Fri, Jan 03, 2020 at 09:46:29PM +0100, Klemens Nanni wrote:
> +Only check the configuration file for validty.
"validity" fixed in my tree.
With the hv_config() now in, `ldomctl init-system -n ldom.conf' to only
parse configuration is trivial.
It is usable as unprivileged user, no devices are touched.
If errors occur, errors will be generated and ldomctl exits; if all is
valid, this prints "configuration OK" just like vmd(8) does.
