Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!lll-winken!uunet!dg-rtp!rti!mozart!sherman From: sherman@unx.sas.com (Chris Sherman) Newsgroups: comp.lang.perl Subject: Re: mg: multi-line grep Message-ID: Date: 30 May 91 05:28:50 GMT References: Sender: news@unx.sas.com (Noter of Newsworthy Events) Distribution: comp Organization: SAS Institute Inc. Lines: 43 Nntp-Posting-Host: foster.unx.sas.com In utashiro@sra.co.jp (Kazumasa Utashiro) writes: >Any comments for command itself or perl programming are >welcom. (//g is used correctly?) >--- >K. Utashiro >utashiro@sra.co.jp >---------------------------------------------------------------------- >#!/usr/local/bin/perl >'di'; >'ig00'; >;# >;# mg: multi-line grep >;# K. Utashiro >;# Original: Mar 29 1991 >;# Revised: Apr 1 1991, Apr 3 1991, Apr 4 1991, Apr 15 1991, Apr 19 1991 >;# Apr 23 1991, Apr 25 1991, May 29 1991 Great program. But I am having a problem with the recursive descent option. I'm not sure if it is the option itself, or the mere fact it allows the program to run for a longer period of time, but as soon as I start the command, my available disk space drops about 7 Megs within the first minute or so. And the more the program runs, the more disk space gets eaten. After a while, I get a Filesystem Full error. This has happened on an HP and Sun4, both running perl v4p3. The funny thing is that I can't figure out where all the disk space goes... I stopped (cntl-Z) the program and thoroughly examined the file system, and I couldn't find 7 Megs worth of new files. When I kill (kill -9) the program, the space comes back. Does anyone know what is going on here? Is the problem caused by perl, or by this neat program? Big Thanx, -- Chris Sherman .................... sherman@unx.sas.com | ,-----------------------------------------' / Q: How many IBM CPU's does it take to execute a job? | A: Four; three to hold it down, and one to rip its head off.