I've got a related question. I'm afraid the discussion up to this point is a bit over my head, so I'm not sure if this got answered, but...
I have my machine set to dial out automatically when any app needs to connect. Occasionally it seems to want to connect for no good reason. Is there any way to determine which app or process is making a connection attempt? I can't find anything in the logs that tips me off. Mike At 8:33 AM -0400 5/21/04, Michael Spencer wrote: >Thanks all, and to those who emailed me off list; I just finished a big >project and now back to this annoying little problem. > >I found the little bast$%rd. It's being written by MP3 Sushi Server and >it is leaving no tracks of itself in the system logs and it is not in >the activity monitor [how can this be? must be operator error]. > >Thanks to everyone and let's see if I really have killed that thing. > >Michael > > >On May 19, 2004, at 3:01 AM, Armando Stettner wrote: > >> If you are familiar with UNIX commands, you could go into the terminal >> application and run OD (piping to MORE) the file and see what's there. >> You then might use the activity monitor (or something else) to see >> what process is writing this file. Is this file referenced in any of >> the system logs? >> >> armando >> >> >> Begin forwarded message: >> >>> From: "Michael Spencer" <[EMAIL PROTECTED]> >>> Date: May 18, 2004 2:17:16 PM PDT >>> To: <[EMAIL PROTECTED]> >>> Subject: [Littlesnitch-talk] [OT] ices.log >>> Reply-To: <[EMAIL PROTECTED]> >>> >> I'm at my wit's end, and before I go to Mac Managers, I thought I'd >> see if anyone on this list has any ideas. I need to throw this problem >> out to some informed folks, and for now, if you're reading this >> pathetic plea, you're more informed than I am :-] >> >> >> >> The short version: an invisible file called >> 'DS9/private/temp/ices.log' is incrementally written, increasing in >> size until it approaches 87G and fills the startup disk. 'DS9' is the >> name of the drive. >> >> >> >> The long version: I have no clue what is writing this file. The >> obvious answer is Icecast, but I have never loaded that app on any >> computer. I DO stream audio with iTunes. >> >> >> >> I googled 'ices.log', learning nothing, and I hit the Icecast support >> forum, also with no luck. I also posted to Apple's support fora in >> several places with no luck; but I did learn about a very nice app >> called 'Whatsize' that helped me at least identify the reason that my >> startup drive was filling up [until then I had no idea why]. >> >> >> >> I've been trying to identify by trial and error who is writing the >> file, but no luck yet. I was able to see the front [and rear] of the >> file in Terminal but learned nothing new. >> >> >> >> Anyone else have any ideas/clues/directions? >> >> >> >> Michael Spencer >> >> _______________________________________________ >> Littlesnitch-talk mailing list >> [EMAIL PROTECTED] >> http://at.obdev.at/mailman/listinfo/littlesnitch-talk >> > >_______________________________________________ >Littlesnitch-talk mailing list >[EMAIL PROTECTED] >http://at.obdev.at/mailman/listinfo/littlesnitch-talk -- "The radish, much as we may or may not love it, and in my case I may love it, is not going to last. If you make a friend of a radish there's an inevitable consequence you will eat it. Consequently if you act the radish to someone you will always wind up being digested." Robyn Hitchcock, 1985 _______________________________________________ Littlesnitch-talk mailing list [EMAIL PROTECTED] http://at.obdev.at/mailman/listinfo/littlesnitch-talk
