Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!swrinde!ucsd!ucbvax!ucdavis!csusac!
From: hoodr@syscube.csus.edu (Robert Hood)
Newsgroups: comp.sys.next
Subject: Re: Problems with at
Message-ID: <1990May2.171849.25401@csusac.csus.edu>
Date: 2 May 90 17:18:49 GMT
References: <9005020916.AA07742@.nextasy2.ece.wsu.edu.ece.wsu.edu.>
Reply-To: hoodr@csus.edu (Robert Hood)
Organization: California State University: Sacramento
Lines: 18

In article <9005020916.AA07742@.nextasy2.ece.wsu.edu.ece.wsu.edu.> schneidj@NEXTASY2.ECE.WSU.EDU (John B. Schneider) writes:
>If I issue the *at* command with the -m option I always get a message
>that the program exited abnormally with the following error:
>
>              Where are you?
>
>John Schneider

I had this same problem a few months ago.  I found that having the 'biff'
command in the .cshrc caused this problem (probably because is was trying
to decide which tty to send its messages to).  I moved 'biff' to my .login,
and I no longer get this message.

Hope this helps....

Robert Hood  --  California State University: Sacramento   (916) 278-7402
  INTERNET: hoodr@csus.edu <-- NeXT mail too!    BITNET: hoodr@CALSTATE
  UUCP: ...!ucdavis!csusac!hoodr