On 4/8/2012 9:29 AM, gene heskett wrote:
> On Sunday, April 08, 2012 09:25:12 AM Mark Wendt (Contractor) did opine:
>
>
>> On 4/7/2012 12:34 PM, Mark Cason wrote:
>>
>>> On 04/07/2012 10:54 AM, gene heskett wrote:
>>>
>>>> You will recall I had to do something that blacklisted ipv6 in order
>>>> to get any network connection at all on the lathe box, but that
>>>> message has been expired now and I don't recall what it was that I
>>>> had to do to it now. Whatever it was, I suspect that now that I have
>>>> the correct version of inetd installed for amanda, that I could
>>>> probably undo that blacklist without harming the ipv4 networking
>>>> now.
>>>>
>>>>
>>> Here's the link again:
>>> http://www.webupd8.org/2010/05/how-to-disable-ipv6-in-ubuntu-1004.html
>>>
>> Gene,
>>
>> Also check the port in /etc/services and see if it's enabled for IPv4.
>> Should be either above or below the IPv6 port for amanda.
>>
>> Mark
>>
> Of the 3 machines live on my network right now, none of the services files
> contain anything to indicate the service is ipv4 or ipv6, and amanda is
> listed at 10080-10083 in all 3 lists.
>
> What SHOULD I be seeing in those files to differentiate the 2 ip versions?
>
> Thanks Mark.
>
> Cheers, Gene
>
Gene,
I meant to say either inetd.conf or xinetd.conf. In the /etc/services
file there should be a line similar to this for amanda with the correct
port number:
telnet 23/tcp
In the inetd.conf or xinetd.conf you may see a line similar to this:
telnet stream tcp nowait root /usr/sbin/telnetd telnetd -a
Depending how xinetd is set up, you may have the directory
/etc/xinetd.d, where the configuration files
for the services are at. In that case, you may need to create a file
called "amandaserver"
which includes statements similar to this:
# default: on
#
# description: Amanda services for Amanda server and client.
#
service amanda
{
disable = no
socket_type = stream
protocol = tcp
wait = no
user = amandabackup
group = disk
groups = yes
server = /usr/lib/amanda/amandad
server_args = -auth=bsdtcp amdump amindexd amidxtaped
}
If this is the case, you don't need an entry in the xinetd.conf file.
That file will source all the files in the xinetd.d directory.
Mark
------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users
