Well, personally, I think it would be better to address this totally from the Linux side. That is a "program" or script which could tell all processes: Harden your data to disk and suspend processing. The process would respond by hardening any data in its cache, then "do something" so that it would become nondispatchable to the zLinux kernel. After all processes have "done this something", the program/script would then harden all cached information to disk. It would then do the "snap" itself (or even do a DIAG 8 to tell z/VM to do it, if necessary). Once the "snap" is done, it would tell all processes: "restart processing". Or tell the kernel to release the processes which went into that voluntary nondispatchabel state previously mentioned.
I do not really see the above happening, however. It would be a change in the kernel which is specific to zSeries processing. I am under the impression that the "kernel gods" want to avoid hardware specific mods as much as possible. -- John McKown Senior Systems Programmer UICI Insurance Center Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. ---------------------------------------------------------------------- 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
