Re: Tar, general, and amindexd questions
Hello,
I forgot to include I am running version 2.4.2p1 on all systems.
I am running amrecover on the amanda server to remove any networking
hardware issues.
On Thu, Apr 26, 2001 at 02:30:23PM -0700, Jason Brooks wrote:
Hello,
Thank you for responding to my message. this platform (redhat 7.0) uses
Xinetd. here's the configuration:
[streak : xinetd.d]$ cat amandaidx
# default: on
# this is for the amindexd program.
service amandaidx
{
socket_type = stream
protocol= tcp
wait= no
user= bv-amanda
groups = yes
server = /usr/local/libexec/amindexd
server_args = amindexd
}
Note that amindexd in the path. That says your inetd.conf or xinetd
config file is wrong. It's passing the program name (amindexd) as an
arg to the program, who is taking it as the config name to use.
Ok, I see (I think) how having my configuration as part of the
server_args line could have an effect, but what if I wish to
run amindexd for a different configuration such as Test, Periodic_full,
or Daily? Since I specify amrecover -C Daily on the command line, I
would expect the data stream from client to server to tell amindexd
what configuration to look for.
Thanks for your time...
--jason
--
~~~
Jason Brooks ~ (503) 641-3440 x1861
Direct ~ (503) 924-1861
System / Network Administrator
Wind River Systems
8905 SW Nimbus ~ Suite 255
Beaverton, Or 97008
--
~~~
Jason Brooks ~ (503) 641-3440 x1861
Direct ~ (503) 924-1861
System / Network Administrator
Wind River Systems
8905 SW Nimbus ~ Suite 255
Beaverton, Or 97008
Re: Tar, general, and amindexd questions
server_args = amindexd Ditch that line. None of the Amanda xinetd config files should have a server_args key/value. ... what if I wish to run amindexd for a different configuration such as Test, Periodic_full, or Daily? Since I specify amrecover -C Daily on the command line, I would expect the data stream from client to server to tell amindexd what configuration to look for. Right. It does. You did when you put -C Daily on the command line. If you want to run for Test, do -C Test. But amindexd looks at the command line first, and that's what triggers the error. If you don't give it the command line arg, then it comes from the data stream. I don't know why amindexd was written to look at it's command line (when not in a debugging mode). That might just be a goof. BTW, the -C on amrecover is optional and probably should not be there. --jason John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Tar, general, and amindexd questions
Hello, On Thu, Apr 26, 2001 at 05:53:13PM -0500, John R. Jackson wrote: server_args = amindexd Ditch that line. None of the Amanda xinetd config files should have a server_args key/value. That did it. it is working now. BTW, the -C on amrecover is optional and probably should not be there. Do you mean to say that the -C option shouldn't be optional? --jason -- ~~~ Jason Brooks ~ (503) 641-3440 x1861 Direct ~ (503) 924-1861 System / Network Administrator Wind River Systems 8905 SW Nimbus ~ Suite 255 Beaverton, Or 97008
Re: Tar, general, and amindexd questions
Do you mean to say that the -C option shouldn't be optional? I mean that every other Amanda command that takes a configuration as an option accepts it as the first argument and none of them use something like -C. So I changed amrecover so it acts like all the other commands, i.e. you can do this: amrecover Daily -s wherever.com -d /some/device ... The only reason I didn't take -C out altogether was backward compatibility (i.e. I didn't want to deal with all the what does 'C: unknown option' mean E-mail :-). Maybe I'll finally get rid of it in 2.5. --jason John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
