Re: [OpenAFS] Re: question for people running OpenAFS on Windows and have Cygwin
The Windows CIFS client authenticates to the AFS Client SMB Service using NTLM with a special loopback authentication mode. If you have not logged into Windows with a password then there is no password for the Windows CIFS client to use to authenticate to the AFS Client SMB Service. If and when a File System Redirector implementation is available, then we won't have this restriction. Your password-less SSHD more than likely has other problems as well since the SSHD is running as a service in a session without a desktop. The service does not have the ability to establish authenticated network connections using the Windows APIs and user authorization data. Jeffrey Altman Adam Megacz wrote: In case anybody else encounters this... I think this is part of the problem: for some reason if you log into windows without using a password, you don't get to see mapped drives. Apparently whatever causes this restriction also (understandably) causes AFS shares to behave strangely from the perspective of a user logged in via passwordless-ssh -- even when accessing those shares via UNC pathnames: http://www.cygwin.com/ml/cygwin/2003-10/msg01454.html A cygwin window physically on the machine itself, or a password-based login via ssh are causing me way fewer problems. I'm trying to get it to crash again so I can send that dump. - a ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info smime.p7s Description: S/MIME Cryptographic Signature
[OpenAFS] many packet are as rx_ignoreAckedPacket and meltdown
Hello, I don't know what is rx_ignoreAckedPacket. I have thousands (up to 5) per 15 seconds of rx_ignoreAckedPacket on the fileserver. Number of calls are less (up to 1). Is posible tenth calls of rx_ignoreAckedPacket? We have this infrastructure: Fileservers (large mode): OpenAFS 1.3.81 built 2005-05-14 (debian/stable) windows and linux clients from version 1.2 to 1.4 and for experimantal use 1.5 OpenAFS 1.2.10 built 2005-04-06 OpenAFS 1.3.82 built 2005-08-20 OpenAFS 1.4.2fc4 built 2006-10-02 OpenAFS1.4.0101 Some of fileserver sometimes going to meltdown state (calls waiting for a thread) and don't know reason. There is 'rxdebug -rxstats': Free packets: 935, packet reclaims: 1283, calls: 2197185, used FDs: 64 not waiting for packets. 201 calls waiting for a thread 2 threads are idle rx stats: free packets 935, allocs 7046769, alloc-failures(rcv 0/0,send 0/0,ack 0) greedy 0, bogusReads 0 (last from host 0), noPackets 0, noBuffers 0, selects 0, sendSelects 0 packets read: data 2220845 ack 3323232 busy 5 abort 5125 ackall 3 challenge 4 response 1098 debug 43944 params 0 unused 0 unused 0 unused 0 version 0 other read counters: data 2220774, ack 3322547, dup 0 spurious 165 dally 5 packets sent: data 2851035 ack 54295 busy 592 abort 72 ackall 0 challenge 109 8 response 4 debug 0 params 0 unused 0 unused 0 unused 0 version 0 other send counters: ack 54295, data 9546732 (not resends), resends 2908, pus hed 0, ackedignored 3238665 (these should be small) sendFailed 0, fatalErrors 0 Average rtt is 0.006, with 745772 samples Minimum rtt is 0.000, maximum is 60.235 518 server connections, 676 client connections, 706 peer structs, 350 call st ructs, 0 free call structs Thanks for any answer. Michal Svamberg ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] Re: openafs and linux 2.6.19-rc1 [patch]
In message [EMAIL PROTECTED],Alex Romosan writes:
sorry to follow up on my own post, but the above patch works only for
reads. for writes one also needs to add
.aio_write = generic_file_aio_write,
below .aio_read above.
it needs configure tests for those of us with antique 2.6.18 kernels.
try this:
Index: src/afs/LINUX/osi_vfsops.c
===
RCS file: /cvs/openafs/src/afs/LINUX/osi_vfsops.c,v
retrieving revision 1.29.2.17
diff -u -u -r1.29.2.17 osi_vfsops.c
--- src/afs/LINUX/osi_vfsops.c 20 Aug 2006 05:34:18 - 1.29.2.17
+++ src/afs/LINUX/osi_vfsops.c 6 Oct 2006 13:00:39 -
@@ -312,8 +312,7 @@
void
afs_destroy_inodecache(void)
{
-if (kmem_cache_destroy(afs_inode_cachep))
- printk(KERN_INFO afs_inode_cache: not all structures were freed\n);
+(void) kmem_cache_destroy(afs_inode_cachep);
}
#else
int
Index: src/afs/LINUX/osi_vnodeops.c
===
RCS file: /cvs/openafs/src/afs/LINUX/osi_vnodeops.c,v
retrieving revision 1.81.2.43
diff -u -u -r1.81.2.43 osi_vnodeops.c
--- src/afs/LINUX/osi_vnodeops.c13 Aug 2006 16:50:43 -
1.81.2.43
+++ src/afs/LINUX/osi_vnodeops.c6 Oct 2006 13:00:39 -
@@ -75,7 +75,11 @@
else {
osi_FlushPages(vcp, credp); /* ensure stale pages are gone */
AFS_GUNLOCK();
+#ifdef DO_SYNC_READ
+ code = do_sync_read(fp, buf, count, offp);
+#else
code = generic_file_read(fp, buf, count, offp);
+#endif
AFS_GLOCK();
}
@@ -121,7 +125,11 @@
code = -code;
else {
AFS_GUNLOCK();
+#ifdef DO_SYNC_READ
+ code = do_sync_write(fp, buf, count, offp);
+#else
code = generic_file_write(fp, buf, count, offp);
+#endif
AFS_GLOCK();
}
@@ -550,6 +558,10 @@
.read = generic_read_dir,
#endif
.readdir = afs_linux_readdir,
+#ifdef GENERIC_FILE_AIO_READ
+ .aio_read = generic_file_aio_read,
+ .aio_write = generic_file_aio_write,
+#endif
#ifdef HAVE_UNLOCKED_IOCTL
.unlocked_ioctl = afs_unlocked_xioctl,
#else
Index: src/cf/linux-test4.m4
===
RCS file: /cvs/openafs/src/cf/linux-test4.m4,v
retrieving revision 1.20.2.13
diff -u -u -r1.20.2.13 linux-test4.m4
--- src/cf/linux-test4.m4 6 Sep 2006 20:57:17 - 1.20.2.13
+++ src/cf/linux-test4.m4 6 Oct 2006 13:00:39 -
@@ -644,3 +644,29 @@
if test x$ac_cv_key_alloc_needs_struct_task = xyes; then
AC_DEFINE([KEY_ALLOC_NEEDS_STRUCT_TASK], 1, [define if key_alloc takes a
struct task *])
fi])
+
+AC_DEFUN([LINUX_DO_SYNC_READ], [
+ AC_MSG_CHECKING([for linux do_sync_read()])
+ AC_CACHE_VAL([ac_cv_linux_do_sync_read], [
+AC_TRY_KBUILD(
+[#include linux/fs.h],
+[do_sync_read(NULL, NULL, 0, NULL);],
+ ac_cv_linux_do_sync_read=yes,
+ ac_cv_linux_do_sync_read=no)])
+ AC_MSG_RESULT($ac_cv_linux_do_sync_read)
+ if test x$ac_cv_linux_do_sync_read = xyes; then
+AC_DEFINE([DO_SYNC_READ], 1, [define if your kernel has do_sync_read()])
+ fi])
+
+AC_DEFUN([LINUX_GENERIC_FILE_AIO_READ], [
+ AC_MSG_CHECKING([for linux generic_file_aio_read()])
+ AC_CACHE_VAL([ac_cv_linux_generic_file_aio_read], [
+AC_TRY_KBUILD(
+[#include linux/fs.h],
+[generic_file_aio_read(NULL, NULL, 0, 0);],
+ ac_cv_linux_generic_file_aio_read=yes,
+ ac_cv_linux_generic_file_aio_read=no)])
+ AC_MSG_RESULT($ac_cv_linux_generic_file_aio_read)
+ if test x$ac_cv_linux_generic_file_aio_read = xyes; then
+AC_DEFINE([GENERIC_FILE_AIO_READ], 1, [define if your kernel has
generic_file_aio_read()])
+ fi])
Index: acinclude.m4
===
RCS file: /cvs/openafs/acinclude.m4,v
retrieving revision 1.114.2.61
diff -u -u -r1.114.2.61 acinclude.m4
--- acinclude.m419 Sep 2006 22:23:00 - 1.114.2.61
+++ acinclude.m46 Oct 2006 13:00:39 -
@@ -608,6 +608,8 @@
LINUX_REFRIGERATOR
LINUX_LINUX_KEYRING_SUPPORT
LINUX_KEY_ALLOC_NEEDS_STRUCT_TASK
+LINUX_DO_SYNC_READ
+LINUX_GENERIC_FILE_AIO_READ
LINUX_EXPORTS_SYS_CHDIR
LINUX_EXPORTS_SYS_CLOSE
LINUX_EXPORTS_SYS_OPEN
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] many packet are as rx_ignoreAckedPacket and meltdown
On Oct 6, 2006, at 04:52, Michal Svamberg wrote: Hello, I don't know what is rx_ignoreAckedPacket. I have thousands (up to 5) per 15 seconds of rx_ignoreAckedPacket on the fileserver. Number of calls are less (up to 1). Is posible tenth calls of rx_ignoreAckedPacket? First, upgrade your fileserver an actual production release, such as 1.4.1. 1.3.81 was pretty good, but, not without problems. (1.4.1 is not without problems, but with less.) Second, when your server goes into a this state, does it come out of it naturally or do you have to restart it? -rob ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] many packet are as rx_ignoreAckedPacket and meltdown
On Fri, 6 Oct 2006, Robert Banz wrote: On Oct 6, 2006, at 04:52, Michal Svamberg wrote: Hello, I don't know what is rx_ignoreAckedPacket. I have thousands (up to 5) per 15 seconds of rx_ignoreAckedPacket on the fileserver. Number of calls are less (up to 1). Is posible tenth calls of rx_ignoreAckedPacket? First, upgrade your fileserver an actual production release, such as 1.4.1. 1.3.81 was pretty good, but, not without problems. (1.4.1 is not without problems, but with less.) Second, when your server goes into a this state, does it come out of it naturally or do you have to restart it? Third, was there some previous version where this did not happen? Derrick ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] many packet are as rx_ignoreAckedPacket and meltdown
Hi Robert, and many thanks for your reply! Let me answer on behalf on Michal - we are co-workes and Michal has left to vacations for couple of days ;-) Robert Banz wrote: First, upgrade your fileserver an actual production release, such as 1.4.1. 1.3.81 was pretty good, but, not without problems. (1.4.1 is not without problems, but with less.) We are thinking of that as a one (last) of possibility, but we are running tens of linux (Debian/stable) servers (not only AFS) as a part of our distributed computing environment and we are trying to keep our server configuration as close as possible to stable dist. And short summary: we don't have any significant AFS problems with same configuration for 1+years... Second, when your server goes into a this state, does it come out of it naturally or do you have to restart it? Actually, this state can freeze many of our users and services (even if affected server servers RO replicas only... and yes, I really don't understand this behavior...) and FS is unable to return to normal state at reasonable time (actually / reasonable time is pretty small for us/our users...). So, we are trying to solve our current problems with fs restart. :-( ( As you can see from original post, FS is still alive, but has no idle threads. Waiting connections (clients) oscillate around 200 and probably could be serve in tens of minutes... ) Thanks again for your reply and suggestions!! -- -- Lubos Kejzlar Head of Laboratory for Computer Science Center for Information Technology Tel.: +420-377 632 710 University of West Bohemia+420-724 094 277 Univerzitni 8, 306 14 Pilsen Fax: +420-377 632 702 Czech Republic E-mail: [EMAIL PROTECTED] -- smime.p7s Description: S/MIME Cryptographic Signature
Re: [OpenAFS] many packet are as rx_ignoreAckedPacket and meltdown
First, upgrade your fileserver an actual production release,
such as 1.4.1. 1.3.81 was pretty good, but, not without
problems. (1.4.1 is not without problems, but with less.)
We are thinking of that as a one (last) of possibility, but we are
running tens of linux (Debian/stable) servers (not only AFS) as a
part of our distributed computing environment and we are trying to
keep our server configuration as close as possible to stable dist.
And short summary: we don't have any significant AFS problems with
same configuration for 1+years...
Keeping with random linux distro's idea of stable for your AFS code
is not a good idea. Stick with OpenAFS's idea of stable -- and while
for short periods I've ran development (e.g late 1.3.*) code on my
production AFS servers when I was in a pinch, stick to the production
releases. Ignore what Debian thinks, because they don't know what
they're talking about ;)
Second, when your server goes into a this state, does it come out
of it naturally or do you have to restart it?
Actually, this state can freeze many of our users and services
(even if affected server servers RO replicas only... and yes, I
really don't understand this behavior...) and FS is unable to
return to normal state at reasonable time (actually / reasonable
time is pretty small for us/our users...). So, we are trying to
solve our current problems with fs restart. :-(
(
As you can see from original post, FS is still alive, but has no
idle threads. Waiting connections (clients) oscillate around 200
and probably could be serve in tens of minutes...
)
You could have the horrible host callback table mutex lockup
problem. The most for-certain way to discover this is to generate a
core from your running fileserver at the time (on Solaris I use
gcore, but you could also kill -SEGV it instead of restarting),
attach a debugger to the core, and see where the threads are
sitting. If you've compiled your OpenAFS distribution with --enable-
debug (which you should), and you examine the stack trace some of the
threads, you may see a lot of them here:
=[5] CallPreamble(acall = ???, activecall = ???, tconn = ???, ahostp
= ???) (optimized), at 0x8082178 (line ~315) in afsfileprocs.c
(dbx) list
315 H_LOCK;
316 retry:
317 tclient = h_FindClient_r(*tconn);
318 thost = tclient-host;
319 if (tclient-prfail == 1) { /* couldn't get the CPS */
...
If this is the case...well...there's no for-sure way around it right
now, though some people, IIRC, have been working on some code changes
to avoid it. Some steps you can take, though, to mitigate the
problem involve making sure all your clients respond promptly on
their AFS callback ports (7001/udp). With all of the packet manglers
out on the network (hostbased firewalls, overanxious network
administrators, etc.) you may find things in the way of the AFS
fileservers contacting their clients on the callback port. One of
the things that can cause this type of lockup are requests to these
clients timing out / taking a long time... If things have been
working fine for awhile and now they don't, network topology/
firewall changes like this could be a culprit.
I've attached a script that I periodically run to see how many bad
clients are using my fileservers, so that I may try to track them
down and swat at them...
-
#!/usr/local/bin/perl
$| = 1;
sub getclients {
my $server = shift @_;
my %ips;
print STDERR getting connections for $server\n;
open(RXDEBUG, /usr/afsws/etc/rxdebug -allconnections
$server|) || die
cannot exec rxdebug\n;
while(RXDEBUG) {
if ( /Connection from host ([^, ]+)/ ) {
my $ip = $1;
if ( ! defined($ips{$ip}) ) {
$ips{$ip} = $ip;
}
}
}
close RXDEBUG;
return keys(%ips);
}
sub checkcmdebug {
my $client = shift @_;
print STDERR checking $client\n;
open(CMDEBUG, /usr/afsws/bin/cmdebug -cache $client 21|)
|| die canot exec cmdebug\n;
while(CMDEBUG) {
if ( /server or network not responding/ ) {
return 0;
}
}
close CMDEBUG;
return 1;
}
my %clients;
# modify this to run getclients on all of your AFS servers...
foreach my $y ( ifs1, ifs2, hfs1, hfs2, bfs1, hfs11,
hfs12 ) {
foreach my $x ( getclients($y..afs.umbc.edu) ) {
$clients{$x}++;
}
}
use Socket;
foreach my $x ( keys(%clients) ) {
if ( ! checkcmdebug($x) ) {
print $x;
use Socket;
my $iaddr = inet_aton($x);
my $name = gethostbyaddr($iaddr, AF_INET);
print ($name)\n;
}
}
___
Re: [OpenAFS] many packet are as rx_ignoreAckedPacket and meltdown
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Robert Banz wrote: First, upgrade your fileserver an actual production release, such as 1.4.1. 1.3.81 was pretty good, but, not without problems. (1.4.1 is not without problems, but with less.) We are thinking of that as a one (last) of possibility, but we are running tens of linux (Debian/stable) servers (not only AFS) as a part of our distributed computing environment and we are trying to keep our server configuration as close as possible to stable dist. And short summary: we don't have any significant AFS problems with same configuration for 1+years... Keeping with random linux distro's idea of stable for your AFS code is not a good idea. Stick with OpenAFS's idea of stable -- and while for short periods I've ran development (e.g late 1.3.*) code on my production AFS servers when I was in a pinch, stick to the production releases. Ignore what Debian thinks, because they don't know what they're talking about ;) The problem is, OpenAFS isn´t synced with distros developement. OpenAFS got better and better on a very quick timeslot (a BIG thx for all the team behind this). So far it wasn´t easy for the stable distros to select the correct version to take. At least in sarge it´s a problem, because sarge is stable for some time... In next Debian there will be a 1.4.x version. And I think the 1.4.1+ versions are much stable than 1.3.8x and so better to keep stable for some time. At least there ARE some 1.4.x builts of OpenAFS for debian sarge easy to install. Nevertheless we use 1.4.1 and 1.4.fc2/4 in production here on debian sarge and it works well enough for our small cell. Most of our problems are with the windows version, which is not as mature as the linux version (in my opinion), which doesn´t mean it isn´t as stable as the linux version. MfG, Lars Schimmer - -- - - TU Graz, Institut für ComputerGraphik WissensVisualisierung Tel: +43 316 873-5405 E-Mail: [EMAIL PROTECTED] Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (MingW32) iD8DBQFFJnp2mWhuE0qbFyMRAt9oAJ99ImBagpENURWmABPxONOMYc+K7ACeJcob pWepS+6uze+lcOb/deA5zio= =lX5y -END PGP SIGNATURE- ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
[OpenAFS] Re: openafs and linux 2.6.19-rc1 [patch]
chas williams - CONTRACTOR [EMAIL PROTECTED] writes: @@ -550,6 +558,10 @@ .read =generic_read_dir, #endif .readdir = afs_linux_readdir, +#ifdef GENERIC_FILE_AIO_READ + .aio_read =generic_file_aio_read, + .aio_write = generic_file_aio_write, +#endif #ifdef HAVE_UNLOCKED_IOCTL .unlocked_ioctl = afs_unlocked_xioctl, #else i think this chunk (in src/afs/LINUX/osi_vnodeops.c) ended in the wrong place. the .aio_read/write were added to afs_dir_fops but they should have been added to afs_file_fops instead (the next structure below). at least that's what i had in my working version. --alex-- -- | I believe the moment is at hand when, by a paranoiac and active | | advance of the mind, it will be possible (simultaneously with | | automatism and other passive states) to systematize confusion | | and thus to help to discredit completely the world of reality. | ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] Debian sarge packages for 1.4.1
Lars Schimmer [EMAIL PROTECTED] wrote: The problem is, OpenAFS isn4t synced with distros developement. OpenAFS got better and better on a very quick timeslot (a BIG thx for all the team behind this). So far it wasn4t easy for the stable distros to select the correct version to take. At least in sarge it4s a problem, because sarge is stable for some time... In next Debian there will be a 1.4.x version. And I think the 1.4.1+ versions are much stable than 1.3.8x and so better to keep stable for some time. At least there ARE some 1.4.x builts of OpenAFS for debian sarge easy to install. There are 1.4.1 pacakges for sarge at http://backports.org AFAIK they work just fine. I know that openafs.org hosted some 1.2.X woody packages in the past. Are there plans to do this again for 1.4.X for sarge? CDC ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
[OpenAFS] Suse SLES 10 IBM PPC64 AFS client : Config error (SLIM ERROR) Linux 2.6.16.21-08-ppc64
Hi,
I read all 2 months ago topics on the list.
Hardware : IBM REGATTA PowerPC 4 64 bits on dynamic LPAR with SuSE Linux,
LVM + Raid 1
I have installed the source tree, make suggested changes
cd/usr/src/linux
make cloneconfig
make prepare
make modules-prepare
cd /lib/modules/`uname -r`
rm build
ln -s source build
mkdir extra
export KERNEL_SOURCE=/usr/src/linux
go in the afs source tree (tried openafs 1.4.1 and 1.4.0)
launch
./configure --with-linux-kernel-headers=/usr/src/linux
--with-afs-sysname=ppc64-linux26 --enable-transarc-path
file config.log contains
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
configure:621: checking for a BSD compatible install
configure:674: checking whether build environment is sane
configure:731: checking whether make sets ${MAKE}
configure:777: checking for working aclocal
configure:790: checking for working autoconf
configure:803: checking for working automake
configure:816: checking for working autoheader
configure:829: checking for working makeinfo
configure:847: checking for gcc
configure:960: checking whether the C compiler (gcc ) works
configure:976: gcc -o conftestconftest.c 15
configure:1002: checking whether the C compiler (gcc ) is a cross-compiler
configure:1007: checking whether we are using GNU C
configure:1035: checking whether gcc accepts -g
configure:1067: checking how to run the C preprocessor
configure:1147: checking for ANSI C header files
configure:1259: checking host system type
configure:1494: checking for AIX
configure:1518: checking for POSIXized ISC
configure:1540: checking for minix/config.h
configure:1589: checking for pid_t
configure:1622: checking for size_t
configure:1655: checking return type of signal handlers
configure:1697: checking for __FUNCTION__ and __LINE__ macros
configure:1743: checking for a BSD compatible install
configure:1796: checking whether ln -s works
configure:1819: checking for ranlib
configure:1851: checking for bison
configure:1887: checking for flex
configure:1920: checking for flex
configure:1954: checking for yywrap in -lfl
configure:1996: checking lex output file root
configure:2017: checking whether yytext is a pointer
configure:2072: checking whether byte order is known at compile time
configure:2103: checking whether byte ordering is bigendian
configure:2180: checking your OS
configure:2752: checking if gcc accepts -march=pentium
configure:2767: gcc -c -MARCH=pentium conftest.c 15
gcc: unrecognized option '-MARCH=pentium'
configure:2790: checking if gcc needs -fno-strength-reduce
configure:2805: gcc -c -fno-strength-reduce conftest.c 15
configure:2825: checking if gcc needs -fno-strict-aliasing
configure:2840: gcc -c -fno-strict-aliasing conftest.c 15
configure:2860: checking if gcc supports -fno-common
configure:2875: gcc -c -fno-common conftest.c 15
configure:2895: checking if gcc supports -pipe
configure:2910: gcc -c -pipe conftest.c 15
configure:2931: checking whether to build osi_vfs.h
configure:2943: checking for linux/completion.h existance
configure:2979: checking for defined for_each_process
configure:3012: checking for defined prev_task
configure:3045: checking for alloc_inode in struct super_operations
configure:3077: checking for page_lock in struct address_space
configure:3109: checking for gfp_mask in struct address_space
configure:3141: checking for i_alloc_sem in struct inode
configure:3173: checking for i_truncate_sem in struct inode
configure:3205: checking for i_dirty_data_buffers in struct inode
configure:3237: checking for i_devices in struct inode
configure:3269: checking for i_mmap_shared in struct inode
configure:3301: checking for i_mutex in struct inode
configure:: checking for i_sb_list in struct inode
configure:3365: checking for i_security in struct inode
configure:3397: checking for inotify_lock in struct inode
configure:3429: checking for inotify_sem in struct inode
configure:3461: checking for inode_setattr return type
configure:3495: checking for write_inode return type
configure:3531: checking whether inode_operations.create takes a nameidata
configure:3568: checking whether inode_operations.lookup takes a nameidata
configure:3605: checking whether inode_operations.permission takes a
nameidata
configure:3641: checking whether dentry_operations.d_revalidate takes a
nameidata
configure:3682: checking whether address_space_operations.writepage takes a
writeback_control
configure:3722: checking for linux/syscall.h in kernel
configure:3733: checking for linux/seq_file.h in kernel
configure:3744: checking for SELinux kernel
configure:3777: checking for 5th argument in sock_create found in some
SELinux kernels
configure:3810: checking for page_follow_link_light vs page_follow_link
configure:3848: checking for redhat kernel configuration
configure:3867: checking for recalc_sigpending arg type
configure:3898: checking for parent in struct task_struct
configure:3930: checking for
[OpenAFS] AFS installation
hi, i have a project involving kerberos and AFS. i found a problem in finding any sites that can assist me to install and configure AFSso that it canwork with kerberos as i am still newin it..can someone post a link that help me in doing my project or anyhelp from you ???thanks,citra How low will we go? Check out Yahoo! Messengers low PC-to-Phone call rates.
[OpenAFS] Re: openafs and linux 2.6.19-rc1 [patch]
In message [EMAIL PROTECTED],Alex Romosan writes:
i think this chunk (in src/afs/LINUX/osi_vnodeops.c) ended in the
wrong place. the .aio_read/write were added to afs_dir_fops but they
should have been added to afs_file_fops instead (the next structure
below). at least that's what i had in my working version.
yep. i guess i need my head examined. derrick, please apply
this (the patch seemed to make it into afs already).
--- src/afs/LINUX/osi_vnodeops.c.0002006-10-06 12:51:19.0 -0400
+++ src/afs/LINUX/osi_vnodeops.c2006-10-06 12:48:43.0 -0400
@@ -558,10 +558,6 @@
.read = generic_read_dir,
#endif
.readdir = afs_linux_readdir,
-#ifdef GENERIC_FILE_AIO_READ
- .aio_read = generic_file_aio_read,
- .aio_write = generic_file_aio_write,
-#endif
#ifdef HAVE_UNLOCKED_IOCTL
.unlocked_ioctl = afs_unlocked_xioctl,
#else
@@ -577,6 +573,10 @@
struct file_operations afs_file_fops = {
.read = afs_linux_read,
.write = afs_linux_write,
+#ifdef GENERIC_FILE_AIO_READ
+ .aio_read = generic_file_aio_read,
+ .aio_write = generic_file_aio_write,
+#endif
#ifdef HAVE_UNLOCKED_IOCTL
.unlocked_ioctl = afs_unlocked_xioctl,
#else
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] OpenAFS1.4.2fc4 and Mac OS X 10.4.8
At 1:57 AM -0400 10/6/06, Derrick J Brashear wrote: On Thu, 5 Oct 2006, Garance A Drosihn wrote: At 12:34 PM -0400 10/3/06, Derrick J Brashear wrote: Already fixed in CVS. Which branch is the fix in? I tried openafs-stable-1_4_x, but that didn't seem to build for me. Failing how? Hmm. Well, I *think* it had failed with an error in src/vol/clone.c, but I just pulled down a fresh copy of that branch and it compiled fine. So now I will install it and see how well it works! (I had tried a few different branches yesterday, so the clone.c error might have been in a different branch) -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] AFS installation
nihh citra wrote: hi, i have a project involving kerberos and AFS. i found a problem in finding any sites that can assist me to install and configure AFS so that it can work with kerberos as i am still new in it..can someone post a link that help me in doing my project or any help from you ??? Take a look at http://www.scode.org/afs/openafs-install.txt courtesy of https://lists.openafs.org/pipermail/openafs-info/2006-September/023747.html It presents a quick set of instructions for setting up Kerberos and AFS. Jason ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
