Hi, I have a script that does a FLASHCOPY, then a "chccwdev -e" against the newly copied disk. It seemed that the chccwdev command finished asynchronously. In the past I had a "sleep 1" which seemed to allow enough time for the command to finish, but I got comments that "udevsettle", or "udevadm settle" were the preferred method of waiting for chccwdev to finish. So I now use "udevadm settle" and it seemed to also work fine.
Until today... I ran the script and it didn't complete for a few minutes. I isolated the delay to the "udevadm settle" command. Now I run it from the command line and see: # time udevadm settle After the udevadm settle timeout, the events queue contains: 415: /devices/css0/0.0.000d/0.0.1100 416: /devices/css0/0.0.000d 423: /devices/css0/0.0.000d 424: /devices/css0/0.0.000d/0.0.1102 427: /devices/css0/0.0.000d/0.0.1102 428: /devices/css0/0.0.000d 431: /devices/css0/0.0.000d 432: /devices/css0/0.0.000d/0.0.1102 435: /devices/css0/0.0.000d/0.0.1102 436: /devices/css0/0.0.000d real 3m0.929s user 0m0.008s sys 0m0.044s It seems that udevadm settle is timing out after three minutes. Has anyone seen this, or can explain it? Thanks. "Mike MacIsaac" <[email protected]> (845) 433-7061 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
