p4_vars should have a flag to ignore "Open for write" permission denied errors to facilitate read-only scripting.
For read only workflows (create a monitoring service user in the OS) we don't "care" that we can't write to some directories. The extra output in "error" format is not helpful for catching other relevant error data in a script.
source /p4/common/bin/p4_vars 1
Perforce server error:
open for write: /p4/1/logs/triggers.csv: Permission denied
Perforce server error:
open for write: /p4/1/logs/errors.csv: Permission denied
Perforce server error:
open for write: /p4/1/logs/events.csv: Permission denied
Perforce server error:
open for write: /p4/1/logs/integrity.csv: Permission denied
Perforce server error:
open for write: /hxlogs/p4/1/frankfurt/logs: Permission denied
Perforce server error:
open for write: /p4/1/logs/journal: Permission denied
Error error:
open for write: /p4/1/logs/events.csv: Permission denied
Perforce server error:
open for write: /p4/1/logs/triggers.csv: Permission denied
Perforce server error:
open for write: /p4/1/logs/errors.csv: Permission denied
Perforce server error:
open for write: /p4/1/logs/events.csv: Permission denied
Perforce server error:
open for write: /p4/1/logs/integrity.csv: Permission denied
Perforce server error:
open for write: /hxlogs/p4/1/frankfurt/logs: Permission denied
Perforce server error:
open for write: /p4/1/logs/journal: Permission denied
Error error:
open for write: /p4/1/logs/events.csv: Permission denied