#192 ktcheck -D option ignored

[Greg Neagle]

in radmind 1.11.1 and radmind 1.13.0, the -D option passed to ktcheck is ignored.

Trying to run radmind from a read-only boot volume by pointing ktcheck, etc to a writeable volume. No go. ktcheck complains about /var/radmind/client, which does not exist on the boot volume, and would be read-only even if it existed.

[Jim Foraker]

I brought this up on radmind-devel back in May '07, but then worked around it and never did anything about it. It's less a bug than a not-well-documented design decision. The consensus at the time seemed to be that -D could be reworked to not just change the starting point for transcript paths (which is what it does now) but to also change the locations of the certs & client directory, with the idea that if -x,-y,-z, or -K is specified, it overrides the value implied by -D.

In the meantime, the workaround to get the client directory where you need it is to tack '-K /path/to/where/you/want/command.K' onto your command line. ktcheck will then root the command files and transcripts at the same directory.

-Jim

[Greg Neagle]

Thanks, Jim. I was able to get the behavior I want in ktcheck and fsdiff by passing a writable path via the -K option.

-Greg

[Andrew Mortensen]

Odd. Looks like this patch was never completed. The problem is that the command file path (/var/radmind/client/command.K) is getting compiled in, and the -D path is ignored.