similar to: Upgrade from 4.7 to 5.2 problem with udev and ssl

Hi, I have upgraded an Asterisk installation with a Xorcom BRI Astribank that was working under Ubuntu 8.04 to Ubuntu 9.10 and the device is no longer initialized. When I reload the udev rules, I see that the rules seems to be correctly loaded: udevd[452]: reading '/etc/udev/rules.d/40-xpp.rules' as rules file However, these rules do not seem to be triggered: # udevadm trigger

On Dec 15, 2013, at 2:03 PM, David C. Rankin wrote: > On 12/14/2013 09:04 PM, Charles Lepple wrote: >>> Is there someway nut can be modified to probe the 0664 permission usb >>> devices >>>> and then connect as root before dropping permissions back to the "nut" >>>> gid? >> Given that the udev method should still work (and seems to, for

Hi. I'm using nut with debian squeeze. When the computer boots and nut is loaded, I get the following messages: "Starting the hotplug events dispatcher: udevdudevd [451]: BUS= will be removed in a future udev version. please use SUBSYSTEM= to match the event device. or SUBSYSTEMS= to match a parent device. in /lib/udev/rules.d/52-nut-usb.rules:6 . Synthesizing the initial hotplug

Hi, seems there is one missing change in /trunk/scripts/udev/nut-usbups.rules.in BUS -> SUBSYSTEMS previous change [1] missed this. Now, the latest udev started to complain: > ... udevd[31526]: BUS= will be removed in a future udev version ... 098 udev version (from 2006) is required for this [2], but this is the same version as required for previous SYSFS -> ATTR change. I've

Hi, I would like to change permissions of /dev/sda* and /dev/hda* files to 0644. I added the following rules to 99-udev.rules files: KERNEL=="[hs]d*", OWNER="root" GROUP="disk", MODE="0644 After restarting udev by strat_udev, I checked that permissions were changed: [root at gini rules.d]# ll /dev/sda* brw-r--r-- 1 root disk 8, 0 Sep 2 2009 /dev/sda

Thought I would write some notes about how I got an APC BackUPS XS 1500 working with newhidups under Gentoo 2006.0. The specific issue here is the permissions on the device files used that libusb uses to access the USB hardware. I followed Peter Selinger's instructions at http://www.mscs.dal.ca/~selinger/ups/backups.html on getting newhidups going with an APC device. The sticking point for

Package: xen-hypervisor-4.1-i386 Version: 4.1.1-1 Severity: important Tags: wheezy I cannot boot a domU with networking after installing the package. root at topsail:~# xm create /etc/xen/udevtest.cfg -c root at topsail:~# Error: Device 0 (vif) could not be connected. Hotplug scripts not working. [2011-08-03 15:56:53 4411] DEBUG (DevController:139) Waiting for devices tap2. [2011-08-03

G'day, all! It's my second trouble with NUT. Latest nut-2.6.1.tar.gz installed from source on Xenserver 5.6 SP2, UPS is Powercom WOW--500U FW3.A4 (USB). Problem with setting permissions for udev (described in /etc/udev/rules.d/52-nut-usbups.rules file): ACTION!="add|change", GOTO="nut-usbups_rules_end" don't work for me. Only when I changed ACTION to:

On Fri, Nov 14, 2014 at 07:32:46PM +0000, mallu mallu wrote: > I upgraded my container from CentOS 6.4 to CentOS 6.5. Everything looks good after upgrade until reboot. When rebooted to container I'm getting the following errors.. Any help would be greatly appreciated > /bin/mknod: `/dev/lp2': Operation not permitted > /bin/chown: cannot access `/dev/lp2': No such file or

I need direction. I don't know what to google for anymore. I am unable to get my SmartUPS 2200XL to be recognized. My suspicions are that it's UDEV or Kernel related. I've updated the kernel to the highest version I feel comfortable with due to other things that run on the server, and I've updated UDEV a bit too. When I plug in the USB cable from the UPS into the server, I

I upgraded my container from CentOS 6.4 to CentOS 6.5. Everything looks good after upgrade until reboot. When rebooted to container I'm getting the following errors.. Any help would be greatly appreciated /bin/mknod: `/dev/lp2': Operation not permitted /bin/chown: cannot access `/dev/lp2': No such file or directory /bin/mknod: `/dev/lp3': Operation not permitted /bin/chown: cannot

On Apr 23, 2014, at 3:47 AM, Frantz de Germain wrote: > I've compiled and installed nut-2.7.2 on a Xen server (Actually XCP > 1.6/Centos 5.7) to manage a Dell UPS 2700W. > > Here is my ups.conf : > > [SU27003U-08] > driver = usbhid-ups > port = auto > desc = "SU27003U-08" > > 52-nut-usbups.rules have well been installed in

On 12/14/2013 09:04 PM, Charles Lepple wrote: >> Is there someway nut can be modified to probe the 0664 permission usb >> devices >>> and then connect as root before dropping permissions back to the "nut" >>> gid? > Given that the udev method should still work (and seems to, for handcrafted > udev rules files), I would like to run that to ground first.

Forwarded to centos mailing list -----Original Messages----- From: wuzhouhui <wuzhouhui14 at mails.ucas.ac.cn> Sent Time: 2018-10-30 14:06:00 (Tuesday) To: "storage performance development kit" <spdk at lists.01.org> Cc: centos at centos.org, qemu-discuss at nongnu.org Subject: Re: [SPDK] VM boot failed sometimes if using vhost-user-blk with spdk I enable debug of

Hi, We seem to be hitting an issue where libguestfs keeps hanging. virt-resize, guestmount etc.. never complete. If we set LIBGUESTFS_BACKEND_SETTINGS=force_tcg it completes. The issue starts when updating to CentOS 7.4 (CentOS 7.3 work fine). It doesn't seem to affect all 7.4 hypervisors and the only similarity that we have found is that they all use NVMe drives. Non-Volatile memory

I am migrating from Fedora 8 to CentOS 5.2 I have usb dvd On F8 I have /etc/udev/rules/00-my-custom.rules BUS=="scsi", SYSFS{vendor}=="TSSTcorp", SYSFS{model}=="CDDVDW SH-S203N ",SYMLINK="dvd",OWNER="rray" When I plug in dvd I get $ ll /dev/scd1 lrwxrwxrwx 1 root root 3 Aug 25 08:17 /dev/scd1 -> sr1 ll /dev/sr1 brw-r----- 1 rray disk 11, 1

Hi, I have a UPS device that seems to work fine with the blazer_usb driver. (I have guessed the driver by googling up the "Product" usb string 010937). However, it does not appear in the supported list, and I had to manually add a udev rule for granting access to the 'nut' user. Would be nice if the info I provide below could be used to help the project/future users to

Hi, Sometimes, I found one of my Mellanox NIC renamed to rename6, instead of eth1. The right names of NICs in my system should be: eth0 Mellanox NIC eth1 Mellanox NIC eth2 Intel NIC eth3 Intel NIC eth4 Intel NIC eth5 Intel NIC eth0 and eth1 will combined as bond1 with mode 4. However, the current names are: eth0 Mellanox

Hi Pawel, 2011/7/26 Pawel Sikora <pluto at agmk.net> > On Tuesday 26 of July 2011 14:33:15 you wrote: > > Hi Pawel, > > > > 2011/7/26 Pawel Sikora <pluto at agmk.net> > > > > > Hi, > > > > > > i have an orvaldi ups > > > http://en.orvaldi.com/index.php/en/product_catalog/product_view/11/162 > > > and it works

On Tue, 26 Feb 2019 16:17:21 -0800 si-wei liu <si-wei.liu at oracle.com> wrote: > On 2/25/2019 6:08 PM, Michael S. Tsirkin wrote: > > On Mon, Feb 25, 2019 at 04:58:07PM -0800, si-wei liu wrote: > >> > >> On 2/22/2019 7:14 AM, Michael S. Tsirkin wrote: > >>> On Thu, Feb 21, 2019 at 11:55:11PM -0800, si-wei liu wrote: > >>>> On