similar to: Installation of 2.0.2 on HPUX 10.2 - configure giving error

> From: Gary Stainburn <gary.stainburn@ringways.co.uk> > To: "Samba Mailing List (E-mail)" <samba@samba.anu.edu.au> > Subject: smbtar multiple machines > Message-ID: <01BDDD6E.ABFF0580@garys.computer.leeds> > > Hi all, > > I'm just looking at using smbtar to backup the Win95 PC's on my network, and would like usability ideas please. >

Hi everybody, I've never posted here before but I seem to be having a similar problem to what Tim Rice had in July, namely when running the configure script I get the following: configure: error: *** zlib missing - please install first or check config.log *** However, I have definitely installed zlib (see below): dngwks1:/tmp/openssh-3.0p1 # swlist # Initializing... # Contacting target

Hi, i tried to build Samba 2.2.4 under HPUX 10.20, but configure generated a Makfile with systax errors. make Make: line 664: syntax error. Stop. Makefile Line 664 shows: : $(WINBIND_NSS_PICOBJS) there should be something before the : configure said: checking whether to build winbind... no, unsupported on hpux10.20 is there a woraround, or can somebody tell me whats before the : Roland

Dear developers, The HPUX 10.20 trusted system hack doesn't work yet as intended. I have adapted the auth-passwd.c file to make it work. Please find a context diff file attached to this file. This diff is against the latest OpenSSH 2.2.0p1 released Sept 2, 2000. Also on HPUX 10.20, xauth is not found at the standard location. Perhaps this standard location could be changed automagically

While running configure on samba2.2.4 source on an HP-UX 10.20 OS, I get the following: checking configure summary... ERROR: No locking available. Running Samba would be unsafe configure: error: summary failure. Aborting config What exactly does "No locking available" mean, and is there a workaround? I'm currently running version 1.9.15p8 on the same OS. TIA! Ed Rodgers

Has anyone noticed that there appears to be a few problems with regards to Samba and in particular the usage of smbclient, which can do one of the following : 1) Complete & udder death of the NT networking subsystem (which requires a reboot to cure) 2) smbclient appears to lose its connection with the host being contacted and eventually needs to be killed. I'm not too sure how

I am trying to install Samba-2.2.3a on HPUX 10.2. I have downloaded the tar file from the web and placed it in my /tmp directory on my Unix server but when I try to install it using SAM I get message saying there is an I/O error on the file. Any suggestions? I am very very new to all this!

Hi Folks, I want to use samba and amanda to backup NT/win file system. I downloaded the latest version of Samba and trying to install on bsdi4.0 and it complains that the OS is a "trapdoor" OS and will not work propperly. I installed it anyway and I can connect to NT no problem but when I connect it back to the unix box, it complains about "Bad password - name/password in a Tree

Hello. I'm trying to use smbtar/smbclient (2.0.3) to copy an NTFS share on an NT Server, onto a Solaris 2.5 system. The NTFS partition is 10Gb. At the 2Gb mark, the tar stops. No errors, the file just stops. The process (smbtar) returns. Is this a problem with Solaris 2.5 ? I believe it is, and if I upgrade to 2.6, I can create larger tar files. However, does anyone know if

Hi. My friend has a problem that smbtar cannot recognize space character in specified filenames. He tried to execute following command line to back file "long file name" up: $ smbtar -s SERVER -p PASSWORD -x SHARE -u username -t /tmp/backup.tar \ "long file name" but smbtar tried to include three files as 'long', 'file' and 'name'. :-( Here is the

Compilation of openssh-3.6.1p2 on hpux-10.20 stops with .. (cd openbsd-compat && make) gcc -O2 -mpa-risc-2-0 -Wall -Wpointer-arith -Wno-uninitialized -I. -I.. -I. -I./.. -I/opt/openssl/include -I ./INCLUDES -D_HPUX_SOURCE -D_XOPEN_SOURCE -D_XOPEN_SOURCE_EXTENDED=1 -DHAVE_CONFIG_H -c bsd-arc4random.c In file included from ../openbsd-compat/openbsd-compat.h:35, from

Hello, I''m using kernel 3.1.0 and I have both / and /home as btrfs. I used suspend to ram quite often and never had a problem, but yesterday I''ve suspended to get into a plane and when I resumed my /home was all about input/output errors. Reboot did not help either. My root (/) did not suffer any problems. Today I''ve upgraded btrfs-progs to latest GIT and tried scrub

Phillip.Link@alcatel.fr wrote: > The problem > ----------- > I've been trying to install the latest samba distrib (2.0.5a) on a hpux > 10.20 machine, but the connection times out, apparently because of > shared memory access. > > Trying to make an smbclient connection (or using the windows nt explorer > to connect generates the following log.smb (smbd launched as smbd

tl;dr version: 3.0 produces “bio too big” dmesg entries and silently corrupts data in “meta-raid1/data-single” configurations on disks with different max_hw_sectors, where 2.6.38 worked fine. tl;dr side-issue: on-line removal of partitions holding “single” data attempts to create raid0 (rather than single) block groups. If it can''t get enough room for raid0 over all remaining disks, it

Mrs, I´m a Brazilian and i don´t speak english very well, but i need try , ok . I need your help. Well, i want install the samba 2.0.7 in HP-UX 10.20. The install process is not completely ok, but install. This is the message in the install process : _______________________________________ /var/tmp/AAAa23547/catalog/samba/samba-ROOT/configure[101]: Syntax error at line 129 :

Ronny Blomme <Ronny.Blomme@elis.rug.ac.be> writes: > The default configuration for smbclient in samba-1.9.18p8 is to send > verbose output to stdout. The output sent to tape is a mix of this > verbose output and the tar-file => corrupt tar file on tape The attached patch for SAMBA fixes this problem, preventing log messages from being printed to stdout if the tar-file is

At the bottom is what I got returned from AMANDA 2.3.0.5 after patching Samba 1.9.16p11 to give estimates. Any idea what I might not have done yet? My disklist reads: shokk \\thor\depot nocomp-user-gnutar To connect successfully to that server with smbclient, I have to do this, giving the same password that I now have in /etc/amandapass: smbclient \\\\THOR\\DEPOT -U BACKUP Also, the

If I do this on a Solaris 8, x86: tar xzf samba-2.0.7.tar.gz cd samba-2.0.7 mkdir OBJ/somedir cd OBJ/somedir ../../configure --prefix=/usr/someplace and then: make it doesn't mkdir "bin" for me, making it compile all the way until it is about to link bin/smbd. The linker gives me a message about not being able to find "bin/smbd" which is kind of misleading. 8-( Anyway,

We've been having problems using SMBTAR to back up some of our PCs. It seems that the tar format used by SMBCLIENT only supports a 100 character path name. Some of the new Microsoft Software generates longer file names. This causes an error when you attempt to write these files out to the tar device. I have developed a patch that will cause SMBCLIENT to write these files in USTAR format (an

When I try to compile the 1.9.18p10 samba package, I get following error: Maybe you guys help me? ---snip--- michelle:/usr/local/samba-1.9.18p10/source# make Using CFLAGS = -O -DSMBLOGFILE="/usr/local/samba/var/log.smb" -DNMBLOGFILE="/usr/local/samba/var/log.nmb" -D CONFIGFILE="/usr/local/samba/lib/smb.conf" -DLMHOSTSFILE="/usr/local/samba/lib/lmhosts"