From: gtaylor@tnetconsulting.net (Grant Taylor)
Subject: [TUHS] Difference in purpose of /var/spool vs /var/lib
Date: Thu, 14 Dec 2017 16:00:32 -0700 [thread overview]
Message-ID: <81c54c6f-2efb-48e7-c5ee-afd1297323ff@spamtrap.tnetconsulting.net> (raw)
Can anyone enlighten me on the effective difference in the use of
/var/spool vs /var/lib?
It's my understanding that spools are for files that are in transit.
Effectively like packages moving through a shipping depo or people
waiting in line. I.e. they come in, they hang around for a while, and
then they leave.
I'm of the opinion that files in /var/lib should stick around longer and
are not nearly as dynamic (if at all, save for code updates).
As sure as I type this, I can't think of a reason library files would go
under /var vs a different */lib directory.
Does it make any difference if the files are actually executed and / or
consumed on the system?
I don't consider the POP3 / IMAP / NNTP server to be processing files
when people access messages / articles (read: files) via the respective
protocols.
Back story: I'm considering writing something that will download a file
every day and process the last day's / week's / month's file(s) to
generate output which is itself stored elsewhere. - I feel like these
files should live in the /var/spool/<bla> subdirectory.
--
Grant. . . .
unix || die
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3982 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171214/2a1f09df/attachment.bin>
next reply other threads:[~2017-12-14 23:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 23:00 Grant Taylor [this message]
2017-12-14 23:38 ` Arthur Krewat
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=81c54c6f-2efb-48e7-c5ee-afd1297323ff@spamtrap.tnetconsulting.net \
--to=gtaylor@tnetconsulting.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).