Has anyone successfully built Samba 2.0.2 with AFS support? Are there any
hints or tips available? The documentation that ships with 2.0.2 still
refers to editing the AFS section of the Makefile, which no longer applies.
I tried pasting the includes and libraries from the 1.9.18 Makefile into
the 2.0.2 Makefile generated by the configure script, but I get a bunch of
conflicts and redefinitions between the AFS headers and the standard
headers. I can still build 1.9.18 with AFS support with no problems. If
anyone can point me to some help on getting the latest version built with
AFS support I'd be most grateful.
I've appended the errors that I'm getting when I try to compile
pass_check.c (the first module that calls for the AFS includes and
libraries). I've tried this under both Linux and HPUX 10.20, with identical
results. This run was attempted on a RedHat 5.2 system with kernel version
2.0.32. Linux-AFS is installed and running on this system.
--Ken
Using FLAGS = -O -Iinclude -I/usr/afsws/include -I./include -I./ubiqx
-I./smbwr
apper -DSMBLOGFILE="/opt/samba/var/log.smb"
-DNMBLOGFILE="/opt/samba/var/log.nm
b" -DCONFIGFILE="/opt/samba/lib/smb.conf"
-DLMHOSTSFILE="/opt/samba/lib/lmhosts"
-DSWATDIR="/opt/samba/swat" -DSBINDIR="/opt/samba/bin"
-DLOCKDIR="/opt/samba/
var/locks" -DSMBRUN="/opt/samba/bin/smbrun"
-DCODEPAGEDIR="/opt/samba/lib/codepa
ges" -DDRIVERFILE="/opt/samba/lib/printers.def"
-DBINDIR="/opt/samba/bin"
-DHAVE
_INCLUDES_H -DPASSWD_PROGRAM="/bin/passwd"
-DSMB_PASSWD_FILE="/opt/samba/private
/smbpasswd"
Using FLAGS32 = -O -Iinclude -I/usr/afsws/include -I./include -I./ubiqx
-I./smb
wrapper -DSMBLOGFILE="/opt/samba/var/log.smb"
-DNMBLOGFILE="/opt/samba/var/log.
nmb" -DCONFIGFILE="/opt/samba/lib/smb.conf"
-DLMHOSTSFILE="/opt/samba/lib/lmhost
s" -DSWATDIR="/opt/samba/swat"
-DSBINDIR="/opt/samba/bin"
-DLOCKDIR="/opt/samb
a/var/locks" -DSMBRUN="/opt/samba/bin/smbrun"
-DCODEPAGEDIR="/opt/samba/lib/code
pages" -DDRIVERFILE="/opt/samba/lib/printers.def"
-DBINDIR="/opt/samba/bin"
-DHA
VE_INCLUDES_H -DPASSWD_PROGRAM="/bin/passwd"
-DSMB_PASSWD_FILE="/opt/samba/priva
te/smbpasswd"
Using LIBS = -lreadline -ldl -lcrypt -lpam -L/usr/afsws/lib
-L/usr/afsws/lib/af
s -lkauth -lprot -lubik -lauth -lrxkad -lsys -ldes -lrx -llwp -lcom_err -laudit
usr/afsws/lib/afs/util.a
Compiling passdb/pass_check.c
In file included from passdb/pass_check.c:140:
/usr/afsws/include/afs/stds.h:118: warning: `uint32' redefined
include/includes.h:420: warning: this is the location of the previous
definition
In file included from /usr/afsws/include/afs/kautils.h:42,
from passdb/pass_check.c:141:
/usr/afsws/include/rx/xdr.h:43: warning: `FALSE' redefined
/usr/include/rpc/types.h:40: warning: this is the location of the previous
defin
ition
/usr/afsws/include/rx/xdr.h:44: warning: `TRUE' redefined
/usr/include/rpc/types.h:41: warning: this is the location of the previous
defin
ition
/usr/afsws/include/rx/xdr.h:237: warning: `IXDR_GET_BOOL' redefined
/usr/include/rpc/xdr.h:231: warning: this is the location of the previous
defini
tion
/usr/afsws/include/rx/xdr.h:238: warning: `IXDR_GET_ENUM' redefined
/usr/include/rpc/xdr.h:232: warning: this is the location of the previous
defini
tion
/usr/afsws/include/rx/xdr.h:240: warning: `IXDR_GET_SHORT' redefined
/usr/include/rpc/xdr.h:234: warning: this is the location of the previous
defini
tion
/usr/afsws/include/rx/xdr.h:241: warning: `IXDR_GET_U_SHORT' redefined
/usr/include/rpc/xdr.h:235: warning: this is the location of the previous
defini
tion
/usr/afsws/include/rx/xdr.h:243: warning: `IXDR_PUT_BOOL' redefined
/usr/include/rpc/xdr.h:237: warning: this is the location of the previous
defini
tion
/usr/afsws/include/rx/xdr.h:244: warning: `IXDR_PUT_ENUM' redefined
/usr/include/rpc/xdr.h:238: warning: this is the location of the previous
defini
tion
/usr/afsws/include/rx/xdr.h:246: warning: `IXDR_PUT_SHORT' redefined
/usr/include/rpc/xdr.h:240: warning: this is the location of the previous
defini
tion
/usr/afsws/include/rx/xdr.h:247: warning: `IXDR_PUT_U_SHORT' redefined
/usr/include/rpc/xdr.h:241: warning: this is the location of the previous
defini
tion
In file included from passdb/pass_check.c:140:
/usr/afsws/include/afs/stds.h:103: warning: useless keyword or type name in
empt
y declaration
/usr/afsws/include/afs/stds.h:103: warning: empty declaration
/usr/afsws/include/afs/stds.h:109: warning: useless keyword or type name in
empt
y declaration
/usr/afsws/include/afs/stds.h:109: warning: empty declaration
In file included from /usr/afsws/include/afs/kautils.h:42,
from passdb/pass_check.c:141:
/usr/afsws/include/rx/xdr.h:106: redeclaration of `enum xdr_op'
/usr/afsws/include/rx/xdr.h:107: conflicting types for `XDR_ENCODE'
/usr/include/rpc/xdr.h:86: previous declaration of `XDR_ENCODE'
/usr/afsws/include/rx/xdr.h:108: conflicting types for `XDR_DECODE'
/usr/include/rpc/xdr.h:87: previous declaration of `XDR_DECODE'
/usr/afsws/include/rx/xdr.h:110: conflicting types for `XDR_FREE'
/usr/include/rpc/xdr.h:89: previous declaration of `XDR_FREE'
/usr/afsws/include/rx/xdr.h:126: conflicting types for `xdrproc_t'
/usr/include/rpc/xdr.h:144: previous declaration of `xdrproc_t'
/usr/afsws/include/rx/xdr.h:136: redefinition of `struct xdr_ops'
/usr/afsws/include/rx/xdr.h:150: conflicting types for `XDR'
/usr/include/rpc/xdr.h:104: previous declaration of `XDR'
/usr/afsws/include/rx/xdr.h:214: redefinition of `struct xdr_discrim'
make: *** [passdb/pass_check.o] Error 1
---------------------------------------------------------------------------
Ken Weiss krweiss@ucdavis.edu
Distributed Computing Analysis & Support 530/752-5554 (voice)
2240 Academic Surge 530/523-4617 (pager)
U.C. Davis cckweiss@pager.ucdavis.edu (text pager)
Davis, CA 95616 http://dcas.ucdavis.edu/kenhome.html
At 05:46 17/02/99 +1100, you wrote:> >Date: Mon, 15 Feb 1999 23:47:50 -0500 >From: "Guy Dallaire" <gdallaire@videotron.ca> >To: <samba@samba.org> >Subject: HELP NEEDED: Problems with Samba 1.9.18p10 + Solaris 2.5.1 + Win95[snip]>I have no problem seeing the shares from win 95 (OSR2+VREDIR update) >network neighborhood. When I connect a drive, I can see the directories >but the names are not in the correct case, for example, UNIX BII >directory becomes Bii under windows. I could live with that.[snip]>I tried all sorts of upper/lower, preserve, case combinations in >smb.conf, nothing seems to work. I tried with debug level =3D 3 and I >noticed a lot of "Error file not found, line=3D..." in the samba log.[snip] You definitely have case conversion problems. W95 preserves case but is case blind. However, because M$ likes the screen to look pretty a filename which is all uppercase is displayed with the first letter uppercase and everything else lowercase in Explorer and other W95 apps. THe command line (DOS) interface tells the truth, though. You need preserve case = yes case sensitive = no If you try to force names to upper or lower case in the Unix filesystem this will cause all sorts of grief with W95 - you get the sort of bizarre errors you're reporting. If you have the Samba tarball, take a look at Andrew Tridgell's smb.conf file from his home Linux machine - if anybody knows how to configure Samba properly, it has to be him. It will be in examples/tridge or some such location. Best regards, Paul Paul Sherwin Consulting 22 Monmouth Road, Oxford OX1 4TD, UK Phone +44 (0)1865 721438 Fax +44 (0)1865 434331 Pager +44 (0)7666 797228
On 17 Feb 99, at 5:51, samba@samba.org wrote:> I'm modifying the files through my unix a/c and displaying them on > my pc via samba with ghostview. I had a look at the faqs which told > me that this wasn't a very good idea. However, it would make my life > a bit easier if I could do it.Sean, We are doing exactly the same thing (Ghostview with Unix created files), and I asked an almost identical question a couple of months ago. The 'problem' is oplocks. Samba 2.x uses oplocks by default which assumes that you access your files through Windows clients ONLY. If you are 'sharing' files between Unix and Windows, then you have to disable oplocks. This can be done by either disabling oplocks for the entire share ("oplocks = no") or by vetoing oplocks on that specific file type within the share ("veto oplock files = *.ps|*.eps"). Once you get rid of oplocks, all should be OK (albeit a bit slower). HTH. Cheers, Duncan Kinnear, McCarthy and Associates, Email: duncan@McCarthy.co.nz PO Box 764, McLean Towers, Phone: +64 6 834 3360 Shakespeare Road, Napier, New Zealand. Fax: +64 6 834 3369 ------------------------------------------------------------------------------- Providing Integrated Software to the Meat Processing Industry for over 10 years
System: Solaris 2.5.1 x86
Samba: 1.9.16p7
PC: Win95
Network:
---------------------+-------------+----- Ethernet
Solaris PC
---+---- -----
PPP -> |
---------
|Win95|
---------
IP Numbers: LAN 192.9.200.0/24
PPP 192.9.200.97
Solaris 192.9.200.44/24
- I have a PC dialing into a statically defined(permanent IP address)
interface.
- This interface is proxy arped so that when the PC is dialed into the
Solaris machine it can see all of the IP addresses on the ethernet.
- When connected the Dial-in PC can ping via name by making DNS
request via the Soalris machine
- The dialIn PC can mount shares and printers via the mapping feature
in Win95
THE PROBLEM
-----------------------
When the PC dials in it requests the user to logon to the Network. The
proper NY logon information and workgroup information is in the PC. The
proper authentication information is entered(works on the ethernet) and
the response is that there is no domain server available. However, the
PC is PPP'd via the Domain Server !?!?!?
So, I spent the last 6hrs reading the archives and found a post that stated
that it is a broadcast issue which makes sense. So snoop tells me that
the PC 192.9.200.97 makes 6-7 broadcast requests to the 192.9.200.255
address which can be seen on the ethernet. There is never a response.
I have tried playing with the broadcast address and route as per a few
suggestions
in the archives, without luck.
I really need to solve this since the requirement is to provide Samba resources
via a logon script.
Many thanks in advance, and I will post a note with detailed resolution
when found.
CC