POPFile requires its directory structure and configuration files exist under the POPFile installation directory.

Assuming you install POPFile to /usr/local/brad/popfile/ then your installation will look like this:

<code> POPFile installation directory (contains popfile.pl, utilities and configuration files)

/usr/local/brad/popfile

 POPFile module directories (these contain the Perl modules that comprise POPFile)

/usr/local/brad/popfile/Classifier /usr/local/brad/popfile/Platform /usr/local/brad/popfile/POPFile /usr/local/brad/popfile/Proxy /usr/local/brad/popfile/UI

 POPFile manual, skins and languages directories

/usr/local/brad/popfile/skins /usr/local/brad/popfile/manual /usr/local/brad/popfile/languages

 POPFile messages directory (contains message history and cache)

/usr/local/brad/popfile/messages

</code>

popfile.db

If you are using the default SQLite backend, then your database will be in the file named popfile.db.

popfile.pid

When POPFile runs, it creates a file, popfile.pid, in the POPFile installation directory. The file contains the process id of the running POPFile and is used as a semaphore to prevent multiple instances of POPFile from running.

popfile.cfg

Once POPFile has been run at least once, a popfile.cfg file will be created. This file contains all of the configuration parameters that control POPFile's operation. These parameters are controlled in several ways;

• They can be altered on a running POPFile from the UI's Advanced Page

• They can be overridden or set at startup by using a commandline parameter when running popfile.pl

• They can be altered by manually editing the popfile.cfg file (do this only when POPFile is not running).