John Summerfied wrote: > Carsten Otte wrote: > >> Rick Troth wrote: >> >>> Lock the file. >>> Or have the device driver enforce single access. >> >> >> But why lock? CP can handle multiple parralel diag8 > > > As I recall someone asserted there's a problem getting the proper cp > feedback at present. VM return codes don't map to *x return codes, so > another action is needed to get the VM return code and publish it some > place a script can use it. > > Without locking, this will fail from time to time. No it will not _if_ the lock is done where it belongs: system kernel, not flock or sysfs or whatever vehicle that locks in userspace. That's what vmcp does, and that's what would work for other diagnoses in a similar way. --
Carsten Otte IBM Linux technology center ARCH=s390 ---------------------------------------------------------------------- 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
