I seem to get a lot of these error in my log files, my question is why?
I have three afs db/file servers two of which are on the same physical
gigabit switch as my client the other is on a separate gigabit subnet.
None of the servers are multi-homed and are running 1.2.13 on debian
stable, ke
! On Tue, 5 Apr 2005, Andy Malato wrote:
!
! > in src/cf/osconf.m4 I changed :
! >
! > XLIBS="${LIB_AFSDB}"
! >
! > to:
! >
! > XLIBS="-lresolv ${LIB_AFSDB}"
!
! oh, LIB_AFSDB probably included -lresolv already.
!
! But, was -lresolv in the link line for the link where you got the error?
Including
! Date: Tue, 4 Apr 2005 14:56:51 -0400 (EDT)
! From: Derrick J Brashear <[EMAIL PROTECTED]>
! To: Andy Malato <[EMAIL PROTECTED]>
! Cc: openafs-info@openafs.org
! Subject: Re: [OpenAFS] Problems building openafs-1.3.80 on linux 2.6
! kernel
!
!
!
! On Tue, 5 Apr 2005, Andy Malato wrote:
!
! >
Rodney M Dyer <[EMAIL PROTECTED]> writes:
> That sort-of makes sense. Sorry, I wasn't suggesting that the bug was
> in AFS, or find. I just think it is kind of silly that it works that
> way. Why not "fix" the gnu find so that it requires the "-noleaf"
> option in all circumstances, or a stupid
At 03:09 PM 4/5/2005, you wrote:
gnu find is not the same as solaris find. the -noleaf option is the
equivalent of the default options with solaris (well, unix) find. so since
gnu find goes out of its way to work this way, when other finds do not, i
see no reason why the filesystem should go out
On Tuesday, April 05, 2005 15:03:30 -0400 Rodney M Dyer <[EMAIL PROTECTED]>
wrote:
At 01:49 PM 4/5/2005, Derrick J Brashear wrote:
use the -noleaf option to find. it's not an afs bug, so you found no bug.
Actually, why isn't this a bug? He doesn't need the -noleaf option if
there is at least on
Rodney M Dyer wrote:
At 01:49 PM 4/5/2005, Derrick J Brashear wrote:
use the -noleaf option to find. it's not an afs bug, so you found no bug.
Actually, why isn't this a bug? He doesn't need the -noleaf option if
there is at least one other "real" directory in the root of the
directory he is t
On Tue, 5 Apr 2005, Rodney M Dyer wrote:
At 01:49 PM 4/5/2005, Derrick J Brashear wrote:
use the -noleaf option to find. it's not an afs bug, so you found no bug.
Actually, why isn't this a bug? He doesn't need the -noleaf option if there
is at least one other "real" directory in the root of the
At 01:49 PM 4/5/2005, Derrick J Brashear wrote:
use the -noleaf option to find. it's not an afs bug, so you found no bug.
Actually, why isn't this a bug? He doesn't need the -noleaf option if
there is at least one other "real" directory in the root of the directory
he is testing.
Rodney
___
On Tue, 5 Apr 2005, Andy Malato wrote:
in src/cf/osconf.m4 I changed :
XLIBS="${LIB_AFSDB}"
to:
XLIBS="-lresolv ${LIB_AFSDB}"
oh, LIB_AFSDB probably included -lresolv already.
But, was -lresolv in the link line for the link where you got the error?
___
Op
! Date: Tue, 5 Apr 2005 12:59:45 -0400 (EDT)
! From: Derrick J Brashear <[EMAIL PROTECTED]>
! To: openafs-info@openafs.org
! Subject: Re: [OpenAFS] Problems building openafs-1.3.80 on linux 2.6
! kernel
!
!
!
! On Tue, 5 Apr 2005, Andy Malato wrote:
!
! > I am attempting to build openafs-1.3.8
Thanks for your responses.
I was following my modifed Server doc, since I have updated it to work with
Solaris 8 & 9, oh well, have to update the client doc as well.
Thanks
Craig Cook
--
Systems Monitoring Consulting and Support Services
http://www.cookitservices.com
___
On Tue, 5 Apr 2005, Jonathan E Halter wrote:
This is on: RHEL WS3, kernel 2.4.21-27.EL, openafs 1.2.13
I'm wondering if anyone else can recreate this problem I've come across
with using the find command in AFS. I don't know if its a problem with
the RHEL's find command, the OpenAFS client, or a com
This is on: RHEL WS3, kernel 2.4.21-27.EL, openafs 1.2.13
I'm wondering if anyone else can recreate this problem I've come across
with using the find command in AFS. I don't know if its a problem with
the RHEL's find command, the OpenAFS client, or a combination of the 2.
I do NOT have this probl
On Tue, 5 Apr 2005, Andy Malato wrote:
I am attempting to build openafs-1.3.80 on am AMD64 platform (dual cpu)
with kernel 2.6.8.1
Add -lresolv to XLIBS in src/cf/osconf.m4, and rerun autoconf?
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https:
I am attempting to build openafs-1.3.80 on am AMD64 platform (dual cpu)
with kernel 2.6.8.1
The build fails with the following error messages :
/home/noderestore/install/afs/openafs-1.3.80/src/auth/cellconfig.c:753:
undefined reference to `__res_search'
libauth.a(cellconfig.o)(.text+0xbfa):/
Hi,
On Tue, Apr 05, 2005 at 11:49:00AM -0400, Sandesh V Chopdekar wrote:
[snip]
> I don't know, but 50 meg is too less for a server. Though depends on
> the amount of data, that you want to put on it.
> But I guess, it would still work.
Yeah, it does :-) :
[EMAIL PROTECTED]:~ > df -Ph
If partitioning is a problem, a loopback file could be mounted as /vicepa
just for test.
tedc
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Sandesh V Chopdekar
Sent: Tuesday, April 05, 2005 8:49 AM
To: openafs-info@openafs.org; [EMAIL PROTECTED]
Subject:
On Tue, 5 Apr 2005, Craig Cook wrote:
In the IBM docs for creating a client it contains this:
Create a directory called /vicepxx for each AFS server partition you are
configuring (there must be at least one). Repeat the command for each partition.
# mkdir /vicepxx
Does there really need to be at
/vicepa is not needed for clients - it is used by AFS fileservers.
>> Is there a minimum size /vicepa must be? Can I make it 50 meg and
everything still work?
I don't know, but 50 meg is too less for a server. Though depends on
the amount of data, that you want to put on it.
But I
"Craig Cook" <[EMAIL PROTECTED]> writes:
> In the IBM docs for creating a client it contains this:
>
>
> Create a directory called /vicepxx for each AFS server partition you are
> configuring (there must be at least one). Repeat the command for each
> partition.
>
># mkdir /vicepxx
>
>
In the IBM docs for creating a client it contains this:
Create a directory called /vicepxx for each AFS server partition you are
configuring (there must be at least one). Repeat the command for each partition.
# mkdir /vicepxx
Does there really need to be at least one /vicepa partition? I
22 matches
Mail list logo
