Isn't talk broken at the moment (talk-server-0.16-1mdk.i586.rpm)?
# cat /etc/xinetd.d/talk
XYý1??c7x{T¦bá·¡föï´?õãBçJÑ_Èså¥ÄUÂÀBe®M(ºSu)°K¥Dx¾.äSp¡!Ê÷~
cat /etc/xinetd.d/ntalk gives the same sort of garbage.
oh crap ...i think i must have broke it ..
i'll do it today.
"David M.
On Wed, 26 Jul 2000, Geoffrey Lee wrote:
Isn't talk broken at the moment (talk-server-0.16-1mdk.i586.rpm)?
# cat /etc/xinetd.d/talk
XYý1??c7x{T¦bá·¡föï´?õãBçJÑ_Èså¥ÄUÂÀBe®M(ºSu)°K¥Dx¾.äSp¡!Ê÷~
cat /etc/xinetd.d/ntalk gives the same sort of garbage.
oh crap ...i think i
Isn't talk broken at the moment (talk-server-0.16-1mdk.i586.rpm)?
# cat /etc/xinetd.d/talk
XYý1??c7x{T¦bá·¡föï´?õãBçJÑ_Èså¥ÄUÂÀBe®M(ºSu)°K¥Dx¾.äSp¡!Ê÷~
cat /etc/xinetd.d/ntalk gives the same sort of garbage.
"David M. Kufta" [EMAIL PROTECTED] wrote:
** Reply to message from "Andrew G.
** Reply to message from "Andrew G. Madrigallos"
[EMAIL PROTECTED] on Tue, 25 Jul 2000 09:21:46 +0800 (PHT)
Andrew if your are using bash for your shell you will need the command
mesg y to allow a user to recieve and reply to a talk request, provided
talk is being started in the inetd.conf file