similar to: Possible bug in 2.2.3a source/script/installbin.sh (with patch)

I remember seeing a patch here a long while back that I thought was going to be committed for making the install relocatable (i.e. allowing for a DESTDIR to be specified during a "make install"). I can't find it, and I'm not sure I am remembering correctly, anyway, so here is a shot at it. Tested both the install and uninstall, run as "make install

Hi, I would like to ask you to consider the attached patch for inclusion into the next samba release. The patch addresses the following three points: 1. 'make install' with VPATH fails at one point ( $(srcdir)/script/findsmb vs. script/findsmb ) 2. support for 'make DESTDIR=<somewhere> install' (e.g. to build a binary package) 3. support for 'configure

I am getting the following errors when compiling SAMBA 2.2.4 on HP-UX 11.00. Anyone have any ideas on what's causing the problem? Using FLAGS = -O -I./popt -Iinclude -I./include -I./ubiqx -I./smbwrapper -D_HPUX_SOURCE -D_POSIX_SOURCE -D_LARGEFILE64_SOURCE -D_ALIGNMENT_REQUIRED=1 -D_MAX_ALIGNMENT=4 -DLOGFILEBASE="/opt/samba/var" -DCONFIGFILE="/opt/samba/etc/smb.conf"

I am getting the following link errors when compiling SAMBA 2.2.4 on HP-UX 11.00. Anyone have any ideas on what's causing the problem? Using FLAGS = -O -I./popt -Iinclude -I./include -I./ubiqx -I./smbwrapper -D_HPUX_SOURCE -D_POSIX_SOURCE -D_LARGEFILE64_SOURCE -D_ALIGNMENT_REQUIRED=1 -D_MAX_ALIGNMENT=4 -DLOGFILEBASE="/opt/samba/var"

Hi, We (NetBSD) just received a bug report that smbclient's mput command usees find(1) with a non-standard option "-maxdepth". This was replaced with a simple call to ls(1). As I don't know how many of the patches from out Packages Collection were sent to you in the past, I'm simply sending you all our patches - please include any you like in future samba releases! BTW,

Hi out there, i intend to run multiple Instancies of Samba on a single, multi-homed, server, with each instance bound to a specific (logical) interface. If this works, it would be fine to me. Mainly for administrative Reasons. (You won't believe, but from time to time it becomes necessary to restart some services, but restarting the entire server is a real mess) Well here my

> Sorry, but in the first mail I forgot to attach the Makefile and I > forgot also to mention that I already tried the password handling in win95 > via the registry. > > De Boe Bart wrote: > > > Hello, > > > > I need to install Samba on a HP J210 HPUX 10.20. > > I downloaded and compiled version 1.9.18p10. > > > > Following problems are

The source for the samba components in MacOS X Server is located at: http://www.opensource.apple.com/tools/cvs ('samba' module) The latest vendor branch is samba2.2.1a. The main branch includes the following modifications (see diffs below).. 1) DirectoryService suport (encrypted authentication) 2) CFString usage (DOS code page <-> decomposed UTF8) 3) smbstatus -r (raw dump of user

I've run into a problem with samba and tdb reporting "too many connections" If I do a typical configure: ./configure --prefix=/usr/local/samba \ --localstatedir=/var/samba \ --with-lockdir=/var/samba/locks \ --with-configdir=/usr/local/samba/etc I see errors like the following in /var/samba/log.smbd: [2001/11/10 22:58:53, 0] tdb/tdbutil.c:tdb_log(342)

To whom it may concern: here are the diffs which I required to make the mentioned Makefile work. I maintain several platforms of samba servers, and thus use the VPATH option in the Makefile. I've been fixing installscripts.sh as well, so that `make install` works when run from my build directory. I'm assuming SAMBA v2.x will migrate to autoconf/configure and should fix these issues, but

You Guys/Gals just Flat out RULE !!!! -jason

Hello, In my log.winbind I'm getting several messages like this one: [2003/12/30 18:19:00, 0] nsswitch/winbindd.c:process_loop(725) process_loop: Invalid request size from pid 12913: 1304 bytes sent, should be 1568 This usually means that you are running old wbinfo, pam_winbind or libnss_winbind clients I suppose that the problem may be cause by old version of pam_winbind and

Hello, We have a samba file server running on Fedora Core 1. I have installed 3.0.11 from RPM package for Fedora. This release have some problems and I need to upgrade. Instead of usinf RPM, I'd like to build samba myself from the sourcecode. I already do that without problem but when installing binaries, lib and config files, it uses default installation directory (ie /usr/local/samba)

I've built an embedded version of samba 3.0.26b. I'm having a problem getting it started, though - it fails to start. A bit of tracing and I *think* it's failing to find secrets.tdb. strace is showing smbd dying after failing to find secrets.tdb - in the wrong place. I think the script below should take care of that, but for some reason it's looking for secrets\.tbd in the

Hello samba gurus I have used samba1.9.18.p4 since jan/1998. I have FreBSD 2.2.6 and samba1.9.18p4 worked just fine. I read in bugtraq that a new version of samba has been released and I thought in upgrade to samba1.9.18.p7 Well I did the same things that I did when I compiled samba1.9.18.p4 1.Edit the Makefile ( I edit the same lines as samba1.9.18.p4) 2.make 3.make installbin Everything

Hi All I've installed Samba 2.0.3 and coudn't put "unix passowrd sync" to work. I set: passwd program = /usr/bin/passwd %u passwd chat = *New*password:* %n\n *Re-enter*new*password:* %n\n*changed.* passwd chat debug = Yes unix password sync = Yes log level = 100 The password page says "The password for 'user' has been changed". In fact it has been

I've set up the following and can open a home share for me (sylveg). I've created a group on W2KADS and on OURSAMBALINUX called oadmin and added me as a member in both. I created a samba share called o_drive (see smb.conf below) w/ the linux dir /home/o_drive and valid users = %D+oadmnin. The /home dir is: drwxr-xr-x 2 root root 4096 2004-09-03 15:16 ftp/ drwx------ 2 root root

Hi All, I extended my AD schema (SFU 3.5) and migrated the users and groups from my NIS domain. The groups migrated from the NIS have the same GID like on the NIS. I added linux machines to my AD domain using windbind, and define on the smb.conf "idmap gid = 10000-20000". I logged in using my AD user account, and when I'm doing "id", I see that all the AD groups

The destination register and each of the source registers can be relatively addressed by some special "address registers": a0, a1, a2, a3. suppose a0 = 4, a1 = 2, the instruction add r[a0], r[a1], r7 equals to: r4 = r2 + r7 How should the instruction be defined in TableGen *.td file? If an opcode is defined for each variant (like X86InstrInfo.td) there will be eight opcodes

Having fought my PXE config and eventually getting it to work (had to comment out the group { } statments ? I now come across another issue I cannot resolve and would appreciate some help. in my /tftpboot/pxelinux.cfg/default file I have cause to use the APPEND statement to pass options to the kernel being used. Unfortunately this line has now become longer than 255 characters and appears to be