root@csccat.UUCP (Jack Hudler) (10/21/87)
Hello!
Just patched up to 11 and curiously enough expire pukes out this
nasty message: (yes it's another on of those nasty expire bugs)
"Cannot open /usr/lib/news/history"
Well looking at the directory tells me there isn't a file called
'history' so I then proceed to look at expire#8 and see what changed.
Well the line of code in expire that created the file in the first
place got axed by patch9 leaving an xfopen in rebuild with no file.
Question: :-)
Has anybody else had this problem? My temporary fix was to just
touch /usr/lib/news/history and then run expire which would
run ok. Which leads to another question whats this file for
anyway!
Another thing that bugged me was the failure to mention that little
def called HP9K5 in ndir.h. cute. I have an HP9000, but I am curious
about what the K5 stands for?
Just a Have'n fun here!
Jack
uucp:{ihnp4|cbosgd}!killer!csccat!jack HP9000 Sys 5.22 with BSD Enhancements
ofcourse somebody will want to argue
over the BSD stuff wondering if its
really enhancing sys V.paul@devon.UUCP (Paul Sutcliffe Jr.) (11/03/87)
I recently installed patches 9, 10 and 11 in my news software. Since
that time, I have been getting the following error message from expire
during its nightly run (from cron):
expire: Unparsable date "31 Dec 69 23:59:59 GMT"
I get several of these each run. They are from the std{out,err} of
the cron process. At the same time, I get messages like these:
Nov 3 00:59 news expire: Unparsable date "31 Dec 69 23:59:59 GMT"
in LIBDIR/log and LIBDIR/errlog.
My guess is that since Un*x keeps its time in a long, with 0L
representing "1 Jan 70 00:00:00 GMT", that the above message comes
from trying to handle a "-1" value.
If this matters, I am running B-news 2.11 patchlevel 11 on a Tandy
Model 16; Tandy Xenix 3.1.2; with OSTYPE=v7 in the Makefile. I have
verified that the same problem exists at my news-neighbor (vu-vlsi) on
a Pyramid 90x; OSx 4.0; with news running in the BSD universe.
- paul
--
Paul Sutcliffe, Jr.
UUCP (smart): paul@devon.UUCP
UUCP (dumb): ...{rutgers,ihnp4,cbosgd}!bpa!vu-vlsi!devon!pauljohn@wa3wbu.UUCP (John Gayman) (12/13/87)
I have been running News 2.11 Patch #8 for about two months. Everythings
been working fine till last night. I received a message back from cron
stating that "expire" couldnt run. The message I received was:
expire: Cannot get NEWSGRP gr entry
Can anyone give me a hint as to the cause of this and better yet, what
would be the most preferred way to go about fixing it ? I have a fair
amount of disk space left so I doubt Ill run out in the next several
days. I appreciate any suggestions. Thanks
John
--
John Gayman, WA3WBU | UUCP: uunet!wa3wbu!john
1869 Valley Rd. | ARPA: wa3wbu!john@uunet.UU.NET
Marysville, PA 17053 | Packet: WA3WBU @ AK3P karl@mumble.cis.ohio-state.edu (Karl Kleinpaste) (12/15/87)
john@wa3wbu.UUCP writes:
I received a message back from cron
stating that "expire" couldnt run. The message I received was:
expire: Cannot get NEWSGRP gr entry
Can anyone give me a hint as to the cause of this and better yet, what
would be the most preferred way to go about fixing it ?
The software is complaining because it can't find the textual name of
the group which is supposed to own the news software. That is, if
it's "news," there is no "news" in /etc/group.
By the way, a general plug for updates: I heartily recommend 2.11
patchlevel 12. We've been running it on the SysV.3 3B2 that feeds
this department for about 2 weeks, and on our main news-serving system
for 5 days. Very stable. Very nice. Takes care of map updates in
comp.mail.maps nicely via the Supersedes: headers.
We haven't been daring enough yet to install #13 and #14...:-)
-=-
Karlmorris@dms.UUCP (Jim Morris) (09/14/88)
Can anyone tell me why I get the following error message fairly frequently:
expire: Unparsable date "31 Dec 69 23:59:59 GMT"
when expire runs.
I can fix it by using the -I option in expire, but I am curious as to
what is corrupting the dates on some news articles. Unfortunately there
appears no way of finding the offending news item or entry.
Any suggestions would be welcome.
Thanks.
--
Jim Morris. morris@dms.UUCP or weitek!dms!morris
Atari Games Corporation, Sycamore Drive, Milpitas CA 95035.
(Arcade Video Game Manufacturer, NOT Atari Corp. ST manufacturer).
Any opinions expressed are probably my own, and not those of Atari Games Corp.wytten@umn-cs.CS.UMN.EDU (Dale R. Wyttenbach) (10/18/88)
In article <542@dms.UUCP> morris@dms.UUCP (Jim Morris) writes: > >Can anyone tell me why I get the following error message fairly frequently: > > expire: Unparsable date "31 Dec 69 23:59:59 GMT" > >when expire runs. I have this problem, too, and I never saw a response to this posting. We recently went from a VAX 11/780 and 4.3 BSD to a Sequent S27 and DYNIX 3.0.12. I don't remember if I was having the '31 Dec 69' problem on the VAX. umn-cs is running 2.11 news, albeit sort of lamely right now. DYNIX is *based* on 4.2 BSD, but I doubt if I have everything defined correctly in the Makefile and include files. (This was my first news install, and I found the localize.sh script worthless, at least in my case) (I wanted to say something stronger about localize.sh, but I didn't want to offend anyone) How much has TMN-Netnews been tested? Could it be substituted for 2.11 without much affect on the end-user? Dale Wyttenbach {wytten,news}@umn-cs.cs.umn.edu ...rutgers!umn-cs!wytten
news@etive.ed.ac.uk (Network News) (10/20/88)
In article <542@dms.UUCP> morris@dms.UUCP (Jim Morris) writes:
%Can anyone tell me why I get the following error message fairly frequently:
% expire: Unparsable date "31 Dec 69 23:59:59 GMT"
%when expire runs.
On my machine if you pass the numerical date -1 to ctime it produces
this date string (date 0 on Unix is Jan 1 1970 00:00:00 GMT). I don't
know where the bug is though, or what the fix is.
Scott Larnachjec@nesac2.UUCP (John Carter ATLN SADM) (10/23/88)
In article <9617@umn-cs.CS.UMN.EDU>, wytten@umn-cs.CS.UMN.EDU (Dale R. Wyttenbach) writes: > In article <542@dms.UUCP> morris@dms.UUCP (Jim Morris) writes: ] ] ] ]Can anyone tell me why I get the following error message fairly frequently: ] ] ] ] expire: Unparsable date "31 Dec 69 23:59:59 GMT" ] ] ] ]when expire runs. ] ] I have this problem, too, and I never saw a response to this posting. ] ] We recently went from a VAX 11/780 and 4.3 BSD to a Sequent S27 and DYNIX ] 3.0.12. I don't remember if I was having the '31 Dec 69' problem on the ] VAX. ] ] umn-cs is running 2.11 news, albeit sort of lamely right now. ] {deletions} ] Dale Wyttenbach ] {wytten,news}@umn-cs.cs.umn.edu ] ...rutgers!umn-cs!wytten UNIX(tm) was 'born' 1/1/1970 - a date of 12/31/1969 23:59 says that the call to get the time returned a -1, and that the call does no error checks. Sounds like a bug in the time code - int/long, 16/32/64 bits, big-endian vs. little-endian, whatever else you can think of that might break what you should get as time_t. -- USnail: John Carter, AT&T, 401 W. Peachtree, FLOC 2932-6, Atlanta GA 30308 Video: ...att!nesac2!jec Voice: 404+581-6239 The machine belongs to the company. The opinions are mine.