Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
the devs are saying that this, along with most other changes concerning the cache, has security reasons. Those other changes include, for example, that you won't easily find videos in the cache, as before. Instead they are obfuscated and immediately deleted in /tmp.
However you can still use the file descriptors from the procfs to copy the downloaded videos (in case videos are your problem...).
the devs are saying that this, along with most other changes concerning the cache, has security reasons. Those other changes include, for example, that you won't easily find videos in the cache, as before. Instead they are obfuscated and immediately deleted in /tmp.
However you can still use the file descriptors from the procfs to copy the downloaded videos (in case videos are your problem...).
AHA , that's what i thought , yes i've read about those "security concerns" i think they are just bogus anyways (and i hate it when devs force decisions on us , would have been nice if they gave us an option to toggle on/off or something).
yes i was trying to find videos in the cache among other things such as flash objects and so forth , btw they are not obfuscated , it's just that they are scattered over a huge directory of directories....aaarrrg !
anyways ,how do i do this procfs magic that you're talking about ?
EDIT: ok looks like i figured out the first part
/proc/PID/fdinfo (PID being FF's pid)
now what? how do i access the files via fd's from the command line?
but how come that the file is still accessible when it says that it has been deleted ?
if i attempt to access the actual /tmp pathname that the soft link references , i don't get anything ...how is that possible?
so if it's not deleted then where exactly is being held ? in the labyrinthian cache directoy ? in Ram ?
deleted files are not really deleted. They are just 'unlinked' from its inode while the data is still there.
In the above case you are using the fact, that a process still has a file descriptor for that file (e.g. "has that file open"), which contains the necessary information to access the data on the disk.
If you have lsof installed, you can use that too (lsof -p <pid>).
Last edited by almatic; 06-01-2011 at 05:37 PM.
Reason: its ≠ it's
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.