BUGS revision 38494 
1# -*- text -*-
2
3	    LIST OF KNOWN BUGS IN AM-UTILS OR OPERATING SYSTEMS
4
5
6(1) mips-sgi-irix*
7
8[1A] known to have flakey NFS V.3 and TCP.  Amd tends to hang or spin
9infinitely after a few hours or days of use.  Users must install recommended
10patches from vendor.  Patches help, but not all the time.  Otherwise avoid
11using NFS V.3 and TCP on these systems, by setting
12
13	/defaults opts:=vers=2,proto=udp
14
15[1B] yp_all() leaks a file descriptor.  Eventually amd runs out of file
16descriptors and hangs.  Am-utils circumvents this by using its own version
17of yp_all which uses udp and iterats over NIS maps.  The latter isn't as
18reliable as yp_all() which uses TCP, but it is better than hanging.
19
20
21(2) alpha-unknown-linux-gnu (RedHat Linux 4.2)
22
23hasmntopt(mnt, opt) can goes into an infinite loop if opt is any substring
24of mnt->mnt_opts.  Redhat 5.0 does not have this libc bug.  Here is an
25example program:
26
27#include <stdio.h>
28#include <mntent.h>
29main()
30{
31  struct mntent mnt;
32  char *cp;
33  mnt.mnt_opts = "intr,rw,port=1023,timeo=8,foo=br,retrans=110,indirect,map=/usr/local/AMD/etc/amd.proj,boo";
34  cp = hasmntopt(&mnt, "ro");
35  printf("cp = %s\n", cp);
36  exit(0);
37}
38
39
40(3) mips-dec-ultrix4.3
41
42Rainer Orth <ro@TechFak.Uni-Bielefeld.DE> reports
43
44[3A] At least the gcc 2.7.0 fixincludes-mangled <sys/utsname.h> needs a
45forward declaration of struct utsname to avoid lots of gcc warnings:
46
47RCS file: RCS/utsname.h,v
48retrieving revision 1.1
49diff -u -r1.1 utsname.h
50--- utsname.h   1995/06/19 13:07:01     1.1
51+++ utsname.h   1998/01/27 12:34:26
52@@ -59,6 +59,7 @@
53 #ifdef KERNEL
54 #include "../h/limits.h"
55 #else /* user mode */
56+struct utsname;
57 extern int     uname _PARAMS((struct utsname *));
58 #endif
59 #define __SYS_NMLN 32
60
61[3B] It autoconfigures and compiles cleanly, but currently hangs after a
62couple of hours without leaving any traces in the syslog output.
63
64
65(4) powerpc-ibm-aix4.2.1.0
66
67[4A] "Randall S. Winchester" <rsw@Glue.umd.edu> reports that for amd to
68start, you need to kill and restart rpc.mountd and possibly also make sure
69that nfsd is running.  Normally these are not required.
70
71[4B] "Stefan Vogel" <vogel@physik.unizh.ch> reports that if your amq
72executable dump core unexpectedly, then it may be a bug in gcc 2.7.x.
73Upgrade to gcc 2.8.x or use IBM's xlC compiler.
74