Hi David, Thank you for bringing up this topic again. No, unfortunately there was no other solution than to rerun the commands.
I think there should be an option for chccwdev to wait till DE/CE is received and not to terminate with device busy. Kind regards, Florian On Thu, Jul 26, 2012 at 6:52 PM, David Boyes <[email protected]> wrote: > A week or two back, someone (I think it was Florian Bilek) asked why there > was a delay between invoking chccwdev and the device becoming available, > and whether there was an option or command that would exit only when the > device was actually available. There was some discussion of the --settle > option in udev, but I don't recall seeing a resolution other than "loop on > (test for device availability;sleep a few seconds) repeat". > > Was there a better solution? If not, could the IBM developers add a --sync > option to chccwdev that forces chccwdev to wait until the requested > operation is actually completed before exiting? > > ---------------------------------------------------------------------- > 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 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
