Can't Locate binfmt... something to worry about?

[Jonathan Gift <jgift@wanadoo.fr>]

Hi,

I've been getting the msg every two or three days now and know that it's
origin is a program accessing an empty file. The questions are:

1. Does this happen on most systems?
2. Is it something particular to this system, and if so, how track down
what is causing it?

I've had xlogmaster on daemon log open almost continuously but have
missed catching it in the act...

Any ideas or suggestions appreciated.

Thanks, 

Jonathan


-- 

/* Jonathan Gift 
jgift@wanadoo.fr */