On 02/19/2015 10:40 AM, Rejy M Cyriac wrote:
On 02/19/2015 11:04 PM, jd1008 wrote:
On 02/19/2015 09:56 AM, Matthew Miller wrote:
On Fri, Feb 20, 2015 at 12:46:31AM +1030, Tim wrote:
Neither, it's a function of it being on tmpfs and being rebooted -
it's not persistent. Whereas /var/tmp is managed by
systemd-tmpfiles-clean.timer.
And on those systems that are left running 24 hours a day?
Note that systemd-tmpfiles also cleans /tmp in its default
configuration. See /usr/lib/tmpfiles.d/tmp.conf, which contains (with
some other stuff):
d /tmp 1777 root root 10d
d /var/tmp 1777 root root 30d
What about
/usr/bin/systemd-tmpfiles
/usr/lib/tmpfiles.d
/usr/lib/dracut/modules.d/98systemd/dracut-tmpfiles.conf
/usr/lib/systemd/system/systemd-tmpfiles-clean.service
/usr/lib/systemd/system/systemd-tmpfiles-clean.timer
/usr/lib/systemd/system/systemd-tmpfiles-setup-dev.service
/usr/lib/systemd/system/systemd-tmpfiles-setup.service
/usr/lib/systemd/system/sysinit.target.wants/systemd-tmpfiles-setup-dev.service
/usr/lib/systemd/system/sysinit.target.wants/systemd-tmpfiles-setup.service
/usr/lib/systemd/system/timers.target.wants/systemd-tmpfiles-clean.timer
Which of these should be disabled in order to make my /tmp files to
survive reboot?
Generally it is the *.conf file which needs to be created/edited to
change the default configuration settings for services. So it looks like
/usr/lib/tmpfiles.d/tmp.conf is your friend for this objective.
'man systemd-tmpfiles' will help you with more information
Interesting obeservation, after I disabled the creation and mount a
tmpfs on /tmp TODAY.
$ cd /tmp
$ ls -ltr
total 1264K
drwx------ 2 jd jd 4096 Dec 31 1969 orbit-jd/
-rw-------. 1 root root 0 Oct 8 13:15 yum.log
-rwx------. 1 root root 663 Oct 8 13:47 ks-script-DhSaAL*
drwxr-xr-x. 2 root root 4096 Oct 8 14:50 hsperfdata_root/
-rw-------. 1 root root 1255957 Oct 8 15:35
yum_save_tx.2014-10-08.15-35.pQVxxn.yumtx
-rw-r--r-- 1 jd jd 0 Feb 19 11:00
qtsingleapp-smplay-ca73-3f0-lockfile
drwx------ 3 root root 4096 Feb 19 12:45
systemd-private-186b844601e2408eaf31371607e83295-rtkit-daemon.service-jSJb1H/
drwx------ 3 root root 4096 Feb 19 12:45
systemd-private-186b844601e2408eaf31371607e83295-cups.service-fz1pho/
drwx------ 3 root root 4096 Feb 19 12:45
systemd-private-186b844601e2408eaf31371607e83295-ntpd.service-p2YLgg/
drwx------ 3 root root 4096 Feb 19 12:45
systemd-private-186b844601e2408eaf31371607e83295-colord.service-4x8X99/
drwx------ 2 jd jd 4096 Feb 19 12:46 ssh-esVxvDC58XKz/
prw------- 1 root root 0 Feb 19 12:46 hogsuspend|
srwxr-xr-x 1 jd jd 0 Feb 19 12:46 qtsingleapp-smplay-ca73-3f0=
drwx------ 2 jd jd 4096 Feb 19 12:46 kde-jdiXm3Tn/
So, how come files dated from Oct 8th of 2014 and last Dec are still in
/tmp,
when I only disabled tmpfs for /tmp today?
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
