search for: udevadm

On Thursday, 13 April 2017 16:55:26 CEST Pavel Butsykin wrote: > Add udev_settle_file() to run 'udevadm settle' with --exit-if-exists option. It > will slightly reduce the waiting-time for pending events if we need to wait > for events related to a particular device/file. > > Signed-off-by: Pavel Butsykin <pbutsykin@virtuozzo.com> > --- > daemon/daemon.h | 2 ++ >...

I'm getting a lot of this at boottime: udev still not settled. Waiting. udevadm settle - timeout of 0 seconds reached, the event queue contains: /sys/module/scsi_wait_scan (11707) udev still not settled. Waiting. udevadm settle - timeout of 0 seconds reached, the event queue contains: /sys/module/scsi_wait_scan (11709) udev still not settled. Waiting. udevadm settle - ti...

On Wed, Apr 12, 2017 at 05:01:10PM +0300, Pavel Butsykin wrote: > Add udev_settle_file() to run 'udevadm settle' with --exit-if-exists option. It > will slightly reduce the waiting-time for pending events if we need to wait > for events related to a particular device/file. > > Signed-off-by: Pavel Butsykin <pbutsykin@virtuozzo.com> > --- > daemon/daemon.h | 2 ++ >...

...0x00007ffff6f77701 in _Py_INCREF (op=<optimized out>) at /usr/include/ > python3.9/object.h:408 > #3 ?guestfs_int_py_event_callback_wrapper > ? ? (g=<optimized out>, flags=<optimized out>, array_len=0, array=0x0, buf_len= > 47, buf=0x113b8a0 "gs=0x0\r\ncommandrvf: udevadm --debug settle -E \303by", > event_handle=0, event=16, callback=0x7ffff2516600) at handle.c:137 > #4 ?guestfs_int_py_event_callback_wrapper > ? ? (g=<optimized out>, callback=0x7ffff2516600, event=16, event_handle=0, > flags=<optimized out>, buf=0x113b8a0 "gs=0x0\r...

There is GUESTFSD_EXT_CMD defining a string for udevadm (so it is marked as "used tool" in the appliance), but it is not actually used when starting udevadm. There should be no behaviour change. --- daemon/guestfsd.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/daemon/guestfsd.c b/daemon/guestfsd.c index 7b33a3a..450...

Processing commands for control at bugs.debian.org: > reassign 456330 xen-3 Bug#456330: use udevadm instead of udevinfo Warning: Unknown package 'xen-3.1' Bug reassigned from package `xen-3.1' to `xen-3'. > -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)

...u/libpthread.so.0 #2 0x00007ffff6f77701 in _Py_INCREF (op=<optimized out>) at /usr/include/python3.9/object.h:408 #3 guestfs_int_py_event_callback_wrapper (g=<optimized out>, flags=<optimized out>, array_len=0, array=0x0, buf_len=47, buf=0x113b8a0 "gs=0x0\r\ncommandrvf: udevadm --debug settle -E \303by", event_handle=0, event=16, callback=0x7ffff2516600) at handle.c:137 #4 guestfs_int_py_event_callback_wrapper (g=<optimized out>, callback=0x7ffff2516600, event=16, event_handle=0, flags=<optimized out>, buf=0x113b8a0 "gs=0x0\r\ncommandrvf: udevad...

...be polite, would it ? Beware that despite the heavy backporting done by RH, fedora is far ahead of RHEL 7 and very far ahead of RHEL 6 ( especially in terms of libraries ) > > Does udev automatically reload when the rules files change? The Debian/Ubuntu packages are supposed to run "udevadm trigger --subsystem-match=usb --action=change" as part of the postinst. I've stolen from the fedora package the following gem which , AFAIK ( I am no udev wizard.. ) does the same thing: postinstall scriptlet (using /bin/sh): /sbin/ldconfig udevadm control --reload ||: > (I think ude...

...devd /usr/lib/systemd/systemd-udevd /sbin/udevd /lib/udev/udevd /usr/lib/udev/udevd + '[' -x /lib/systemd/systemd-udevd ']' + UDEVD=/lib/systemd/systemd-udevd + break + '[' -z /lib/systemd/systemd-udevd ']' + /lib/systemd/systemd-udevd --daemon starting version 237 + udevadm trigger + udevadm settle --timeout=600 + shopt -s nullglob + for f in /sys/block/sd*/device/timeout + echo 300 + for f in /sys/block/sd*/device/timeout + echo 300 + for f in /sys/block/{h,s,ub,v}d*/queue/scheduler + echo noop /init: line 116: echo: write error: Invalid argument + for f in /sys/bloc...

On Thu, Apr 13, 2017 at 07:01:09PM +0300, Pavel Butsykin wrote: > I missed that that reply_with_error is not just error output, but may > lead to termination of the client. Agree. That's right -- reply_with_error sends a protocol message back to the client, so it's important to only call it when the client (ie. the library) is expecting it. In this case, just ignore the error or

