After switching o the new syntax for 66-tools, my nfs service is no longer working. I can't trace any change in config files, buit I get below warnings
silversurfer@ Ob66 ~ % sudo 66-start -R nfs-server
66-start: info: Already down: rpc.mountd
66-start: info: Already down: rpc.statd
66-start: info: Already down: rpcbind
umount: ${cmd_args_fs}: no mount point specified.
umount: : no mount point specified.
umount: ${cmd_args_nfsd}: no mount point specified.
66-start: info: Stopped successfully: nfs-server
66-start: info: Stopped successfully: nfs-utils
66-start: info: Stopped successfully: nfs-mounts
66-start: info: Stopped successfully: nfs-modules
66-start: info: Already down: nfs-server
66-start: info: Already down: rpc.mountd
66-start: info: Already down: rpc.statd
66-start: info: Already down: nfs-utils
66-start: info: Already down: nfs-mounts
66-start: info: Already down: nfs-modules
66-start: info: Already down: rpcbind
s6-mount: fatal: unable to mount ${cmd_args_fs} on : No such file or directory
s6-mount: fatal: unable to mount ${cmd_args_nfsd} on : No such file or directory
66-start: warning: unable to start: rpcbind
66-start: info: Started successfully: nfs-modules
66-start: info: Started successfully: nfs-mounts
66-start: info: Started successfully: nfs-utils
66-start: warning: unable to start: rpc.statd
66-start: warning: unable to start: rpc.mountd
66-start: info: Started successfully: nfs-server
66-start: fatal: unable to start atomic services list
It seems somethings is wrong/missing for cmd_args_fs/cmd_args/nfsd. The nfs server is working ok on another box, can't see big differences on the environment args.
Anyone with a hint with a direction to look at?