snexpire,v0.3.8(8)
β¨ snexpire β¨
okay bestie, welcome to the snexpire page from the System Manager's Manual β it's section 8, it's version v0.3.8, and it's here to help you clean out your news spool. let's get into it π
π NAME π
snexpire β expire news under the sn system.
π¦ SYNOPSIS π¦
snexpire [-v] [-exp] newsgroup [[-exp] newsgroup]...
π DESCRIPTION π
so snexpire expires news in the sn news system, and it does it one article file at a time β and just so you know, one article file is =10 articles by compile-time default. iconic behaviour tbh.
and here's the cute part: snexpire always leaves behind at least one article file β¨ so that newly entered articles get numbers that don't overlap previously used numbers. no number collisions, no chaos, we love a tidy queen.
but β and this is the exception, so listen up π β if the expiration age is set to 0, then even this last file will be expired, and subsequent article numbers will start from the beginning. lowkey a glow-up reset, highkey a whole new era.
β οΈ heads up bestie: you will need to berootor own/var/spool/snto runsnexpire. no root, no slay. π
πΈ OPTIONS πΈ
-vβ outputs a line for each article expired. and the format of this line? literally the same as forsnscan. so if you knowsnscan, you already know. iykyk π«Ά
π ARGUMENTS π
snexpire expires all newsgroups named on the command line. all of them. every single one. periodt π
each newsgroup may be preceded by -exp to control the expiration age. and exp is of the form #[hdwmy] β so that's a # (a number, bestie) followed by one of these characters:
hβ hoursdβ dayswβ weeksmβ monthsyβ years
the default for -exp is a compile-time fixed. so if you don't say anything, it's already decided for you.
and here's the thing that gets people: each [-exp] applies to the next newsgroup only. any newsgroups after that one get default treatment unless overridden by another [-exp]. so it's one -exp per newsgroup, no sharing, no passing it down the line. it's giving "one for you, not for everyone else" π
π§ FILES MODIFIED π§
these are the files that get touched:
/var/spool/sn/newsgroup/.times/var/spool/sn/newsgroup/[0123456789]*/var/spool/sn/{.chain,.table}
β ENVIRONMENT VARIABLES β
SNROOTβ if this is set and is not empty, the value is used in place of/var/spool/sn, the default news spool directory. so basically you can relocate the whole vibe. π¦
π FILES π
/var/spool/sn/newsgroup/.expireβ if this exists, its contents are taken to beexpif not overridden by-expon the command line. so it's the fallback bestie, the backup plan, the second option β¨
π N.B. β shoutout to Harold Tay for writing this one π«Ά
and that's the whole page, bestie!! π this was snexpire version v0.3.8, from section 8 of the System Manager's Manual, brought to you by Harold Tay β go expire some news, stay root, and don't forget your -exp only applies to the next newsgroup. mwah πβ¨πΈ
π¦ where this page comes from
- debian bookworm: sn 0.3.8-12
- ubuntu jammy: sn 0.3.8-12
- ubuntu noble: sn 0.3.8-12
- ubuntu resolute: sn 0.3.8-12
- ubuntu stonking: sn 0.3.8-12
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms