On Aug 1, 2008, at 10:09 AM, Rob van der Heij wrote:
On Fri, Aug 1, 2008 at 4:40 PM, Alan Altmark
<[EMAIL PROTECTED]> wrote:
And while I'm halucinating, I would have a command that adds and
deletes
users from an autolog list. The list is in the warm start area. No
requirement for AUTOLOG1 unless you want it. Oh, and the autologs
would
be paced to ensure that the system is not brought to its knees
during IPL.
We did run PROP in AUTOLOG2 and it would also get the message when the
autologged user went away, it allowed the operator to check the
status, etc. It allowed people to add things to the list (also users
could request their own server to be started). IIRC we had a disk with
a file per userid to be autologged, and the file itself had
information about when it should be started and on what system and who
to alert when it broke.
I think David recently also did something like this.
If by "David," you mean "Adam," then yes, the answer is we did, it was
SYSVINIT. It's at http://download.sinenomine.net/sysvinit/
It wasn't quite as sophisticated as all that, but it's a lot more
sophisticated than a list of XAUTOLOGS interspersed with CP SLEEPS.
The URL in the WAAV presentation there is no longer valid. But if you
got to the WAAV presentation, you're there.
The community response to SYSVINIT was deafening silence, which sort
of surprised me, as it really DID provide a nice flexible mechanism
for automating startup with real dependency checking. Although the
log disk fills up--I never got around to adding an autocleaner to it--
and I never got midnight message trapping to work correctly.
Still, if there's actually SOME interest in it, I might be eventually
persuaded to address that. If not, hey, it's all Rexx, so feel free.
Adam
