Trying to use on a custom robot: failure to find *.xacro

[rcpilotp51]

This is the error I'm getting:

`robot.service - "bringup robot"
Loaded: loaded (/lib/systemd/system/robot.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2019-01-05 14:22:12 EST; 39s ago
Process: 25391 ExecStart=/usr/sbin/robot-start (code=exited, status=1/FAILURE)
Main PID: 25391 (code=exited, status=1/FAILURE)

Jan 05 14:22:11 RobotVM systemd[1]: Started "bringup robot".
Jan 05 14:22:11 RobotVM robot-start[25391]: <14>Jan 5 14:22:11 root: robot: Using workspace setup file /home/kbrown/robot_ws/devel/setup.bash
Jan 05 14:22:11 RobotVM root[25418]: robot: Launching ROS_HOSTNAME=RobotVM, ROS_IP=, ROS_MASTER_URI=http://127.0.0.1:11311, ROS_HOME=/home/kbrown/.ros, ROS_LOG_DIR=/tmp
Jan 05 14:22:11 RobotVM robot-start[25391]: <14>Jan 5 14:22:11 root: robot: Launching ROS_HOSTNAME=RobotVM, ROS_IP=, ROS_MASTER_URI=http://127.0.0.1:11311, ROS_HOME=/home/kbrown/.ros, ROS_LOG_DIR=/tmp
Jan 05 14:22:12 RobotVM robot-start[25391]: ls: cannot access '/etc/ros/kinetic/robot.d/*.xacro': No such file or directory
Jan 05 14:22:12 RobotVM robot-start[25391]: <14>Jan 5 14:22:12 root: robot: Generated launchfile: /tmp/robot.launch
Jan 05 14:22:12 RobotVM robot-start[25391]: <11>Jan 5 14:22:12 root: robot: Can't launch as unprivileged user without setuidgid. Please install daemontools package.
Jan 05 14:22:12 RobotVM systemd[1]: robot.service: Main process exited, code=exited, status=1/FAILURE
Jan 05 14:22:12 RobotVM systemd[1]: robot.service: Unit entered failed state.
Jan 05 14:22:12 RobotVM systemd[1]: robot.service: Failed with result 'exit-code'.`

any suggestions on launching a custom launch file on startup?

[k-okada]

I had same situation and found this is not because of "*.xacro", but

 Can't launch as unprivileged user without setuidgid. Please install daemontools package.

so install daemontools solved the problem