Re: Do too many files hurt a directory?

From: Nick Landsberg (hukolau_at_NOSPAM.att.net)
Date: 03/29/04

  • Next message: Peter J. Acklam: "Re: /usr/local/" 
    Date: Mon, 29 Mar 2004 21:20:27 GMT

    Charlie Gibbs wrote:

    > In article <Yh59c.24304$tY6.703172@bgtnsc04-news.ops.worldnet.att.net>
    > hukolau@NOSPAM.att.net (Nick Landsberg) writes:
    >
    >
    >>Charlie Gibbs wrote:
    >>
    >>
    >>>In article <d229c.23475$tY6.687474@bgtnsc04-news.ops.worldnet.att.net>
    >>>hukolau@NOSPAM.att.net (Nick Landsberg) writes:
    >>>
    >>
    >>[SNIP]
    >>
    >>Charlie, to change the subject back almost to the
    >>original.
    >>
    >>Now that the current problem is "fixed" ...
    >>
    >>The process which created all those files is
    >>downright dangerous! You would probably be
    >>doing your client a favor if you tracked it
    >>down and filed a MAJOR trouble report with the
    >>vendor. (And charged appropriately for the tracking
    >>down, etc.)
    >
    >
    > That's easy. I wrote it. :-) It's a sort utility; I still
    > don't know how it ran off creating all those files, but this
    > problem was just one of many that resulted from the customer
    > running our application as root instead of under the proper
    > user ID. (All the files belonged to root, but fortunately
    > the directory still belonged to the original user so I was
    > able to delete them with rm -f.)

    Whoops! Then I guess you can't charge for
    fixing it! :)

    >
    > --
    > /~\ cgibbs@kltpzyxm.invalid (Charlie Gibbs)
    > \ / I'm really at ac.dekanfrus if you read it the right way.
    > X Top-posted messages will probably be ignored. See RFC1855.
    > / \ HTML will DEFINITELY be ignored. Join the ASCII ribbon campaign!
    > 

    -- 
"It is impossible to make anything foolproof
because fools are so ingenious"
  - A. Bloch
  • Next message: Peter J. Acklam: "Re: /usr/local/"