Xref: utzoo comp.unix.microport:2959 comp.unix.questions:12139 unix-pc.general:2426
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!nrl-cmf!ukma!tut.cis.ohio-state.edu!osu-cis!att!cbnewsl!raj
From: raj@cbnewsl.ATT.COM (Richard A. Johnson)
Newsgroups: comp.unix.microport,comp.unix.questions,unix-pc.general
Subject: Re: ct on SysV386 3.0Ue
Summary: I used to use ct
Message-ID: <229@cbnewsl.ATT.COM>
Date: 9 Mar 89 18:41:03 GMT
References: <584@pgthor.UUCP> <7475@killer.DALLAS.TX.US> <4616@cbnews.ATT.COM>
Organization: AT&T Bell Laboratories
Lines: 27


I used to use ct to call me at home when I had mail.  I did this
via a cron job that ran every hour from 6PM to 10PM weekdays, and
10 AM to 10PM on weekends.  It checked for mail, and if there was
any, it invoked ct to the computer line in my house.  If I was home
and the data line rang, I'd turn on my terminal and get a login:
prompt.

I had to stop this when I started getting a lot of junk mail
from root and uucp.  Also it was driving my wife crazy whenever
it rang and I wasn't home - she didn't want to login so she would
let it ring (and ring and ring - do you know how persistent the
uucp dial routine is?).

Another thing that has happened since then is that AT&T has decided
that ct is a security risk and we should not have it enabled on
our machines.  :-(

To get back to the original question, yes, ct does work on unix
machines - I had it working on a VAX running BSD, and a 3B2 running
SVR2 and SVR3.

Rich Johnson
AT&T Bell Laboratories
Whippany, NJ
(201) 386-7345
att!video!raj