Compilation quirks (was: Problems with port ranges)
2005-09-19 20:10:25
Just out of curiosity...
Is this the right place to be asking questions about compilation? Or
should I be doing that on the dev list?
Also...
I noticed another quirk when compiling. If I put the following in my
config.site file, I get compilation errors:
NO_SERVER_MODE=true
However, if I use the command line option "--without-server", all is well.
I am trying to compile version 2.4.5 on FC3.
Cheers,
David
Hello!
I compiled both my client and server with the options:
--with-portrange=50000,50100 --with-udpportrange=512,520
However, when I run amdump, on my client machine, apparently it is
attempting to use a different port (see log file below).
Is there something I'm doing wrong?
Thank you!!
sendbackup: debug 1 pid 15670 ruid 510 euid 510: start at Mon Sep 19
18:04:32 20
05
/usr/local/libexec/sendbackup: version 2.4.5
parsed request as: program `DUMP'
disk `/tmp'
device `/tmp'
level 0
since 1970:1:1:0:0:0
options `|;bsd-auth;compress-fast;index;'
sendbackup: try_socksize: send buffer size is 65536
sendbackup: time 0.001: stream_server: waiting for connection:
0.0.0.0.35952
sendbackup: time 0.001: stream_server: waiting for connection:
0.0.0.0.35953
sendbackup: time 0.001: stream_server: waiting for connection:
0.0.0.0.35954
sendbackup: time 0.002: waiting for connect on 35952, then 35953, then
35954
sendbackup: time 29.999: stream_accept: timeout after 30 seconds
sendbackup: time 29.999: timeout on data port 35952
sendbackup: time 59.995: stream_accept: timeout after 30 seconds
sendbackup: time 59.995: timeout on mesg port 35953
sendbackup: time 89.990: stream_accept: timeout after 30 seconds
sendbackup: time 89.990: timeout on index port 35954
sendbackup: time 89.990: pid 15670 finish time Mon Sep 19 18:06:02 2005
|
|
|