On Thu 03 Jan 2002, Glenn Maynard wrote:
>
> By default, find doesn't follow links. When forced to (-follow), it
> keeps track of inodes and doesn't enter the same directory twice.
I wish diff -r did the same :-(
Paul Slootman
On Wed, Jan 02, 2002 at 06:45:53PM -0600, Bryan Andersen wrote:
> > > on a simple 'find /var -name sendmail* -print' command, the find-process
> > > eats all my memory (128 Meg RAM)
> > > when there is no memory left, the process gets killed.
Some information about the output (or lack thereof) mig
On Wed, Jan 02, 2002 at 06:45:53PM -0600, Bryan Andersen wrote:
> Andreas Rottmann wrote:
> >
> > Michael De Nil <[EMAIL PROTECTED]> writes:
> >
> > > Hi
> > >
> > > on a simple 'find /var -name sendmail* -print' command, the find-process
> > > eats all my memory (128 Meg RAM)
> > > when there is
Andreas Rottmann wrote:
>
> Michael De Nil <[EMAIL PROTECTED]> writes:
>
> > Hi
> >
> > on a simple 'find /var -name sendmail* -print' command, the find-process
> > eats all my memory (128 Meg RAM)
> > when there is no memory left, the process gets killed.
> >
> > I work with debian woody with re
Michael De Nil <[EMAIL PROTECTED]> writes:
> Hi
>
> on a simple 'find /var -name sendmail* -print' command, the find-process
> eats all my memory (128 Meg RAM)
> when there is no memory left, the process gets killed.
>
> I work with debian woody with recent update, reiserfs, 128 meg RAM & 256
>
Hi
on a simple 'find /var -name sendmail* -print' command, the find-process
eats all my memory (128 Meg RAM)
when there is no memory left, the process gets killed.
I work with debian woody with recent update, reiserfs, 128 meg RAM & 256
meg SWAP on my P3 733 system.
Here is what I get using 'top
6 matches
Mail list logo
