Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!pmafire!uudell!bigtex!texsun!sundc!newstop!exodus!shukra.Eng.Sun.COM!ram
From: ram@shukra.Eng.Sun.COM (Renu Raman)
Newsgroups: comp.sys.super
Subject: Re: NQS info wanted (do we need a FAQ posting?)
Keywords: NQS, CRAY, CRI
Message-ID: <5331@exodus.Eng.Sun.COM>
Date: 5 Jan 91 16:17:50 GMT
References: <1991Jan4.171447@obelix.anu.edu.au> <1991Jan4.181847.24382@nas.nasa.gov> <012352.8054@timbuk.cray.com>
Sender: news@exodus.Eng.Sun.COM
Organization: Sun Microsystems, Mt. View, Ca.
Lines: 29

In article <012352.8054@timbuk.cray.com> glover@sequoia.cray.com (Roger Glover) writes:
>
>
>In article <1991Jan4.181847.24382@nas.nasa.gov> eugene@wilbur.nas.nasa.gov (Eugene N. Miya) writes:
>>
>>M88-10054 Sterling
>>NOS- NETWORK OUEUEING SYSTEM
>

  While on the subject of NQS - can somebody out there help me?

     I have two problems so far

	a) WHen I start a substantially large process, NQS kills the job
	   saying "not enough memory". Obviously the process is hitting
	   some memory limits imposed by NQS. I want to circumvent it.
	   (Yes, I know about the options one can specify to alter
	   limits)
        b) I am unable to queue a job from one machine onto another.
	   i.e. remote submission does not seem to work.

   THanks

   renu raman
--
--------------------------------
   Renukanthan Raman				ARPA:ram@sun.com
   M/S 18-412, 2500 Garcia Avenue,              TEL :415-336-1813
   Sun Microsystems, Mt. View,  CA 94043