Bork Bork Bork
The BORKED parameter.
I realize most of our international users of Dirtracer may not get the reference but the BORKED parameter got its name in part from the US TV show called The Muppet Show; something I watched as a child. A show made up entirely of Puppets (Muppets) who's main character is called Kermit the Frog.
The BORKED parameter is a reference to the Swedish Chef special Bork-speak...a parody of a wacky Chef who speaks in unintelligible Swedish. In certain tech circles "Borked" is synonymous with "Broken", and when developing this settings purpose the name just stuck.
http://en.wikipedia.org/wiki/The_Muppet_Show
http://en.wikipedia.org/wiki/Bork_bork_bork
Think of Borked as "Hung" when it comes to its use with Dirtracer. If a Directory Server process is thought to be Hung, then use set the BORKED parameter to 1.
BORKED="1"
Note: I plan to rename the parameter to HUNG (Config File only) in the next release.
What does BORKED="1" do?
Normally Dirtracer will run a set of the following searches and or modiify's, if Borked is set to 1 (on) then these searches etc. are skipped. Setting Borked to 1 helps make sure Dirtracer itself doesn't hang waiting on these ldapsearches to return. If Borked is not set to 1 when the Directory Server is suspected of being Hung then Dirtracer will not complete its data gathering.
Searches:
Backend Suffix names; naming contexts
Backend Database names
cn=monitor
cache info searches
nsds50ruv; replica ruv's
cn=config info
rootdse
Modifies; only completed if Dirtracer is configured to do so.
PTS_CONFIG_LOGGING can set the server Logging level to the parameter value configured. This sets the nsslapd-infolog-area or nsslapd-errorlog-level
Examples:
nsslapd-infolog-area: 4 sets Heavy Trace Logging
nsslapd-infolog-area: 128 sets ACI debugging
nsslapd-infolog-area: 8192 sets Replication Debug Logging
See the following link for more info on Logging Levels
http://docs.sun.com/source/816-6699-10/confattr.html#15873
Dirtracer can also set (rarely used) Logging On or Off.
TURN_LOGGING_ON="0" # Turn On access/error logs
TURN_LOGGING_OFF="0" # Turn Off access/error logs
AUDIT_LOGGING_ON="0" # Turn On audit logs
AUDIT_LOGGING_OFF="0" # Turn Off audit logs
As mentioned Dirtracer only completes the above ldapmodify's if configured to do so.
[LT]