My network installation via PXE breaks when graphical installation starts, here my program.log: Running... /bin/mount -n -t auto -o ro,loop=/dev/loop0 /tmp/install.img /mnt/runtime 07:51:29,617 INFO : Running... ['udevadm', 'trigger', '--action=add', '--subsystem-match=net'] 07:51:29,660 INFO : Running... ['udevadm', 'trigger', '--action=add', '--subsystem-match=block'] 07:51:29,812 INFO : Running... ['udevadm', 'settle', '--timeou...

...38,31 +1038,19 @@ device_name_translation (char *device, const char *func) * involved. eg. You can create or remove some device, but the /dev * device node won't appear until some time later. This means that * you get an error if you run one command followed by another. + * * Use 'udevadm settle' after certain commands, but don't be too * fussed if it fails. + * + * 'udevsettle' was the old name for this command (RHEL 5). This was + * deprecated in favour of 'udevadm settle'. The old 'udevsettle' + * command was left as a symlink. Then in Fedora...

...port=auto After dealing hours with this, hope this will help some : rename udev rule to higher priority and move it to its right location, reload udev rules mv /lib/udev/rules.d/52-nut-usbups.rules /lib/udev/rules.d/62-nut-usbups.rules cp /lib/udev/rules.d/62-nut-usbups.rules /etc/udev/rules.d/ udevadm control --reload-rules udevadm trigger reboot server to be sure everything is OK Nicolas upsc HPR1500 Init SSL without certificate database battery.charge: 100 battery.charge.low: 20 battery.charge.warning: 20 battery.runtime: 24171 battery.temperature: 46.0 battery.type: PbAc battery.voltage: 41...

...t > #0 ?0x00007f6dd17b4701 in _Py_INCREF (op=<optimized out>) at /usr/include/ > python3.9/object.h:408 > #1 ?guestfs_int_py_event_callback_wrapper > ? ? (g=<optimized out>, flags=<optimized out>, array_len=0, array=0x0, buf_len= > 43, buf=0xd1dc90 "commandrvf: udevadm --debug settle -E /\347\232\204\303 > available\r\ned7 > #2 ?guestfs_int_py_event_callback_wrapper > ? ? (g=<optimized out>, callback=0x7f6dd19ec040, event=16, event_handle=0, > flags=<optimized out>, buf=0xd1dc90 "commandrvf: udevadm --debug settle -E /\ > 347\232\2...

I tried to use cdrom in domU linux pv (Linux Mint 11 based on Natty). With ''/mnt/vm/iso/test.iso,raw,xvdb,ro,cdrom'', Mint sees it as internal disk (not cdrom) and only administrators can mount it. I tried also ''/dev/scd0,raw,xvdb,ro,cdrom'' does the same thing. Is possible use cdrom on linux domU pv full working where also normal user can mount it without

...--------- next part -------------- >From 018e8b562b3980a002bd2f9c42cf7dab541ac005 Mon Sep 17 00:00:00 2001 From: Richard Jones <rjones at centos5x32.home.annexia.org> Date: Wed, 18 Nov 2009 16:02:53 +0000 Subject: [PATCH] daemon/RHEL: Choose correct udev settle script. On RHEL/CentOS 5.4, udevadm settle command does not work. This didn't affect us before, but now that we're using parted for partitioning, we *do* need to wait for udev to settle (because parted isn't waiting for this, unlike sfdisk). This commit chooses the correct program to run. --- daemon/guestfsd.c | 22 +...

udevadm is included in all reasonable recent distributions. This avoids 'command not found' errors in verbose mode. Signed-off-by: Olaf Hering <olaf at aepfle.de> diff --git a/daemon/guestfsd.c b/daemon/guestfsd.c index e6d5fde..0db56e4 100644 --- a/daemon/guestfsd.c +++ b/daemon/guestfsd.c...

...n a variable. This shaves off 5 grep invocations. --- appliance/init | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/appliance/init b/appliance/init index f6fe9b9..8d662fa 100755 --- a/appliance/init +++ b/appliance/init @@ -75,7 +75,9 @@ $UDEVD --daemon #--debug udevadm trigger udevadm settle --timeout=600 -if grep -sq selinux=1 /proc/cmdline; then +cmdline=$(</proc/cmdline) + +if [[ $cmdline == *selinux=1* ]]; then mount -t selinuxfs none /sys/fs/selinux fi @@ -91,16 +93,16 @@ shopt -u nullglob hwclock -u -s # Parse the kernel command line. -if gr...

netstat -lptu gives me tcp6 0 0 [::]:16514 [::]:* LISTEN 1314/libvirtd so the server is correctly listening on interfaces. My /etc/libvirt/libvirtd settings are defaulted. My /etc/default/libvirt-bin has "-d -l" options so server is listening. If I do virsh -c qemu://143.225.229.190/system (that is my ip or an ip belonging to my network) I

..."YYYY", SYMLINK+="ups0", GROUP="nut" Where idVendor and idProduct are the device manufacturer and product ID. You can see these either in the error output [XXXX:YYYY] or by using lsusb. After this is done, reload and retrigger udev rules by issuing this command: # udevadm control --reload-rules && udevadm trigger </quote> After adding the rule and calling udevadm, Bingo! Up and running. Consider adding the information about the permission errors and Udev rule to tuser-manual.html. That is the first place I thought to look, but either it missed the...