From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6463 invoked from network); 10 Nov 2003 10:26:39 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 10 Nov 2003 10:26:39 -0000 Received: (qmail 7979 invoked by alias); 10 Nov 2003 10:23:49 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 19231 Received: (qmail 7937 invoked from network); 10 Nov 2003 10:23:48 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 10 Nov 2003 10:23:48 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [213.97.199.90] by sunsite.dk (MessageWall 1.0.8) with SMTP; 10 Nov 2003 10:23:46 -0000 Received: (qmail 15983 invoked by uid 500); 10 Nov 2003 10:24:11 -0000 Date: Mon, 10 Nov 2003 11:24:10 +0100 From: David =?iso-8859-15?Q?G=F3mez?= To: Bart Schaefer Cc: Zsh-workers Subject: Re: Strange problem with ulimit Message-ID: <20031110102410.GA15979@fargo> Mail-Followup-To: Bart Schaefer , Zsh-workers References: <20031108095037.GA11894@fargo> <20031109161853.GL22980@DervishD> <1031109212136.ZM14473@candle.brasslantern.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1031109212136.ZM14473@candle.brasslantern.com> User-Agent: Mutt/1.4.1i Hi Bart ;), On Nov 09 at 09:21:36, Bart Schaefer wrote: > [Hmm, I don't seem to have received the first message in this thread.] I won't be surprised that some messages are lost at the mail servers. These last days i'm being hitted (again) by the infamous "Microsoft support" virus, and i guess several mail servers are being bombed too... > The "ulimit" builtin is not a full-fledged builtin -- it's supplied by > the zsh/rlimits module. Aha, i didn't know that it was supplied by the rlimits module... > Even though that module is normally linked to > the base executable (rather than dynamically loaded), Are there more builtins with this behavior? > Modules are zmodload'd automatically at startup only when the shell is > invoked as zsh. This is to prevent clashes with command and variable > names used e.g. by "sh" scripts that are expecting a clean namespace. Ok, thanks for the info. I justed wanted to know if it was a expected behavior or some kind of bug. Cheers, -- David Gómez "The question of whether computers can think is just like the question of whether submarines can swim." -- Edsger W. Dijkstra