> From: Richardson, Bruce > The details of what the config file is should largely be hidden from the user > IMHO.
Agreed, however hiding it totally removes the flexibility of waiting for a primary that is starting with --file-prefix (aka: in a non-default location). Imposing a limit on only monitoring primary procs in the default location seems wrong. > If you want to allow a secondary to query an arbitrary primary process can you > still allow a NULL string to query the default primary based on the passed in > file-prefix parameter (if any)? Yep, I've made a v2 which includes handling NULL as path arg and using the default config file, will post later after some more testing. -Harry
