* On 23 Jan 2015, Jon LaBadie wrote: > > You should be able to "remove" it in the script that copies it and > starts firefox. If more than a process has a file open and the > file is removed, only the directory entry is deleted. The inode > and data blocks not freed until the last close is done. So you > may be able to do something like: > > copy > start firefox in background > pause a second or two > "remove" the copy > exit (or issue a "wait" for firefox to complete)
The trouble here is usually that /usr/bin/firefox is, itself, a wrapper. It typically passes a message to firefox (perhaps also launching firefox as a background process first) and then exits, so the real firefox might not actually read the file until after /usr/bin/firefox exits. This is how things used to be anyway -- maybe it's changed but I wouldn't expect so since this approach (while a bit messier) is more responsive to the user POV. -- David Champion • [email protected]
