Good Day Serge Hallyn Thank You for the reply
You may have inadvertently solved this bug. Your questions: ls -l /etc/udev/rules.d total 16 -rw-r--r-- 1 root root 1450 Jul 23 09:23 56-hpmud.rules lrwxrwxrwx 1 root root 37 Mar 24 14:36 62-nut-usbups.rules -> /lib/udev/rules.d/62-nut-usbups.rules -rw-r--r-- 1 root root 794 Aug 3 15:52 70-persistent-cd.rules -rw-r--r-- 1 root root 670 Mar 23 19:53 70-persistent-net.rules -rw-r--r-- 1 root root 1157 Apr 5 2012 README cat /var/log/upstart/nut.log cat: /var/log/upstart/nut.log: No such file or directory cat /var/log/upstart/udev.log cat: /var/log/upstart/udev.log: No such file or directory My /var/log/udev.txt file in tar is almost 300kb. Do you really want it? Now my solution. Your text says that nut ships a 52 file and not a 62 file but I definitely have a reference to a 62 file because everything I did on the bug report was cut and pasted. The above rules.d 62 file links as shown to /lib/udev/rules.d/62-nut-usbups.rules. You wrote nut ships with a 52 file. It was logical to marry these two files up. I changed the link properties in /etc/udev/rules.d62-nut-usbups.rules from 62 to 52 but leaving the filename the same. No more error message in boot.log! The 62 file is mentioned prominently in CENTOS and Red Hat. Maybe, someone somewhere should have include a 52 file instead of a 62 file. I don't know but my dirty fix works! Thank You for your help -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/1209020 Title: nut - "udevd[433]: can not find '/etc/udev/rules.d/62-nut- usbups.rules': No such file or directory" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1209020/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
