If the fileserver is running, put a volume on it. "vos create -help"
Mount the volume. (fs mkmount -help)
cd to the mount point.
client reads mount point, asks vlserver where new volume is located.
vlserver looks up volname, returns location, which is a vice partition on
the new fileserver.
Take a look at ports in use -- we've seen this on a Solaris box running some
sort of RAID management utility and IBM/Transarc AFS -- it was using
2040/tcp -- turns out the volserver talks to the fileserver on this port ...
FSYNC_clientInit comes from fileserver/volserver talking to each other abou
ready on the ACL there's no need to issue
"fs sa system:anyuser none"
I was thinking that "system:anyuser" might already be in place on some of
your ACLs.
I'm not sure what you intend when you mention "upper mounts" ??
Kim
> Dexter Kimball
Try
udebug 7004
How many servers are mentioned in the output?
You should have only one server listed in your /usr/afs/etc/CellServDB file,
and the only cell in that file should be yours.
IIRC "udebug" should say, if configured this way, something like "I'm sync
site forever, single DB server"
er" groups. If not,
why maintain a "all users in my cell" group? Perhaps I missed something
earlier in the thread.
Kim
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Dexter Kimball
> Sent: Tuesday, March 08, 2005 6:5
system:authuser
MyIPgroup
These two entries say "only users who have valid tokens in my cell" and "any
requests, authenticated or no, from this group of IPs or wildcarded subnets"
OTHER POINTS OF INTEREST
Since a user can "fs mkmount" a volume anywhere she/he
WRT fileserver -- what are you using to synch clocks? xntp, the NTP wrapper
from IBM/Transarc AFS? Something else?
WRT client -- you can disable time synch by using "-nosettime" on the afsd
command line in your startup sequence.
Usage: /usr/vice/etc/afsd [-blocks <1024 byte blocks in cache>]
If your cronjob can run as root on any AFS server (strictly speaking, on any
AFS node with /usr/afs/etc/KeyFile, but it's generally not a good idea to
put the KeyFile on a client), you can use the "-localauth" argument to "vos
release"
vos release -localauth
When run as root with an accessible K
vos examine oddity
>
>
>
>
> On Friday, January 28, 2005 08:16:13 PM -0700 Dexter Kimball
> <[EMAIL PROTECTED]>
> wrote:
>
> > Jeffrey Hutzelman wrote:
> >> It is about the volume being examined, but what it tells
> you are that
> >> volume's
PROTECTED]; openafs-info@openafs.org
> Subject: RE: [OpenAFS] vos examine oddity
>
>
> On Friday, January 28, 2005 05:34:27 PM -0700 Dexter Kimball
> <[EMAIL PROTECTED]>
> wrote:
>
> > Jeffrey Hutzelman has clarified things nicely in his other em
Right, the last part is the VLDB entry (vos listvldb, identical).
The third line (after the line with the prompt, below) is the one that I
thought was odd:
[EMAIL PROTECTED] kim]$ vos exa root.afs.readonly
root.afs.readonly 536901459 RO 10 K On-line
magic.lab.
Jim, could you respond to this inquiry I got from one of our FreeBSD fans?
Thanks.
Kim
On 3/9/2004 7:48:39 PM, Dave ([EMAIL PROTECTED]) wrote:
> Thanks for that info. Is he planning to commit to both 4.X (stable)
> and 5.X (current) branches? If he is,
> I'll pick up his patches and
-Ori
12 matches
Mail list logo
