---
title: "Logging the Pharos Mac Popup Client"
slug: "logging-the-pharos-mac-popup-client"
updated: 2024-03-19T13:01:46Z
published: 2024-03-19T13:01:46Z
canonical: "kb.pharos.com/logging-the-pharos-mac-popup-client"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.pharos.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Logging the Pharos Mac Popup Client

### Backend logging

To enable more verbose Print and Popup backend logging, edit the **/etc/cups/cupsd.conf** file, replacing the text: `LogLevel info` With this text:

`LogLevel debug` Leave everything else as is.

### For the UI logging:

To enable logging for the Popup user interface, edit the **/etc/syslog.conf** file, replacing the text:

`lpr.info`

with the text

`lpr.debug`

Leave everything else as is. For Mac OS X 10.8 (Mountain Lion): as indicated within syslog.conf, changes should instead be made to **/etc/asl.conf**. To enable the necessary logging, add the following line:

`? [= Facility lpr] file /var/log/lpr.log` **NOTE:** You must restart the client machine to make sure the changes take effect.

If you encounter Popup problems, send the following files to [Pharos Support](mailto:support@pharos.com):

1. /var/log/cups/error_log
2. /var/log/lpr.log

The first file is the print system log. The second is the Popup application log. When no longer needed, stop logging by changing the edited files back to the original state, as logging can generate very large files.

## Related

- [Mac auto installation files fail to install printers](/mac-auto-installation-files-fail-to-install-printers.md)
- [Tracker silent installs not working in combination with the /dir option](/tracker-silent-installs-not-working-in-combination-with-the-dir-option.md)
- [Blueprint Tracker installer command line options](/blueprint-tracker-installer-command-line-options.md)
- [Diagnostics and Logging Packages](/diagnostics-and-logging-packages.md)