Hey, sorry I didn't read your post quite right, and my brain was for some reason telling me that you were asking about /tmp.
No, it's fine. It still helped remind me about tmpfs vs ramdisk.
]]>Add yourself the adm group, or use "sudo systemctl status ..." to see the relevent journal info.
Thanks, adding myself to the group worked. This does what I want, so I will mark this thread as solved. Thank you to everyone who helped.
]]>[me@localhost ~]$ sudo systemctl start psd.service
Job for psd.service failed. See 'systemctl status psd.service' and 'journalctl -xn' for details.
[me@localhost ~]$ systemctl status psd.service
psd.service - Profile-sync-daemon
Loaded: loaded (/usr/lib/systemd/system/psd.service; enabled)
Active: failed (Result: exit-code) since Mon, 2012-12-31 11:32:59 EST; 10s ago
Process: 3402 ExecStart=/usr/bin/profile-sync-daemon sync (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/psd.service
Does anyone have any ideas as to why?
Thanks!
UnsolvedCypher wrote:I believe it would be possible to copy the files back to my SSD before reboot or shutdown. Also, I have symbolically linked some applications' caches and other operational files to this location thinking that the tmp meant that it was on tmpfs. So, I would like to actually put this on tmpfs.
Example: Browser running from RAM reduces tiny file writes and also speeds up things like cache.
That's very useful, thanks. I will look into this.
]]>So link them to /tmp ?
I'll do that, good idea. But how would I copy the files back before shutdown?
]]>I believe it would be possible to copy the files back to my SSD before reboot or shutdown.
yes, you could. You would have to copy the files from /var/tmp to the SSD and then back to /var/tmp on bootup. This saves you exactly 0 write cycles - congratulations!
Also, I have symbolically linked some applications' caches and other operational files to this location thinking that the tmp meant that it was on tmpfs. So, I would like to actually put this on tmpfs.
Example: Browser running from RAM reduces tiny file writes and also speeds up things like cache.
So link them to /tmp ?
]]>]]>I believe it would be possible to copy the files back to my SSD before reboot or shutdown. Also, I have symbolically linked some applications' caches and other operational files to this location thinking that the tmp meant that it was on tmpfs. So, I would like to actually put this on tmpfs.
Example: Browser running from RAM reduces tiny file writes and also speeds up things like cache.
UnsolvedCypher wrote:What I want to do is to put /var/tmp onto my RAM, but make sure that it does not clear on reboot. How would I go about doing this?
you can't do this. RAM drive = lost on reboot.
UnsolvedCypher wrote:Also, SSDs would last about 20 years if 50 GB was written daily. So yes, they last a while, but I'd just like to reduce unnecessary writes in addition to the nice speed boost.
They are not unnecessary, applications don't just write there for no reason.
I still don't see the point of this, just don't worry about it.
I believe it would be possible to copy the files back to my SSD before reboot or shutdown. Also, I have symbolically linked some applications' caches and other operational files to this location thinking that the tmp meant that it was on tmpfs. So, I would like to actually put this on tmpfs.
Example: Browser running from RAM reduces tiny file writes and also speeds up things like cache.
What I want to do is to put /var/tmp onto my RAM, but make sure that it does not clear on reboot. How would I go about doing this?
you can't do this. RAM drive = lost on reboot.
Also, SSDs would last about 20 years if 50 GB was written daily. So yes, they last a while, but I'd just like to reduce unnecessary writes in addition to the nice speed boost.
They are not unnecessary, applications don't just write there for no reason.
I still don't see the point of this, just don't worry about it.
]]>you shouldn't do anything, /var/tmp is not supposed to be cleared on reboot. Applications may rely on this, so you shouldn't mess with that.
imho you shouldn't be worried about this, afaik modern SSDs have a write cycle that you wouldn't be able to reach in your lifetime. And as far as I can see, there isn't much stuff written to /var/tmp anyway.
What I want to do is to put /var/tmp onto my RAM, but make sure that it does not clear on reboot. How would I go about doing this? Also, SSDs would last about 20 years if 50 GB was written daily. So yes, they last a while, but I'd just like to reduce unnecessary writes in addition to the nice speed boost.
]]>imho you shouldn't be worried about this, afaik modern SSDs have a write cycle that you wouldn't be able to reach in your lifetime. And as far as I can see, there isn't much stuff written to /var/tmp anyway.
]]>/usr/lib/systemd/system/tmp.mount
Edit: There are two types of RAM disks. One is ramfs and the other is tmpfs. They're basically the same except the tmpfs is dynamically sized.
I'm assuming this mean that /tmp is mounted as tmpfs, but /var/tmp is not. If I am correct, would modifying the file be the way to go in order to put /var/tmp in the tmpfs as well, or would I have to do something different because /var/tmp should not be cleared on reboot?
Thanks!
Edit: There are two types of RAM disks. One is ramfs and the other is tmpfs. They're basically the same except the tmpfs is dynamically sized.
]]>