<quote who="Gavin Henry">
> <quote who="Gavin Henry">
>> <quote who="Paul Bijnens">
>>> On 2006-08-08 16:17, Gavin Henry wrote:
>>>>
>>>> Currently trying to compile 2.5.0p2 with:
>>>>
>>>> ./configure --with-user=amanda --with-group=disk --with-ssh-security
>>>> --with-config=Suretec --with-changer-device=/dev/sg2
>>>> --with-tape-device=/dev/nst0
>>>>
>>>> But configure just sits there at:
>>>>
>>>> checking for smbclient... /usr/bin/smbclient
>>>>
>>>> Same when adding --with-smbclient=/usr/bin/smbclient
>>>
>>>
>>> If you do not need smbclient support, then you can configure
>>> with  "--without-smbclient"  and work around this problem.
>>
>> I have tried that, and with --with-smbclient=no.
>>
>> I've been going through configure.in to see what the probs are.
>>
>>>
>>> If you do need it...  then try to investigate what is blocking.
>>> It seems like "configure" is hanging in one of the next steps.
>>>
>>> Configure tries to find out what version of smbclient you have
>>> by running the command:
>>>
>>> smbclient '\\not.a.host.name\notashare' -U nosuchuser -N -Tx /dev/null
>>
>> Looks like it's this. It just hangs.
>>
>
> Must be smbclient, as it is taking forever, even when I jsut run:
>
> smblcient
>
> with no options.
>
> Forget it, will debug smbclient. Nothing wrong with Amanda.
>
> Thanks all.

strace smbclient -d 5

show it sitting at:

futex(0x2aaaabdf2dc0, FUTEX_WAIT, 2, NULL

Hmm.

>> I just setup 2 clients on Fedora Core 5 with 2.5.0p2, and they both are
>> fine.
>>
>> The server is on a SUSE 9.3 x86_64 box, that has (Is a Samba PDC too):
>>
>> free -m
>>              total       used       free     shared    buffers
>> cached
>> Mem:          3961        296       3665          0         48
>> 154
>> -/+ buffers/cache:         93       3868
>> Swap:         2070          0       2070
>>
>> uname -a
>> Linux nas1 2.6.14.2-smp #2 SMP Thu Nov 17 15:31:40 GMT 2005 x86_64
>> x86_64
>> x86_64 GNU/Linux
>>
>> df -h
>> Filesystem            Size  Used Avail Use% Mounted on
>> /dev/sda1              73G  6.0G   67G   9% /
>> tmpfs                 2.0G     0  2.0G   0% /dev/shm
>> /dev/sdb              6.9T  263G  6.6T   4% /storage
>>
>> lsscsi
>> [0:0:0:0]    disk    ATA      HTS541080G9SA00  MB4O  /dev/sda
>> [4:0:1:0]    tape    CERTANCE ULTRIUM 2        1775  /dev/st0
>> [4:0:1:1]    mediumx QUANTUM  UHDL             000E  -
>> [6:0:0:0]    disk    Areca    ARC-1160-VOL#00  R001  /dev/sdb
>>
>>>
>>> What happens if you run that manually?
>>
>> Hangs
>>
>>> The output of that step does not appear on screen however, so it could
>>> be that configure is actually hanging on the step after that.
>>
>> I think it's smbclient that is the problem.
>>
>>>
>>> The next step is finding out where the "gzip" program lives.
>>> Is does that by looking in several directories.
>>> If one of those directories happens to be mounted on a non-responsive
>>> NFS-server, you hang here too.
>>>
>>> The list of directories is:
>>> /bin:/usr/bin:/sbin:/usr/sbin:/usr/ucb:/usr/bsd:/etc:/usr/etc
>>> /usr/local/sbin:/usr/local/bin:/usr/ccs/bin
>>> and the value of $PATH from the user that runs configure.
>>>
>>> Anything strange when trying "test -e /bin/gzip"?  (Try that for
>>> all the above dirs)
>>
>> Nope, looks fine.
>>
>>>
>>>
>>> --
>>> Paul Bijnens, xplanation Technology Services        Tel  +32 16 397.511
>>> Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM    Fax  +32 16 397.512
>>> http://www.xplanation.com/          email:  [EMAIL PROTECTED]
>>> ***********************************************************************
>>> * I think I've got the hang of it now:  exit, ^D, ^C, ^\, ^Z, ^Q, ^^, *
>>> * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
>>> * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt,  abort,  hangup, *
>>> * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e,  kill -1 $$,  shutdown, *
>>> * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
>>> * ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm out          *
>>> ***********************************************************************
>>>
>>>
>>
>>
>
>

Reply via email to