On Wed, Feb 19, 2020 at 09:08:07PM +, b...@0x1bi.net wrote:
> I've set my hostname to point to 127.0.0.1 and I still receive the
> same error. I tried with and without the domain information.
>
> Is there a log for talkd or inetd? I've attempted to use the -d
> flag for inetd however I
Thank you, Steve. I was able to get talk to work
by properly configuring /etc/resolve.conf as well
as the hosts file.
Ben Raskin.
On Wed, 19 Feb 2020 21:01:10 +0100
KatolaZ wrote:
> On Wed, Feb 19, 2020 at 07:13:48PM +, b...@0x1bi.net wrote:
> > > Do you have a correct entry with the machine hostname (full
> > > hostname(1) output) in /etc/hosts?
> >
> > I don't. What should the entry look like? Should the hostname
On Wed, 19 Feb 2020 15:48:00 + (UTC)
b...@0x1bi.net wrote:
> I verified the output of rcctl and inetd is running.
>
> Ben Raskin.
>
Hi Ben,
Here's what I did on my Void Linux computer to get talk working:
* Configured xinetd to work
* Make sure xinetd has an entry for talk[1]
* As my
>Appart from setting your address and host and domain names in /etc/hosts, do
>you
>have a "lookup file bind" line in /etc/resolv.conf ? If you don't, it defaults
>to "lookup bind file", so it will query DNS first, and then look into
>/etc/hosts. There is a possibility this too can confuse talk.
On 19.02.2020. 22:08, b...@0x1bi.net wrote:
I've set my hostname to point to 127.0.0.1 and I still receive the
same error. I tried with and without the domain information.
Is there a log for talkd or inetd? I've attempted to use the -d
flag for inetd however I receive no error messages or
I've set my hostname to point to 127.0.0.1 and I still receive the
same error. I tried with and without the domain information.
Is there a log for talkd or inetd? I've attempted to use the -d
flag for inetd however I receive no error messages or warnings.
Ben Raskin.
On Wed, Feb 19, 2020 at 07:13:48PM +, b...@0x1bi.net wrote:
> > Do you have a correct entry with the machine hostname (full hostname(1)
> > output) in /etc/hosts?
>
> I don't. What should the entry look like? Should the hostname point to
> 0.0.0.0?
It should point to 127.0.0.1
> Do you have a correct entry with the machine hostname (full hostname(1)
> output) in /etc/hosts?
I don't. What should the entry look like? Should the hostname point to
0.0.0.0?
Ben Raskin.
On Wed, Feb 19, 2020 at 06:25:56PM +, b...@0x1bi.net wrote:
> >Did you restart inetd after editing inetd.conf? It has to decide what
> >ports to listen on when it starts up, which means it isn't going to
> >notice edits.
>
> Yes, I restarted inetd. I still receive the 'Couldn't bind to
>Did you restart inetd after editing inetd.conf? It has to decide what
>ports to listen on when it starts up, which means it isn't going to
>notice edits.
Yes, I restarted inetd. I still receive the 'Couldn't bind to socket:
Can't assign requested address'
I'm not attempting to talk to another
On 2020-02-19 9:48, b...@0x1bi.net wrote:
I verified the output of rcctl and inetd is running.
Did you restart inetd after editing inetd.conf? It has to decide what
ports to listen on when it starts up, which means it isn't going to
notice edits.
--
Matthew Weigel
I verified the output of rcctl and inetd is running.
Ben Raskin.
On Wed, Feb 19, 2020 at 03:38:24PM +, b...@0x1bi.net wrote:
>
> Hello, everyone;
>
> I'm attempting to initiate a conversation via talk(1) however upon
> executing the command I receive the following error:
>
> talk: Couldn't bind to control socket: Can't assign requested address
>
> I've
Hello, everyone;
I'm attempting to initiate a conversation via talk(1) however upon
executing the command I receive the following error:
talk: Couldn't bind to control socket: Can't assign requested address
I've uncommented the line in /etc/inetd.conf which corresponds to the
talkd daemon,
15 matches
Mail list logo
