Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!emory!gatech!purdue!mentor.cc.purdue.edu!mace.cc.purdue.edu!abe
From: abe@mace.cc.purdue.edu (Vic Abell)
Newsgroups: comp.unix.aix
Subject: Re: Does SIGXCPU work under AIX 3.1?
Message-ID: <6894@mace.cc.purdue.edu>
Date: 26 Feb 91 20:20:54 GMT
References: <6893@mace.cc.purdue.edu> <22867@hydra.gatech.EDU>
Reply-To: abe@mace.cc.purdue.edu (Vic Abell)
Organization: Purdue University
Lines: 21

In article <22867@hydra.gatech.EDU> scott@prism.gatech.EDU (Scott Holt) writes:
>
>In short - no. SIGXCPU does not work.
>
.
.
.
>For us, the ability to have a CPU time limit is crucial - we plan to implement
>a processor farm of sorts managed by a batch management system such as NQS.

That's why I asked the question. We're near the end of the single-machine
NQS port and looking at production and network scheduling issues.

Another AIX 3.1 deficiency that affects NQS is the lack of support for csh's
/etc/.login environment support.  The /etc/environment support is login-
specific, /etc/profile only supports sh and ksh, so NQS has no ready way to
influence the environment of those who use csh under NQS - e. g., setting
the TZ environment variable.  It will be interesting to see what IBM's
answer will be to that defect.  :-)

Vic Abell


Brought to you by Super Global Mega Corp .com