On 9/26/07, <b class="gmail_sendername">alan</b> <<a href="mailto:alan@crabbnet.com">alan@crabbnet.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I got several errors when I tried running the command, andno luck so far<br>trying to search dpms on google.<br><br>On Fri, 21 Sep 2007 12:42:11 -0500, "Craig Huff" <<a href="mailto:huffcslists@gmail.com">huffcslists@gmail.com
</a>><br>wrote:<br>> Alan and Jim,<br>><br>> I don't recall where I found it, or I'd give you more specifics, but<br>there<br>> was another place that was turning dpms on despite the settings<br>> recommended
<br>> in Jarod's HOWTO. Try running this on your system:<br>> # find / -type f -exec grep -l dpms {} \;<br>> and then check the files that are not binaries to see what matched the<br>> "dpms" pattern.
<br>><br>> You could try googling "dpms", too.<br>><br>> Craig.<br></blockquote></div><br>Alan,<br><br>You probably ran the find command as a plain user and got a lot of messages <br>saying something about "Permission denied" or something similar. You can
<br>weed out such cruft like so: (all on one line in case the next line gets wrapped)<br><br> # find / -type f -exec grep -l dpms {} \; 2>&1 | egrep -v "Permission denied"<br><br>If you get more than one kind of complaint, just expand the last part with pipe-
<br>characters and the strings to be ignored, like so:<br><br> # find / -type f -exec grep -l dpms {} \; 2>&1 | egrep -v "Permission denied|Second type|Third type"<br><br>That will get you down to just the list of files that are worth looking into. Then
<br>you'll need to filter out binaries and such with a command on each of<br>the file names similar to:<br><br> # file /path/to/candidate/file<br><br>and stick with ones that don't have descriptions mentioning "binary" (kinda hard
<br>for us mere mortals to read ;-).<br><br>HTH,<br>Craig.<br>