Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!rutgers!mit-eddie!genrad!decvax!tektronix!reed!nscpdc!joer From: joer@nscpdc.NSC.COM (G. Wiz) Newsgroups: comp.unix.wizards Subject: Re: Peculiar behaviour of ulimit(2) Message-ID: <876@nscpdc.NSC.COM> Date: Wed, 1-Jul-87 13:09:19 EDT Article-I.D.: nscpdc.876 Posted: Wed Jul 1 13:09:19 1987 Date-Received: Sat, 4-Jul-87 08:52:34 EDT References: <185@augean.OZ> Reply-To: joer@nscpdc.UUCP (G. Wiz) Distribution: world Organization: NSC Portland Development Center Lines: 30 In article <185@augean.OZ> idall@augean.OZ (Ian Dall) writes: > >On my SysV.2.2 system ( National Semiconductors port for the ICM-3216 ) >the ulimit(2) system call seems to misbehave. >The question is: Is this a bug or a feature? >If it's a bug, is it generic to SysV or just this port of it? > >Ian Dall This WAS a bug in an earlier release. I do not know if it was generic SysV or if it was our port. None the less, it has been repaired. I would like to say that asking the world about alleged bugs in a specific implementation is not the best way to get a resolution (nor is it a nice thing to do). In general, the world does not have the answer to that type of question. It is better to ask the manufacturer directly over the provided support phone line (free to licensed users in U.S.). I realize that you are in Australia. You can email directly to me if you choose not to call, (hours being different here and all). Cheers, -- /****************************************************************************** * * * Joe Rawlings nsc!nscpdc!joer or * * ICM Product Support tektronix!reed!nscpdc!joer * * National Semiconductor Corp. 1-800-222-2433 (outside Oregon) * * Portland Development Center or 629-4414 (inside Oregon) * * * ******************************************************************************/