On Jun 11, 2017, at 8:10 AM, Andrea de Lutti <adelu...@gmail.com> wrote: > > What's the right procedure for loading driver/daemon at boot? > I have read a lot about /var/run/nut missing, but haven't find any > solution....
Your copy of /etc/init.d/nut-server should have the following lines: # Check if /var/run/nut exists and has the correct perms check_var_directory() { [ ! -d ${pid_dir} ] && mkdir -p ${pid_dir} \ && chown root:nut ${pid_dir} \ && chmod 770 ${pid_dir} \ && [ -x /sbin/restorecon ] && /sbin/restorecon ${pid_dir} } This works on my Ubuntu 16.04 test system. I am using a PPA with some libusb-1.0 changes, but this particular file does not seem to have changed since Ubuntu 14.04 (looks like there is some systemd emulation of SysV-style init scripts for NUT on 16.04). Are you using systemd or upstart? _______________________________________________ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser