grep -r <filename> would just sit and do nothing infinitely, as you didn't give it any files to look in. so it assumes it's waiting for text to be piped into it.
grep -r <filename> . would be sufficient, since he would already be "cd"ed into the desired location. grep -r <filename> /var/log would be equivalent. -wes On Wed, Feb 10, 2016 at 7:22 PM, Don Buchholz <buchh...@easystreet.net> wrote: > ... also, > # cd /var/log > # grep -r <filename> > If some daemon is responsible for restoring it, maybe it's logging the > event. > -Don > P.S. I know there is interest in figuring out "why?", but I still think > that nuking it in single-user mode would be a good test ... > > On February 10, 2016 7:12:00 PM PST, Bill Barry <b...@billbarry.org> > wrote: > >On Wed, Feb 10, 2016 at 7:01 PM, John Jason Jordan <joh...@comcast.net> > >wrote: > >> We shall see what happens. > > > >The output of lsof would be useful. Try something like > >lsof | grep -i filename > >to see if something has the file open. > > > >Bill > >_______________________________________________ > >PLUG mailing list > >PLUG@lists.pdxlinux.org > >http://lists.pdxlinux.org/mailman/listinfo/plug > > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > _______________________________________________ > PLUG mailing list > PLUG@lists.pdxlinux.org > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list PLUG@lists.pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
