* [TUHS] Difference in purpose of /var/spool vs /var/lib
@ 2017-12-14 23:00 Grant Taylor
2017-12-14 23:38 ` Arthur Krewat
0 siblings, 1 reply; 2+ messages in thread
From: Grant Taylor @ 2017-12-14 23:00 UTC (permalink / 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>
^ permalink raw reply [flat|nested] 2+ messages in thread
* [TUHS] Difference in purpose of /var/spool vs /var/lib
2017-12-14 23:00 [TUHS] Difference in purpose of /var/spool vs /var/lib Grant Taylor
@ 2017-12-14 23:38 ` Arthur Krewat
0 siblings, 0 replies; 2+ messages in thread
From: Arthur Krewat @ 2017-12-14 23:38 UTC (permalink / raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1628 bytes --]
In my humble opinion, "spool" means files in transit. Run something
locally, it generates a file, it gets shipped somewhere (email, printer,
etc) and it's gone.
On Linux and Solaris (to a lesser extent), /var/lib seems to be
configuration files like samba's password database, and other "non
transient" files.
If you're storing files for long periods, /var/spool is not where you
want to do that. Again, IMHO.
On 12/14/2017 6:00 PM, Grant Taylor via TUHS wrote:
> 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.
>
>
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-12-14 23:38 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-12-14 23:00 [TUHS] Difference in purpose of /var/spool vs /var/lib Grant Taylor
2017-12-14 23:38 ` Arthur Krewat
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).