Greetings, I should have said that the bug manifests itself if pqact(1) is explicitly given the pathname of its configuration-file as a RELATIVE pathname (e.g., "pqact etc/data-specific-actions.conf"). Configuration-file pathnames specified as absolute pathnames don't trigger the bug. Regards, Steve Emmerson
ldm-users
archives: