Closed LaMarMot closed 6 months ago
Hi @LaMarMot , I think it's working as expected, you can actually see that the directory that you have would be a mountpoint actually and not a symlink, this change was made in asd with 6.0 version to make the user experience more transparent and help with the scenarios where asd crashes and restoration introduces a time gap that leads to the applications crashing.
Hey @manorit2001, thanks a lot for your answer (and for your work by the way !).
I kind of remembered asd
was using simlinks before (and is still referencing it in its description here by the way), and, as I'm not familiar with "bind mounting" (which I only discovered thanks to you :sweat_smile:) I then started to wonder what was wrong when I realize the directories weren't simlinks.
Thanks a lot for your reply and insights, much appreciated!
Hey
So, I’m using
anything-sync-daemon
(asd) on Arch Linux (EndeavourOS install to be exact) and I’m just wondering if it’s working as it should.I’m using it to manage the
chromium
cache directory.It’s suppose to “move” this directory in
tmpfs
(i.e. in RAM) and synchronize it to the hard drive from time to time…So when I “ask” it if everything is going according to plan, it seems to tell me “yes”:
But if I look at the “managed” folder (
/home/user/.cache/chromium
) it is still a “regular” directory, shouldn’t it rather be a symbolic link to/tmp/asd-user/home/user/.cache/chromium
?I’m using profile-sync-daemon (psd) to achieve the same behavior with my browsers profiles, and, in that case, the managed directories are (became) indeed symlinks to the directories in tmpfs…
Have I done something wrong or is
asd
working as it should (i.e. not writing cache on disk anymore, except to back it up)?I would be very grateful for any advice![:slight_smile: :slight_smile:](https://forum.endeavouros.com/images/emoji/twitter/slight_smile.png?v=12)
Cheers !!