Placing temporary data that survives reboot | LinuC Level 1 101 Exam original practice question

1.02.4Basic

Store temporary work files that need not be permanent but should normally survive a system reboot.

Which FHS directory is appropriate?

Hint 1: Focus on the requirement

Match the temporary-data location to whether it may survive a reboot.

Hint 2: Key terms

Review the short search and filesystem-placement definitions before comparing the choices.

/var/tmp: A hierarchy for temporary files that may be retained across reboots.
/tmp: A short-lived temporary-file hierarchy that may be cleared at boot.
/run: A hierarchy for runtime data valid only for the current boot.
Retention period: The operational rule defining how long temporary data is kept.

Detailed explanation

Incorrect/run

Incorrect. /run is generally a volatile runtime filesystem.

Incorrect/tmp

Incorrect. /tmp may be cleared during boot.

Incorrect/var/log

Incorrect. /var/log is for logs.

Correct/var/tmp

Correct. /var/tmp is intended for temporary files that can persist across reboot.

An example you can run in a temporary verification environment.

test -d /var/tmp && printf '/var/tmp exists\n'

/var/tmp exists

Environment: FHS準拠Linux / ディレクトリ存在確認のみ
Use read-only lookups or disposable paths when verifying search behavior.
Distribution-specific defaults should be checked before changing system configuration.

Foundation review

Neither location is permanent storage; /var/tmp simply has a longer expected lifetime than /tmp.

Confirm the distribution's cleanup policy before depending on retention for an important workflow.

Question IDKL-101-429

EnvironmentFHS準拠Linux / ディレクトリ存在確認のみ

Last technical review2026-08-13

More practice in this area