View Single Post
Old 09-04-2015, 06:30 AM   #2361
tshering
Wizard
tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.tshering ought to be getting tired of karma fortunes by now.
 
Posts: 3,489
Karma: 2914715
Join Date: Jun 2012
Device: kobo touch
Quote:
Originally Posted by Ken Maltby View Post
If you are looking at this issue, I can understand using lsof (to see a list of open files and the process ids using them) but why grep fonts?
I did it only to shorten the list.

Quote:
Originally Posted by Ken Maltby View Post
Wouldn't grep fonts get that list anyway?
Against which list would I have to run grep?

Quote:
Originally Posted by Ken Maltby View Post
Perhaps we could add:

exec 3<&-

after the call to reader.lua ? It should change your 2nd lsof results, wouldn't it?
I am not sure about that.
Maybe it would be possible to prevent this to start with. I have no idea how the opening of font files is related to wifi.
As for now, I thought of killing the process(es) that keep the files opened.
tshering is offline   Reply With Quote