Date: Tue, 16 Dec 2008 16:32:26 +0300 From: Boris Samorodov <bsam@ipt.ru> To: ElBarto <elbarto@arcadebsd.org> Cc: freebsd-afs@freebsd.org Subject: Re: openafs server executables Message-ID: <69526901@bb.ipt.ru> In-Reply-To: <4947A9D0.6050900@arcadebsd.org> (elbarto@arcadebsd.org's message of "Tue\, 16 Dec 2008 14\:14\:56 %2B0100") References: <37396849@bs1.sp34.ru> <D0A121F456CC44D3AA1FD11CF28E21DE@valentine> <01705453@bs1.sp34.ru> <49453004.9010107@linuxbox.com> <83768316_-_@bs1.sp34.ru> <4947A9D0.6050900@arcadebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
ElBarto <elbarto@arcadebsd.org> writes: > Boris Samorodov wrote: >> Matt Benjamin <matt@linuxbox.com> writes: >> >> >>>> Hm, until now I've been sure that client is kernel modile + >>>> afsd daemon + configuration files. Where can I find out >>>> which file should belong to which port? >>>> >>> That is the client, minimally. Users need to get, list, and discard >>> tokens (aklog, klog, unlog, tokens*), talk to the client to configure >>> and debug it (fs), as well as do some AFS specific file operations (fs), >>> manage groups (pts), possibly also users (pts). They should have vos, >>> too (vos listvldb). You should also ship pagsh* (but I don't remember >>> if pags work right now in the FreeBSD client). >>> >>> I'd think you should ship all of sys, rxgen, scout, udebug, cmdebug, >>> rxdebug, fstrace, up, and bos for administrative and debugging purposes. >>> >>> Other distribution packages people have done (openafs.org) could be >>> helpful, also openafs top-level make has a "dest" target that puts a >>> Transarc style installation in a subtree "dest" of the openafs source >>> tree being built. >>> >>> For the server, perhaps everything openafs would have put in its libexec >>> or sbin, and not already mentioned (except maybe copyauth). And somehow >>> you are accounting for configuration files and a var tree with >>> appropiate permissions, as you noted. >> >> OK, seems that to determine the server part is an easier task. >> Let's say server executables are: [old list was here] >> And let's assume other executables belong to the client part. >> >> Any changes, additions, fixes? Thanks! >> > Well, the bos, vos and backup command are totally useless to an afs > user so I think it will > be better to included them in the openafs-server ports. > I don't see either the "scout" or "udebug" command in your list, this > is for monitoring servers so ... > The uss command is only for the administrator. Done. > I think if your add those command in the list it should be good. Thanks for your help! Here is a changed list: ----- bin/ bos scout udebug libexec/openafs/ buserver fileserver kaserver ptserver salvager upclient upserver vlserver volserver sbin/ backup bosserver ka-forwarder kadb_check kdb kpwvalid prdb_check pt_util rmtsysd uss vldb_check vldb_convert voldump volinfo vos vsys ----- Any more fixes? WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?69526901>