Seems to me CP already has most of this code path anyway. The free
storage limit detection will stop a machine in its tracks after the
second violation. It puts the errant machine into CP READ stopped state.
In the distant past I made some presentations on this - I'll dig
around. How deep and true this stopped state is - don't know - but
likely its a reasonable stoppage.
David Kreuter
Rob van der Heij wrote:
On 4/7/06, Phil Smith III <[EMAIL PROTECTED]> wrote:
Well, that capability isn't that hard -- V/SPOOL (now part of
CA-somethingorother-VM:Spool V/SEG-PLUS feature) has a FREEZE capability, and
ISTR it was a few lines in the right place in CP to keep the guest from being
dispatched.
I suppose you could even issue a SEND CP xxx SLEEP to stop Linux from
working, but it would cause things to time out and sessions to drop
when it takes a bit longer.
Especially with LVM, it is hard to avoid inconsistency when the backup
of the physical volumes is not done at the same time. But with LVM you
can quiesce the disk for a moment to allow the backups to be taken.
--
Rob van der Heij
Velocity Software, Inc
----------------------------------------------------------------------
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 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
