Sponsored Content
Full Discussion: Usenet is dead
The Lounge What is on Your Mind? Usenet is dead Post 302444578 by Action on Thursday 12th of August 2010 07:12:59 AM
Old 08-12-2010
cjcox, which servers are you using? Are they commercial or free? In those groups you follow, how active are users, how many messages in what time? On the servers i had a look at in many groups there was only one post in each of them. When getting news from there, programs often refuse to accept post because those posts are too old - like from year 2002, for example. Those servers look like abandoned, dead, with no activity at all.
 

7 More Discussions You Might Find Interesting

1. Solaris

Dead SUN

My SUN V210 refuses to fully boot up. We had a power outage (ie. someone tripped the cord) and thereafter the Sun will not come up, and the OS is not starting. The LED on the front is not lit. Monitor gets no feed, so I plugged in via the management port. The system comes up to: Trap 3e. and... (7 Replies)
Discussion started by: ireeneek
7 Replies

2. UNIX for Dummies Questions & Answers

dead.letter

HI, I am pretty new to Unix...but here is 1 serious problem...atleast for me..:-) now..the dead.letter file in /var/tmp has been growin continuously..n i dont know why..I ve even killed the sendmail process..but the dead.letter file keeps on increasin..Can anyone tell me where do I start... (6 Replies)
Discussion started by: unisam
6 Replies

3. Linux

Kinda OT: USENET Linux Groups

First, Please feel free to move or delete this thread if you do not feel it's appropriate. I used to be a regular user of Linux USENET groups such as alt.linux, alt.os.linux, and others. I haven't used the said groups for a couple of months now, but imagine my HORROR when I thought I'd drop by... (2 Replies)
Discussion started by: zazzybob
2 Replies

4. Answers to Frequently Asked Questions

USENET Unix FAQS

I have been working on another faq thread sites recommended by users and these Usenet FAQs really belong there. But I decided to give them their own thread and link in each faq. This overflowed the 10000 character limit per post so I had to break it into two posts. I reread all of the faqs as... (1 Reply)
Discussion started by: Perderabo
1 Replies

5. UNIX for Advanced & Expert Users

Dead pseudo-ttys

We are having a problem on an AIX 4.3 system, whereby users somehow exit the system in a way such that their process continues to run. In the who listing, the user may or may not be listed. Processes are still listed in ps, and are still assigned to the pseudo-tty. Processes continue to... (1 Reply)
Discussion started by: markat2k
1 Replies

6. Shell Programming and Scripting

what is dead.letter ??

Hi all can you please help me what is dead.letter file ? when it is created ? for the first time i have seen this file getting created in my current directory? I am using SunOs. Any IDEA ?? (2 Replies)
Discussion started by: jambesh
2 Replies

7. Shell Programming and Scripting

sed is dead

Hello everybody, I'm new to bash scripting (and scripting in general) but I'm making decent progress in the hands-on solutions I need... I've encountered a problem that seemed very simple to me at first, but had me going on for hours. Maybe you can help me. Say I have an input text file like... (2 Replies)
Discussion started by: origamisven
2 Replies
NEWS.DAILY(8)						      System Manager's Manual						     NEWS.DAILY(8)

NAME
news.daily - do regular Usenet system administration SYNOPSIS
news.daily [ keyword... ] DESCRIPTION
News.daily performs a number of important Usenet administrative functions. This includes producing a status report, removing old news articles, processing log files, rotating the archived log files, renumbering the active file, removing any old socket files found in the ``firewall'' directory, and collecting the output. This program should be run under the news administrator's id, not as root. By default, news.daily performs all of its functions and mails the output to the news administrator, usenet. By specifying ``keywords'' on the command line, it is possible to modify the functions performed, as well as change the arguments given to expire(8) and expireover(8). News.daily should be run once a day, typically out of cron(8). It may be run more often, but such invocations should at least use the ``notdaily'' keyword to prevent the log files from being processed and rotated too fast. The shlock(1) program is used to prevent simultaneous executions. KEYWORDS
The following keywords may be used: delayrm This uses the ``-z'' flag when invoking expire and expireover. The names of articles to be removed are written to a temporary file, and then removed after expiration by calling expirerm(8). expctl=path Specify the file to use as the expire.ctl(5) file for expire. expdir=path By default, expire builds the new history(5) file and database in the same directory as the current files. Using this keyword spec- ifies a different local to build the new files (by passing the ''-d'' flag to expire), which will then be moved to the right loca- tion when finished. nostat This keyword disables the status report generated by innstat (see newslog(8)). Without this keyword, the status report is the first function performed, just prior to obtaining the news.daily lock. notdaily By default news.daily expects to be run only once a day. Use this keyword any extra times news.daily is run in the day and the nor- mal logfile processing (and rotation) will not be done. noexpire By default, expire is invoked to remove old news articles. Using this keyword disables this function. noexplog Expire normally appends information to /var/log/news/expire.log (see newslog(5)). Using this keyword causes the expire output to be handled as part of news.daily's output. It has no effect if the ``noexpire'' keyword is used. flags='expire args' By default, expire is invoked with the an argument of ``-v1''. Using this keyword changes the arguments to those specified. Be careful to use quotes if multiple arguments are needed. This keyword has no effect if the ``noexpire'' keyword is used. nologs After expiration, scanlogs(8) is invoked to process the log files. Using this keyword disables all log processing functions. norotate By default, log processing includes rotating and cleaning out log files. Using this keyword disables the rotating and cleaning aspect of the log processing: the logs files are only scanned for information and no contents are altered. This keyword has no effect if the ``nologs'' keyword is used. The ``norotate'' keyword is passed on to scanlogs if it is invoked. norenumber This keyword disables the ctlinnd(8) renumber operation. Normally, the low-water mark for all newsgroups (see active(5)) is reset. norm By default, any socket ctlinnd socket that has not been modified for two days will be removed. Using this keyword disables this function. nomail News.daily normally sends a mail message containing the results to the administrator. Using this keyword causes this message to be sent to stdout and stderr instead. Normally, all utilities invoked by the script have their stdout and stderr redirected into a file. If the file is empty, no message is sent. expireover The expireover program is called after expiration to purge the overview databases. expireoverflags='expireover args' If the ``expireover'' keyword is used, this keyword may be used to specify the flags to be passed to expireover. If the ``delayrm'' keyword is used, then the default value is ``-z'' and the list of deleted files; otherwise, the default value is ``-s''. /full/path The program specified by the given path is executed just before any expiration is done. A typical use is to specify an alternate expiration program and use the ``noexpire'' keyword. Multiple programs may be specified; they will be invoked in order. HISTORY
News.daily and this manual page written by Landon Curt Noll <chongo@toad.com> and Rich $alz <rsalz@uunet.uu.net>. This is revision 1.11, dated 1996/12/10. SEE ALSO
active(5), ctlinnd(8), expire(8), fastrm(8), newslog(5), newslog(8), innwatch.ctl(5), shlock(1). NEWS.DAILY(8)
All times are GMT -4. The time now is 05:28 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy