On 2020-04-28 Gerald Brandt wrote:

If it compiles and runs, and you just want it to start, can't you throw it into crontab with @start or @reboot (whichever one it is).

Nope, doesn't run even manually:

2:00am html/Eword/Live#/usr/sbin/in.talkd Socket operation on non-socketExit 1 2:00am html/Eword/Live#/usr/sbin/in.ntalkd Socket operation on non-socketExit 1

strace: getsockname(0, 0x7ffcb85f1820, [16]) = -1 ENOTSOCK (Socket operation on non-socket) write(2, "Socket operation on non-socket", 30Socketoperation on non-socket) = 30 exit_group(1) = ? +++ exited with 1 +++

From the man page there really are no options. -d debugging doesn't

give me any further info.

Looks like something is really busted in the way it listens on its socket. I checked and talk's usual 2 ports (whether "n" or not) aren't taken.

I was just wondering if maybe there was some weird config file or undocumented command line option I'm missing that someone knows about. It is a strangely optionless daemon.

Tim: I forgot to mention, I don't even need inter-machine support... I just want to run talk on one box between 2 people logged in to that 1 box.

But I do want something that has the nice split window paradigm that talk uses.

On 2020-04-29 03:41, athompso@athompso.net wrote:

Setenforce 0, maybe?

Also, utalk (https://utalk.ourproject.org/) has a peer-to-peer mode that doesn't require talkd/ntalkd. And it compiled under CentOS 8 so should work for you, too. (I can't even compile ntalk!)

-Adam

On 2020-04-29 Gilbert E. Detillieux wrote:

IIRC, all the in.*d daemons (and in.talkd in particular) were meant to be run through inetd, and not directly as a standalone daemon. They would expect stdin and stdout to be already connected to a socket on startup.

Thanks! That explains that... however, I was trying to run it through systemd (which has a .socket file for it) as well as xinetd (but I had to guess at a conf file for it because none are supplied anymore). Both barfed with errors.

On 2020-04-29 athompso@athompso.net wrote:

Setenforce 0, maybe?

Always!

Also, utalk (https://utalk.ourproject.org/) has a peer-to-peer mode that doesn't require talkd/ntalkd. And it compiled under CentOS 8 so should work for you, too. (I can't even compile ntalk!)

Thanks! I'll check that out... yes, something newer/better supported would seem to be the solution.