Bug 256238 - periodic: remove obsolete news.expire
Summary: periodic: remove obsolete news.expire
Status: In Progress
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: 13.0-STABLE
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-bugs (Nobody)
Depends on:
Reported: 2021-05-29 10:00 UTC by Nils Johannsen
Modified: 2021-06-03 19:34 UTC (History)
2 users (show)

See Also:

git commit to remove news.expire from periodic (2.40 KB, patch)
2021-05-29 10:00 UTC, Nils Johannsen
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Nils Johannsen 2021-05-29 10:00:45 UTC
Created attachment 225351 [details]
git commit to remove news.expire from periodic

Together with the initial import of 386BSD 0.1 in 1993 the daily execution of /etc/news.expire was invented (see commit 1bf9d5d9518e).
This excution was maintained throughout and transferred accordingly to periodic in 1997, resulting in daily/330.news (see e.g. commit 28dce04d1975).

But as far as I see there was nevery any /etc/news.expire existing.
I also asked several people but none was able to explain me what news.expire could be or was at any time...
Comment 1 Thierry Thomas freebsd_committer 2021-05-30 09:21:06 UTC
I have a server running INN, and it does not run /etc/news.expire.
The crontab entry is:

0 3 * * * /usr/local/news/bin/news.daily expireover lowmark

and this does the job.
Comment 2 Andriy Gapon freebsd_committer 2021-05-30 18:13:57 UTC
Maybe in the past people thought that every BSD (or Unix) machine would run a news (as in NNTP) server. E.g., a small repertoire of syslog facilities includes news as well.
But I think that we never had a news server in the base.
And I expect that all "third-party" news server have their own stuff for periodic tasks.

So, it should be fine to purge that periodic entry.
Comment 3 Robert Wing freebsd_committer 2021-06-03 19:34:37 UTC