Enterprise Linux operations with tmpfiles, journald, NFS and versionlock
Author: DEWOLF.IT
Diagnose temporary-file cleanup, journal retention, Kerberos NFS and package version locks on enterprise Linux.
This English edition covers the main steps. See the Dutch article for the full detail and examples.
Temporary files and service isolation
Determine which filesystem holds the files, whether the service uses a private temporary directory and which cleanup policy applies. Give the application a designated directory and use a narrowly scoped tmpfiles rule if it needs predictable aging.
# /etc/tmpfiles.d/exampleapp.conf
# Type Path Mode User Group Age
d /var/tmp/exampleapp 0700 exampleapp exampleapp 7d
Journal storage and retention
Check the effective journal configuration and storage location before adjusting retention. Persistent and runtime storage have different limits. Size the local journal for available space and incident investigation, and account for any separate remote logging policy.
# Example only. Set limits for the host and its logging policy.
[Journal]
Storage=persistent
SystemMaxUse=1G
SystemKeepFree=2G
MaxRetentionSec=30day
Kerberos NFS
Trace the failure through name resolution, clock synchronisation, realm and principal, keytabs and tickets, export configuration and client mount options. Validate access as the application identity and use the protection level required by the environment.
Pinning packages with versionlock
Inspect enabled repositories, exclude rules and existing version locks before diagnosing a package that will not update. Document the reason, owner and expiry of a narrow lock. Review relevant security advisories during the exception and test removal in a controlled environment.
Consult the Red Hat Enterprise Linux documentation for the installed release.
