lsof doesn't show up my djvu files
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
I am trying to print the djvu
file names that are currently running on either okular
or atril
, but when I do lsof | grep ".djvu$"
then I am getting no output in the terminal, where the same command works for pdf
files.
grep lsof djvu
add a comment |
up vote
1
down vote
favorite
I am trying to print the djvu
file names that are currently running on either okular
or atril
, but when I do lsof | grep ".djvu$"
then I am getting no output in the terminal, where the same command works for pdf
files.
grep lsof djvu
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I am trying to print the djvu
file names that are currently running on either okular
or atril
, but when I do lsof | grep ".djvu$"
then I am getting no output in the terminal, where the same command works for pdf
files.
grep lsof djvu
I am trying to print the djvu
file names that are currently running on either okular
or atril
, but when I do lsof | grep ".djvu$"
then I am getting no output in the terminal, where the same command works for pdf
files.
grep lsof djvu
grep lsof djvu
edited yesterday
Rui F Ribeiro
38.1k1475123
38.1k1475123
asked yesterday
Ritajit Kundu
84
84
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
if the application is running as a different user, you will need
sudo
:sudo lsof | grep ".djvu$"
if some of the file extension is capital, you need to
-i
ingrep
to ignore case:sudo lsof | grep -i ".djvu$"
the dot at the beginning of
.djvu$
will match any character (though this probably won't cause false positives in your case); what you probably mean is.djvu$
I recommend putting regular expressions in single quotes rather than double quotes because the dollar sign has special meaning for the Linux shell:
sudo lsof | grep -i '.djvu$'
(updated from
ps
topgrep
thanks to comment from qubert) if the application reads the files into memory and then closes it, thelsof
won't see it, butps
(process list) will;pgrep
is the proper tool to search through running processes; try:pgrep --list-full --full --ignore-case '.djvu'
I tried your suggestion but again, though I have adjvu
file open, I get nothing.
– Ritajit Kundu
yesterday
@Ritajit Kundu - I don't have that reader. It's possible that the application opens the file, reads the contents into memory, and then closes the file before you runlsof
so that you don't have a chance to see it when it's open. I added a 5th bullet to my list above which may work if this is the case.
– bitinerant
yesterday
the last command works. thanks a lot.
– Ritajit Kundu
yesterday
the library used to render .djvus (libdjvulibre) is always using separate threads to render each page, and it's those threads that open the file (they're not passed an open fd from the parent), and exit when they're finished rendering.
– qubert
yesterday
instead ofps -ef | grep ...
, usepgrep -afi '.djvu>'
; or if you insist on usingps
, useps -wwef | grep ...
; otherwise it will truncate the command line and may miss if eg. a .djvu file name is longer than 80 characters.
– qubert
yesterday
|
show 1 more comment
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
if the application is running as a different user, you will need
sudo
:sudo lsof | grep ".djvu$"
if some of the file extension is capital, you need to
-i
ingrep
to ignore case:sudo lsof | grep -i ".djvu$"
the dot at the beginning of
.djvu$
will match any character (though this probably won't cause false positives in your case); what you probably mean is.djvu$
I recommend putting regular expressions in single quotes rather than double quotes because the dollar sign has special meaning for the Linux shell:
sudo lsof | grep -i '.djvu$'
(updated from
ps
topgrep
thanks to comment from qubert) if the application reads the files into memory and then closes it, thelsof
won't see it, butps
(process list) will;pgrep
is the proper tool to search through running processes; try:pgrep --list-full --full --ignore-case '.djvu'
I tried your suggestion but again, though I have adjvu
file open, I get nothing.
– Ritajit Kundu
yesterday
@Ritajit Kundu - I don't have that reader. It's possible that the application opens the file, reads the contents into memory, and then closes the file before you runlsof
so that you don't have a chance to see it when it's open. I added a 5th bullet to my list above which may work if this is the case.
– bitinerant
yesterday
the last command works. thanks a lot.
– Ritajit Kundu
yesterday
the library used to render .djvus (libdjvulibre) is always using separate threads to render each page, and it's those threads that open the file (they're not passed an open fd from the parent), and exit when they're finished rendering.
– qubert
yesterday
instead ofps -ef | grep ...
, usepgrep -afi '.djvu>'
; or if you insist on usingps
, useps -wwef | grep ...
; otherwise it will truncate the command line and may miss if eg. a .djvu file name is longer than 80 characters.
– qubert
yesterday
|
show 1 more comment
up vote
0
down vote
accepted
if the application is running as a different user, you will need
sudo
:sudo lsof | grep ".djvu$"
if some of the file extension is capital, you need to
-i
ingrep
to ignore case:sudo lsof | grep -i ".djvu$"
the dot at the beginning of
.djvu$
will match any character (though this probably won't cause false positives in your case); what you probably mean is.djvu$
I recommend putting regular expressions in single quotes rather than double quotes because the dollar sign has special meaning for the Linux shell:
sudo lsof | grep -i '.djvu$'
(updated from
ps
topgrep
thanks to comment from qubert) if the application reads the files into memory and then closes it, thelsof
won't see it, butps
(process list) will;pgrep
is the proper tool to search through running processes; try:pgrep --list-full --full --ignore-case '.djvu'
I tried your suggestion but again, though I have adjvu
file open, I get nothing.
– Ritajit Kundu
yesterday
@Ritajit Kundu - I don't have that reader. It's possible that the application opens the file, reads the contents into memory, and then closes the file before you runlsof
so that you don't have a chance to see it when it's open. I added a 5th bullet to my list above which may work if this is the case.
– bitinerant
yesterday
the last command works. thanks a lot.
– Ritajit Kundu
yesterday
the library used to render .djvus (libdjvulibre) is always using separate threads to render each page, and it's those threads that open the file (they're not passed an open fd from the parent), and exit when they're finished rendering.
– qubert
yesterday
instead ofps -ef | grep ...
, usepgrep -afi '.djvu>'
; or if you insist on usingps
, useps -wwef | grep ...
; otherwise it will truncate the command line and may miss if eg. a .djvu file name is longer than 80 characters.
– qubert
yesterday
|
show 1 more comment
up vote
0
down vote
accepted
up vote
0
down vote
accepted
if the application is running as a different user, you will need
sudo
:sudo lsof | grep ".djvu$"
if some of the file extension is capital, you need to
-i
ingrep
to ignore case:sudo lsof | grep -i ".djvu$"
the dot at the beginning of
.djvu$
will match any character (though this probably won't cause false positives in your case); what you probably mean is.djvu$
I recommend putting regular expressions in single quotes rather than double quotes because the dollar sign has special meaning for the Linux shell:
sudo lsof | grep -i '.djvu$'
(updated from
ps
topgrep
thanks to comment from qubert) if the application reads the files into memory and then closes it, thelsof
won't see it, butps
(process list) will;pgrep
is the proper tool to search through running processes; try:pgrep --list-full --full --ignore-case '.djvu'
if the application is running as a different user, you will need
sudo
:sudo lsof | grep ".djvu$"
if some of the file extension is capital, you need to
-i
ingrep
to ignore case:sudo lsof | grep -i ".djvu$"
the dot at the beginning of
.djvu$
will match any character (though this probably won't cause false positives in your case); what you probably mean is.djvu$
I recommend putting regular expressions in single quotes rather than double quotes because the dollar sign has special meaning for the Linux shell:
sudo lsof | grep -i '.djvu$'
(updated from
ps
topgrep
thanks to comment from qubert) if the application reads the files into memory and then closes it, thelsof
won't see it, butps
(process list) will;pgrep
is the proper tool to search through running processes; try:pgrep --list-full --full --ignore-case '.djvu'
edited yesterday
answered yesterday
bitinerant
363
363
I tried your suggestion but again, though I have adjvu
file open, I get nothing.
– Ritajit Kundu
yesterday
@Ritajit Kundu - I don't have that reader. It's possible that the application opens the file, reads the contents into memory, and then closes the file before you runlsof
so that you don't have a chance to see it when it's open. I added a 5th bullet to my list above which may work if this is the case.
– bitinerant
yesterday
the last command works. thanks a lot.
– Ritajit Kundu
yesterday
the library used to render .djvus (libdjvulibre) is always using separate threads to render each page, and it's those threads that open the file (they're not passed an open fd from the parent), and exit when they're finished rendering.
– qubert
yesterday
instead ofps -ef | grep ...
, usepgrep -afi '.djvu>'
; or if you insist on usingps
, useps -wwef | grep ...
; otherwise it will truncate the command line and may miss if eg. a .djvu file name is longer than 80 characters.
– qubert
yesterday
|
show 1 more comment
I tried your suggestion but again, though I have adjvu
file open, I get nothing.
– Ritajit Kundu
yesterday
@Ritajit Kundu - I don't have that reader. It's possible that the application opens the file, reads the contents into memory, and then closes the file before you runlsof
so that you don't have a chance to see it when it's open. I added a 5th bullet to my list above which may work if this is the case.
– bitinerant
yesterday
the last command works. thanks a lot.
– Ritajit Kundu
yesterday
the library used to render .djvus (libdjvulibre) is always using separate threads to render each page, and it's those threads that open the file (they're not passed an open fd from the parent), and exit when they're finished rendering.
– qubert
yesterday
instead ofps -ef | grep ...
, usepgrep -afi '.djvu>'
; or if you insist on usingps
, useps -wwef | grep ...
; otherwise it will truncate the command line and may miss if eg. a .djvu file name is longer than 80 characters.
– qubert
yesterday
I tried your suggestion but again, though I have a
djvu
file open, I get nothing.– Ritajit Kundu
yesterday
I tried your suggestion but again, though I have a
djvu
file open, I get nothing.– Ritajit Kundu
yesterday
@Ritajit Kundu - I don't have that reader. It's possible that the application opens the file, reads the contents into memory, and then closes the file before you run
lsof
so that you don't have a chance to see it when it's open. I added a 5th bullet to my list above which may work if this is the case.– bitinerant
yesterday
@Ritajit Kundu - I don't have that reader. It's possible that the application opens the file, reads the contents into memory, and then closes the file before you run
lsof
so that you don't have a chance to see it when it's open. I added a 5th bullet to my list above which may work if this is the case.– bitinerant
yesterday
the last command works. thanks a lot.
– Ritajit Kundu
yesterday
the last command works. thanks a lot.
– Ritajit Kundu
yesterday
the library used to render .djvus (libdjvulibre) is always using separate threads to render each page, and it's those threads that open the file (they're not passed an open fd from the parent), and exit when they're finished rendering.
– qubert
yesterday
the library used to render .djvus (libdjvulibre) is always using separate threads to render each page, and it's those threads that open the file (they're not passed an open fd from the parent), and exit when they're finished rendering.
– qubert
yesterday
instead of
ps -ef | grep ...
, use pgrep -afi '.djvu>'
; or if you insist on using ps
, use ps -wwef | grep ...
; otherwise it will truncate the command line and may miss if eg. a .djvu file name is longer than 80 characters.– qubert
yesterday
instead of
ps -ef | grep ...
, use pgrep -afi '.djvu>'
; or if you insist on using ps
, use ps -wwef | grep ...
; otherwise it will truncate the command line and may miss if eg. a .djvu file name is longer than 80 characters.– qubert
yesterday
|
show 1 more comment
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f481524%2flsof-doesnt-show-up-my-djvu-files%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password