Thanks, I'm aware of the linux file system hierarchy.
The file where this output is piped is not in /tmp so it can be preserved
across reboots and not in /var/tmp as it's on a per-user basis.It's in a
per-user directory that is cleaned out nightly of files older than X days.
It seems to me that the problem is checkrestart can't distinguish between an
output file, which should not require a restart,and a changed library, which
would. thanks,--jack
From: Axel Beckert <a...@debian.org>
To: js <jsh...@yahoo.com>; 864...@bugs.debian.org
Sent: Tuesday, June 13, 2017 7:47 PM
Subject: Re: Bug#864749: debian-goodies: checkrestart false positives due to
piping process output to tmp file
Control: tag -1 + wontfix
Hi,
js wrote:
> I start X from a console with roughly this command:
> startx > /usr1/ME/.remove/junk.X 2>&1
In the subject, you said something about "piping process output to tmp
file", but this path you're using is not a common path for temporary
files, hence checkrestart can't recognize that you consider this to
be a temporary file.
In contrary, /usr1 is very similar to /usr which is cleary _no_
directory where tempfiles should be. Please see the Filesystem
Hierachy Standard at
https://www.debian.org/doc/packaging-manuals/fhs/fhs-2.3.html for how
directories are and should be used on Debian.
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
