Core components of Web Safety are installed into /opt/websafety. Admin UI for Web Safety and Squid proxy is installed into /opt/websafety-ui. Both installation folders have the same structure.
- /opt/websafety(-ui)/etc contains application configuration.
- /opt/websafety(-ui)/bin contains binary files of the application (filtering daemon wsicapd, traffic monitor and various support scripts).
- /opt/websafety(-ui)/var contains support files of the application (definition files, application logs and Admin UI).
In addition to application files installer may also set up the following scripts in the system directories:
- startup scripts for daemon are saved in /etc/systemd.
- /etc/logrotate.d/websafety - used to perform automatic daily log rotation of log files stored at /opt/websafety/var/log and /opt/websafety-ui/var/log.
- /etc/cron.hourly/websafety_* - scripts used to automatically update definition files in /opt/websafety/var/spool, as well as to automatically check for a new version of Web Safety published on our web site.
Core components of Web Safety run under the same proxy user account as Squid. For Admin UI, the installer also adds a user and group named websafety to the user database in /etc/passwd and /etc/group. This user account is later used to run the Admin UI. This user account is removed automatically when Web Safety is removed. The websafety user has some sudo privileges, described in file /etc/sudoers.d/websafety (mainly to restart ICAP and Squid services and manage Squid configuration files).
Web Safety stores its configuration in /opt/websafety/etc, /opt/websafety-ui/etc and /opt/websafety-ui/var/db/config.sqlite files and folders. The easiest way to backup the configuration is to download the backup archive as indicated in the article Back up your current configuration from old version.