PMDADS389LOG(1)
π pmdads389log β bestie's guide to the 389 Directory Server Log PMDA π
okay so real talk, you found the man page for pmdads389log, which lives in section 1 of the General Commands Manual, and honestly? it's giving "quietly essential infrastructure" and i'm obsessed. let's get into it π«Ά
β¨ NAME β¨
pmdads389log β the 389 Directory Server Log PMDA, no cap π
πΈ DESCRIPTION πΈ
so pmdads389log is a Performance Metrics Domain Agent (a PMDA, iykyk) and what it does is literally extract statistics from the 389 Directory Server access log, and it does that using the logconv.pl(1) utility. that's the whole vibe. it reads the log, it pulls the numbers, it hands them over. queen behavior π
π INSTALLATION π
first things first: pmdads389log reads a configuration file, and that file is:
$PCP_PMDAS_DIR/ds389log/ds389log.conf
this file can contain overridden values (and heads up, they're Perl code, not vibes) for the settings listed at the start of pmdads389log.pl, namely:
logconv.plparameters- minimal query interval
- 389 DS access log to use
- 389 DS log directory to use (this one kicks in if no file is specified)
- non-root user having read access to the access log file
once all of that is set up, you can access the names and values for the 389 DS performance metrics by doing the following as root:
# cd $PCP_PMDAS_DIR/ds389log
# ./Install
and when you wanna uninstall, same energy, also as root:
# cd $PCP_PMDAS_DIR/ds389log
# ./Remove
β οΈ ok important one bestie:pmdads389logis launched bypmcd(1)and should never be executed directly. like, do not. theInstallandRemovescripts are the ones that notifypmcd(1)when the agent is installed or removed, so let them do their job. periodt π
π¦ FILES π¦
$PCP_PMDAS_DIR/ds389log/ds389log.confβ configuration file for thepmdads389logagent$PCP_PMDAS_DIR/ds389log/Installβ installation script for thepmdads389logagent$PCP_PMDAS_DIR/ds389log/Removeβ undo installation script for thepmdads389logagent$PCP_LOG_DIR/pmcd/ds389log.logβ default log file for error messages frompmdads389log/var/log/dirsrv/slapd-.../accessβ the 389 Directory Server access log parsed bylogconv.pl
π PCP ENVIRONMENT π
so the environment variables with the prefix PCP_ are what parameterize the file and directory names used by PCP. on each installation, the file /etc/pcp.conf contains the local values for these variables. and if you wanna get fancy, the $PCP_CONF variable may be used to specify an alternative configuration file, as described in pcp.conf(5). very demure, very mindful β¨
π SEE ALSO π
PCPIntro(1), logconv.pl(1), pmcd(1) and pmdads389(1). go read them, they're all part of the same little family π«Ά
and that's the whole page, bestie!! this one comes to you from Performance Co-Pilot, version PCP β that's the source and the version right there, no date on this one, it's mysterious like that π§ stay slaying, and remember: never run the agent directly. mwah πβ¨
π¦ where this page comes from
- arch rolling: pcp 7.2.2-2 Β· GPL-2.0-or-later AND LGPL-2.1-or-later AND CC-BY-3.0
- centos-stream 10: pcp-doc 7.1.5-6.el10 Β· GPL-2.0-or-later AND CC-BY-3.0
- centos-stream 9: pcp-doc 6.3.7-14.el9 Β· GPL-2.0-or-later AND CC-BY-3.0
- debian trixie: pcp 6.3.8-1
- fedora 43: pcp-doc 7.0.1-1.fc43 Β· GPL-2.0-or-later AND CC-BY-3.0
- fedora 43: pcp-doc 7.2.1-1.fc43
- fedora 43: pcp-doc 7.2.2-1.fc43
- fedora 43: pcp-doc 7.2.2-2.fc43 Β· GPL-2.0-or-later AND CC-BY-3.0
- fedora 44: pcp-doc 7.1.0-6.fc44 Β· GPL-2.0-or-later AND CC-BY-3.0
- fedora 44: pcp-doc 7.2.1-1.fc44
- fedora 44: pcp-doc 7.2.2-1.fc44
- fedora 44: pcp-doc 7.2.2-2.fc44 Β· GPL-2.0-or-later AND CC-BY-3.0
- ubuntu questing: pcp 6.3.8-1
- ubuntu resolute: pcp 7.1.1-1
- ubuntu stonking: pcp 7.2.1-2build1
- Copyright (c) 2014-2018 Red Hat
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms