POPFile's Directory Structure and Configuration Files

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)


 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)




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


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.


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 altered by manually editing the popfile.cfg file (do this only when POPFile is not running).
installationhowtos/dirstruct.txt · Last modified: 2008/02/08 19:49 (external edit)

Should you find anything in the documentation that is incomplete, unclear, outdated or just plain wrong, please let us know and leave a note in the Documentation Forum.

Recent changes RSS feed Donate Driven by DokuWiki
The content of this wiki is protected by the GNU Fee Documentation License