Empty Files appearing all over file system
I first noticed this a day or so after install of suse 9.2 amd64, and now 2 months down the track I have noticed the same thing happening all over my filesystem. It only occurs on my 64bit workstation, my 32bit laptop is fine. What it is is an empty file with the name simply '2' appearing this appears in home directorys, / /vol and a seemingly random assortment of places... Deleting the offending file removes it but it comes back after a while... I've tried looking through logs etc and stat on the files they always have one of the systems users creation uid and group. But are created at seeminly random times. Anyone know what service/program thing that may be causing this behaviour?
Hi Joel: On Tuesday 22 February 2005 16:56, Joel Wiramu Pauling wrote:
I first noticed this a day or so after install of suse 9.2 amd64, and [...] happening What it is is an empty file with the name simply '2' appearing this appears in home directorys, / /vol and a seemingly random assortment of places...
Question: Is this machine by serving SMB (aka CIFS or Windows) protocol and accessible to a Windows PC? I've seen something like this once on a Sun at work, and it turned out that a virus infected Windows box was dropping these things in many directories. Just a thot, - Darrell -- sused@mucus.com "Perfect! ....what am I doing?" -- Washu
On Tuesday 22 February 2005 5:33 pm, Darrell Shively wrote:
Hi Joel:
On Tuesday 22 February 2005 16:56, Joel Wiramu Pauling wrote:
I first noticed this a day or so after install of suse 9.2 amd64, and [...] happening What it is is an empty file with the name simply '2' appearing this appears in home directorys, / /vol and a seemingly random assortment of places...
Question: Is this machine by serving SMB (aka CIFS or Windows) protocol and accessible to a Windows PC? I've seen something like this once on a Sun at work, and it turned out that a virus infected Windows box was dropping these things in many directories.
I see these same files, no shared folders on this box but the files are still showing up. Reiserfs. Same files were showing up on 9.1 64 bit too. Scott -- POPFile, the OpenSource EMail Classifier http://popfile.sourceforge.net/ Linux 2.6.8-24.11-default x86_64
Nope this machine is not a Samba server. It does nfs sharing but only /vol is shared... and I noticed the first one before I setup nfs... On Tue, 2005-02-22 at 18:34 -0800, Scott Leighton wrote:
On Tuesday 22 February 2005 5:33 pm, Darrell Shively wrote:
Hi Joel:
On Tuesday 22 February 2005 16:56, Joel Wiramu Pauling wrote:
I first noticed this a day or so after install of suse 9.2 amd64, and [...] happening What it is is an empty file with the name simply '2' appearing this appears in home directorys, / /vol and a seemingly random assortment of places...
Question: Is this machine by serving SMB (aka CIFS or Windows) protocol and accessible to a Windows PC? I've seen something like this once on a Sun at work, and it turned out that a virus infected Windows box was dropping these things in many directories.
I see these same files, no shared folders on this box but the files are still showing up. Reiserfs. Same files were showing up on 9.1 64 bit too.
Scott
-- POPFile, the OpenSource EMail Classifier http://popfile.sourceforge.net/ Linux 2.6.8-24.11-default x86_64
I haven't heard of such problems before and we use here at SUSE lots of systems with AMD64. If you can figure out the problem, please tell me and if it's in one of the packages, I'll help getting it fixed, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Wednesday 23 February 2005 12:16 am, Andreas Jaeger wrote:
I haven't heard of such problems before and we use here at SUSE lots of systems with AMD64. If you can figure out the problem, please tell me and if it's in one of the packages, I'll help getting it fixed,
Well, I found out what was causing mine. Operator error <g>. I had some crontab entries that used the redirection operators incorrectly, e.g., 3 3 * * * /usr/local/bin/fetchyahoo > /tmp/fetchyahoo.helphand 2>1& When it should have been 3 3 * * * /usr/local/bin/fetchyahoo > /tmp/fetchyahoo.helphand 2>&1 The former was leaving empty files named '1' in various directories due to those bad crontab entries. Scott -- POPFile, the OpenSource EMail Classifier http://popfile.sourceforge.net/ Linux 2.6.8-24.11-default x86_64
participants (4)
-
Andreas Jaeger
-
Darrell Shively
-
Joel Wiramu Pauling
-
Scott Leighton