It may be that /bin/tar got corrupted some how. You may try to replace it or rename it to see what process complains about not finding it. Do your system logs tell you anything?
Whats your setup .... are you running NFS (there is a default nobody account for NFS if I remember correctly ... thats why we never setup Apache with nobody as the User ... Do we? ...)
do a netstat -a to see what/who is connected to your ftp port ... look for:
tcp 0 0 yourhost:ftp-data remoteIPortNo ESTABLISHED
I would check that it is really tar that is running. You may have a rogue program on your hands.
It is quite easy for a program to change it's name as far as what you see in ps. That makes it easy for a malicious program to avoid detection because it looks like a regular system command. See what files the program has open (lsof is invaluable here). This may give you a clue as to who ran it (i.e. what is the cwd). You can also write a wrapper script for tar that records the command line parms, start time, cwd, terminal, etc that then calls the real tar binary.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.