Bugs in Pfind 4.4

Sometimes Pfind misreports. I mostly use Pfind to search contents of files.

Once it reported no files found, but I knew the string was in a file.

Right now, I am searching the Xsane source, looking for the string 'WARN_XSANE_AS_ROOT', and it found 93 files matched, including even .ico, .png and .xpm images.

When it displays the results, if I want to do another search, Pfind has forgotten the directory that I had previously chosen and starts searching from '/'. I am forced to exit from Pfind and start again.

Anyway, I should not have to choose a directory in the first place. This was something that I requested ages ago -- if pfind is started in a terminal, the default search directory should be set to that directory, not to '/'. No one would ever want to search from '/' anyway.

So, I used Zfind, works real nice and easy. I started zfind from a terminal open in the xsane source directory, entered "*" in the 'name' box, "WARN_XSANE_AS_ROOT" in the 'contains' box, and it found two files.

Zfind though, is very limited, hardly any search options.

Posted on 29 Apr 2009, 16:09


Posted on 29 Apr 2009, 16:45 by coolpup


Posted on 29 Apr 2009, 18:49 by ttuuxxx
Pfind alternative
Hi Barry Lately I've been Using Search Monkey, its a great replacement for Pfind, and has some really advanced features and is easily configured and takes 1/2 the CPU resources of Pfind and it not based on gtkdialog so it always shutsdown fully.
You can test the puppy 4.0 version located at
and the sources you can get at
and the homepage which explains why it so good is good reading :)


Posted on 29 Apr 2009, 21:10 by zigbert
I made a test right now (Pfind 4.8), and it seems to work for me. But I don't have the sane source, so it's hard to match our results. I wonder if you can point me to an example in the default Puppy filesystem. - I really need more flesh on the bone to solve this one.

- Default searchdir is /, but can be changed in the preferences.
- Yes, you have asked earlier about the 'search-in-my-directory' option. I then included the -d switch to both pfind and pfilesearch. 'pfind -d ./' uses your directory. There was no response of it, so I thought everything was ok... How can I determine if user starts pfind from terminal or not ?
- You may also want to use the -a switch that points you to the advanced mode at once (pfind -a -d ./) ...... hmmm, while testing this I see a bug in Pfind 4.8 related to this.
- Remember last used search-dir is added to my todo-list.


Posted on 29 Apr 2009, 21:52 by BarryK
Re: Pfind
mostly Pfind works ok. However something goes wrong with the finding sometimes, after I have used it for awhile -- could there be files left behind from previous seaches that cause confusion for the current search?

At the beginning of the /usr/local/pfind/pfind script, have this:


...unless overridden by a commandline parameter.

I just checked something. I put this:
pwd > /tmp/z
into the beginning of
...content of /tmp/z is "/root"
...which is a good default place to search.

Posted on 29 Apr 2009, 21:55 by BarryK
Pfind default dir
To clarify my previous post, in the last paragraph I was checking what 'pwd' returns when Pfind is started from the menu.

Posted on 30 Apr 2009, 4:27 by zigbert
Pfind and pwd
In version 1 of Pfind the default search dir was set to /root/. But because of good argumentation from some users, it was changed to /. I agreed because /root/ doesn't make any sense the way I use Puppy. I don't store my data in pup_save, but on a mounted partition elsewhere. Searching in only /root/ wouldn't find my personal files.......

Are you aware of the possibility to set Pfind to always use current dir as searchdir? In the preferences you can specify ./ to be your default choice.

I will upload a new bugfixed version of Pfind/Pfilesearch. Hopefully in this weekend. I'll try to make some searching to see if I can detect some bugs related to yours