ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: Anton Midyukov <antohami@altlinux.org>
To: devel@lists.altlinux.org
Subject: Re: [devel] Должен ли /tmp очищаться при каждой загрузке
Date: Thu, 6 Nov 2025 10:21:09 +0300
Message-ID: <751d1592-8487-4e36-aab5-e8b59caf2fce@altlinux.org> (raw)
In-Reply-To: <de131fde-d0be-49ad-8da8-84a2075b1786@basealt.ru>

06.11.2025 10:06, Anton Farygin пишет:
> On 11/6/25 10:04, Sergey V Turchin wrote:
>> On Thursday, 6 November 2025 09:56:01 MSK Anton Midyukov wrote:
>>
>> [...]
>>> Должен ли /tmp очищаться при загрузке, когда он не на tmpfs?
>> Никогда никому не был должен. Существование stmpclean тому в доказательство.
>>
>> [...]
>>
> Да, то что tmp не очищается при загрузке - это фича а не ошибка.
> 
> Знаю людей, которые этой фичей пользуются.
> 

Немного нормативных документов:
https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch03s18.html
"Although data stored in /tmp may be deleted in a site-specific manner, it is recommended that files and directories located in /tmp be deleted whenever the system is booted."

https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch05s15.html
The /var/tmp directory is made available for programs that require temporary files or directories that are preserved between system reboots.

То есть для файлов, которые должны переживать перезагрузку должен использоваться /var/tmp.

-- 
best regards, Anton Midyukov <antohami@altlinux.org>



  reply	other threads:[~2025-11-06  7:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-06  6:56 Anton Midyukov
2025-11-06  7:04 ` [devel] " Sergey V Turchin
2025-11-06  7:06   ` [devel] " Anton Farygin
2025-11-06  7:21     ` Anton Midyukov [this message]
2025-11-06  7:27       ` [devel] " Sergey V Turchin
2025-11-06 17:32       ` [devel] " Leonid Krivoshein
2025-11-07  5:19         ` Денис Самсоненко
2025-11-07  4:50 ` Alexey V. Vissarionov

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=751d1592-8487-4e36-aab5-e8b59caf2fce@altlinux.org \
    --to=antohami@altlinux.org \
    --cc=devel@lists.altlinux.org \
    /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

ALT Linux Team development discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
		devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
	public-inbox-index devel

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git