Date: Tue, 16 Dec 2008 14:46:59 +0100 From: ElBarto <elbarto@arcadebsd.org> To: Derrick Brashear <shadow@gmail.com> Cc: freebsd-afs@freebsd.org Subject: Re: openafs server executables Message-ID: <4947B153.5060101@arcadebsd.org> In-Reply-To: <db6e3f110812160537ia5d1d4fm3d8587cd0dd731ce@mail.gmail.com> References: <37396849@bs1.sp34.ru> <D0A121F456CC44D3AA1FD11CF28E21DE@valentine> <01705453@bs1.sp34.ru> <49453004.9010107@linuxbox.com> <83768316_-_@bs1.sp34.ru> <db6e3f110812160537ia5d1d4fm3d8587cd0dd731ce@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Derrick Brashear wrote: > On Tue, Dec 16, 2008 at 3:49 AM, Boris Samorodov <bsam@ipt.ru> 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: >> ----- >> libexec/openafs/ >> buserver >> fileserver >> kaserver >> ptserver >> salvager >> upclient >> upserver >> vlserver >> volserver >> sbin/ >> bosserver >> ka-forwarder >> kadb_check >> kdb >> kpwvalid >> prdb_check >> pt_util >> rmtsysd >> vldb_check >> vldb_convert >> voldump >> volinfo >> vsys >> ----- >> >> And let's assume other executables belong to the client part. >> >> > > Two copies of fs, vos, pts, bos, kas, asetkey, tokens, udebug, klog get > installed normally. you want copies of at least fs, vos, bos, asetkey, > udebug, pts (maybe not klog, tokens) in server, even if they are installed > elsewhere in client. > So if I install openafs-client and openafs-server I'll have fs at two different place ? Seems ugly to me. As I said vos and bos are useless to an user so they should be in the server port. pts must be in the client port, even it's used for creating users, it can also be used to create sub-group (login:group). fs is needed to setting up a new cell but not after (server side), so it should be in the client ports. -- Emmanuel Vadot elbarto@arcadebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4947B153.5060101>