home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!darwin.sura.net!jvnc.net!netnews.upenn.edu!cs.widener.edu!dsinc!dsinc!not-for-mail
- From: syd@dsi.com (Syd Weinstein)
- Newsgroups: comp.mail.elm
- Subject: Re: newmail problem
- Message-ID: <1erqkpINN2ln@dsinc.dsi.com>
- Date: 23 Nov 92 23:48:41 GMT
- References: <1erf0oINNp8k@usenet.INS.CWRU.Edu> <1erfibINNpna@usenet.INS.CWRU.Edu>
- Reply-To: syd@DSI.COM
- Organization: Datacomp Systems, Inc., Huntingdon Valley, PA
- Lines: 21
- NNTP-Posting-Host: dsinc.dsi.com
-
- ce095@cleveland.Freenet.Edu (Jeffrey Scott Traigle) writes:
- >>I set the option during configuration to have newmail run in the
- >>background automatically. It isn't working however. I even try running
- >>it in the background explicitly, but it replies with "Done" after a
- >>second or two. What happened? It worked in earlier versions, I know.
- >A little correction in the behavior that I just discovered. If I run
- >newmail explicitly, it does spawn a newmail process that remains active
- >and works. In previous versions, this wasn't necessary with the flag
- >during configuration set to run newmail automatically.
-
- Newmail never ran automatically, it always had to be started at the command
- line (or via shell or login script.)
-
- The option just indicates whether newmail does the fork and runs in the background
- automatically, or stays in the foreground. This behavior has not changed since
- it was intruduced long ago in a version long since forgotten.
- --
- ========================================================================
- Sydney S. Weinstein, CDP, CCP Elm Coordinator - Current 2.4PL11
- Datacomp Systems, Inc. Projected 3.0 Release: ??? ?,1994
- syd@DSI.COM or dsinc!syd Voice: (215) 947-9900, FAX: (215) 938-0235
-