 |
 |
3 GB bash file! WTF?
|
|
|
|
|
Mac Elite
Join Date: Feb 2001
Location: Canaduh
Status:
Offline
|
|
I've been having some weird issues with my Terminal. I was looking for a certain invisible file when I noticed that a file called "bash" in the "bin" folder is 3 GB in size.
This ain't right, is it? What should I do to fix it?
|
|
|
| |
|
|
|
|
|
|
|
Mac Elite
Join Date: May 2002
Status:
Offline
|
|
Definitely not right - my copy of bash (which is sh on OS X) is only 500 KB. I'd suggest reinstalling it from the OS X CDs.
|
|
[vash:~] banana% killall killall
Terminated
|
| |
|
|
|
|
|
|
|
Mac Elite
Join Date: Oct 2001
Location: Enschede
Status:
Offline
|
|
532 KB
Before doing the thing suggested above try running an app like MacJanitor (all schedules)
|
|
iMac G5 2.0 Ghz 20", 2 GB RAM, 400 GB, OS X 10.4.5, iPod with color screen 60 GB
|
| |
|
|
|
|
|
|
|
Mac Elite
Join Date: May 2000
Status:
Offline
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
Forum Regular
Join Date: Sep 2000
Location: UK
Status:
Offline
|
|
What I think you've done (as I did it myself once) is type "sudo foo > /bin/bash" when you meant "sudo foo | /bin/bash" or somethign like that.
In your case, foo output 3GB of data to the file instead of piping it to the bash executable.
|
|
|
| |
|
|
|
|
|
|
|
Forum Regular
Join Date: May 2001
Status:
Offline
|
|
You "could" have been hacked and now have the worlds largest root kit ever 
just kidding.
|
|
If your computer stops responding for a long time, turn it off and then back on. - Microsoft
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
 
|
|
|
Forum Rules
|
|
|
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
|
|
|
|
|
|
Top