I use something similar to this:
find /afs/foo/bar/ -type f -exec md5sum {} \;
I use md5sum just to force the entire file to be read by the client. I'm not
claiming that this is the best option, but it has always worked for me.
-Scott
- Original Message -
From: Gilles Martin
I've got a file server that is behind a nat and is also multihomed that is no
longer working from outside the nat. It was working fine outside for a long
while, though we're not sure when it stopped (It gets very light use
externally).
The server's NetInfo looks like this:
192.168.1.108
I'm not going to claim to be a guru, but when I upgraded my system all I did
was install the 1.4.11 Snow Leopard build over my old Leopard build. I haven't
had any issues with it.
-Scott
- Original Message -
From: avison48 aviso...@yahoo.co.uk
To: openafs-info@openafs.org
Sent:
I've been running the client (1.4.10) on OpenSolaris 2008.11 without any
issue. Today I updated the machine to 2009.06 and installed 1.4.11. The
kernel module loads fine but when afsd starts the system crashes with the
following error: osi_NetIfPoller: ldi_open_by_name failed: 22
I traced it as
On Sun, Aug 2, 2009 at 3:31 PM, Andrew Deason adea...@sinenomine.netwrote:
You're sure you're running the 1.4.11 kernel module? This exact issue
was present in 1.4.10 but should have been fixed in 1.4.11.
Oops, that was it. My boot archive didn't get updated because of the panic
so the
I suggested the exact same thing (and forgot to CC the list).
I know that reusing the chown interface would make fs a little more comfortable
for some of my users.
-scott
- Todd M Lewis uto...@email.unc.edu wrote:
Would it make sense to say f'rinstance +w rather than w+ to keep
it
On 10/27/06, Juha Jäykkä [EMAIL PROTECTED] wrote:
Hi!
After upgrading to 1.4.2, I have started to get these (probably any bos
command will do - I tried the most common ones):
bos: could not find entry (can't find cell 'default' in cell database)
Also, /etc/init.d/openafs-fileserver stop