--- Greg Woodhouse <[EMAIL PROTECTED]> wrote:
>
> A thought: Why notstart a background job (not a task) that goes into
> a
> loop, repeaetedly sleeping (say 10 seconds), waking up and checking
> to
> see if KIDS is still running, and if it is, going back to sleep? If
> KIDS terminates abnormal
I've seen this happen before (a number of times, actually). By way of
background, KIDS gives you the opportunity to disable logins when
installing patches or packages, and the installation instructions often
tell you to do so. The danger in not doing so is that it is possible
that someone will atte
Just thought I'd post a followup. Thanks for the suggestion offered too!
It was definitely 'weird'...
Background: previously we had a site license of Cache, and were used to
bumping into our license limit of ~180 users on the system
simultaneously, and then not being allowed access. However, r
hey LUKE
Guess someoone messed with your Volume set file or while installing a KID set the option "Inhibit logons" to 'yes'.
You have to Set the "INHIBIT LOGONS?:" field of "VOLUME SET" file to "NO"
You could do that from "EVE" (system manager's menu) but you you are not able to log i
Looking for a lead here... our Vista/RPMS system started something new
to us this morning...
SEARHC>D ^XUS
Volume set: AKM:SEARHC UCI: SEARHC Device: /dev/pts/5
Device: /dev/pts/5
Signons not currently allowed on this processor.
The Solaris server seems fine, Cache seems fine, but it see
