I will briefly crawl out from under my rock to point out the existence of my AFS::Command CPAN modules, which provide a pretty decent OO API to those commands, and they handle all of the ugly CLI parsing for you.
http://search.cpan.org/~wpmoore/AFS-Command-1.99/lib/AFS/Command.pod We have built a very large quantity of enterprise-class systems management software using this API. There's a good chance it will work for you, if your primary goal is automating the use of bos, vos, fs, etc. What my modules do NOT have are things like setpag(). If I ever get back into working on OpenAFS again (probability totally indeterminate), the first time I need setpag(), I will code up a standalone perl module that provides that, independent of the very broken AFS.pm distribution. When that code was written, and first presented at the AFS/Kerberos workshop, I railed long and loud (much to the annoyance of the author) that this cut/paste approach to implementing those modules was a strategic disaster. The fact that we haven't had a working version since the release of 1.6 proves I was right (sorry for gloating.... can't help it... :-P) Anyway, please consider using AFS::Command as alternative. On Fri, Sep 5, 2014 at 8:50 PM, Russ Allbery <[email protected]> wrote: > Benjamin Kaduk <[email protected]> writes: > > > I have a vague recollection that the AFS perl modules only worked with > > openafs 1.4, but have nothing to support that at hand. Maybe someone > > else has a better memory than me... > > That's correct. That's also why they're not in Debian and Ubuntu. They > were broken by a combination of Perl switching to natively multithreading > and some really ugly hacks that linked LWP code with pthread code no > longer working around the 1.6 time frame. > > Even if you manage to get the modules to build, they'll just randomly > segfault. At Stanford, we rewrote all the software that used them to > parse command-line output instead. > > They should work again once OpenAFS is 100% pthreads, but as long as they > require linking LWP code and pthread code together, they're probably not > going to work. > > -- > Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/> > _______________________________________________ > OpenAFS-info mailing list > [email protected] > https://lists.openafs.org/mailman/listinfo/openafs-info >
