Waiting for async console (message queue) output after invoking a command [closed]

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite












I have to work with a command (lets call it update) which somehow prints its output asynchronously to the terminal (mq_timedsend). The output is not recognized as the commands output and therefore the stdout of the command is not usable (piping like update| grep -m 1 "$s" does not work). Unfortunately, I have to life with this.



Invoking the command sooner or later will print $s or $f as the creators were apparently also not aware of exit codes. I need to be able to parse after $s and $f and set the exit code manually.



I'm still not very versioned with bash and all its possibilities. How could a script or even a single chained command which will execute the update command and will wait until the specific text ($s or $f) appears in the console look like? Is this even possible?






bash output exit-code async







share|improve this question















closed as unclear what you're asking by andcoz, schily, Isaac, msp9011, maulinglawns Aug 22 at 10:16


Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.














  • Are you searching for literally $s in update output? What happens if you try update | grep -m 1 -F '$s'?
    – andcoz
    Aug 21 at 12:16










  • Nothing, as the command update does not produce a direct output. It most possibly starts another background process which finally prints to the console.
    – Herr Derb
    Aug 21 at 12:23











  • Perhaps update is using STDERR, try update 2>&1 | grep -m 1 -F '$s'
    – andcoz
    Aug 21 at 14:04










  • no I'm afraid not. update &> log.txt results in an empty file while text is getting printed to the console, after the console was ready to take input again.
    – Herr Derb
    Aug 21 at 15:28






  • 1




    You should find out what processes update creates and what file descriptors it writes to. Try with e.g. strace or similar.
    – RudiC
    Aug 21 at 22:13














up vote
1
down vote

favorite












I have to work with a command (lets call it update) which somehow prints its output asynchronously to the terminal (mq_timedsend). The output is not recognized as the commands output and therefore the stdout of the command is not usable (piping like update| grep -m 1 "$s" does not work). Unfortunately, I have to life with this.



Invoking the command sooner or later will print $s or $f as the creators were apparently also not aware of exit codes. I need to be able to parse after $s and $f and set the exit code manually.



I'm still not very versioned with bash and all its possibilities. How could a script or even a single chained command which will execute the update command and will wait until the specific text ($s or $f) appears in the console look like? Is this even possible?






bash output exit-code async







share|improve this question















closed as unclear what you're asking by andcoz, schily, Isaac, msp9011, maulinglawns Aug 22 at 10:16


Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.














  • Are you searching for literally $s in update output? What happens if you try update | grep -m 1 -F '$s'?
    – andcoz
    Aug 21 at 12:16










  • Nothing, as the command update does not produce a direct output. It most possibly starts another background process which finally prints to the console.
    – Herr Derb
    Aug 21 at 12:23











  • Perhaps update is using STDERR, try update 2>&1 | grep -m 1 -F '$s'
    – andcoz
    Aug 21 at 14:04










  • no I'm afraid not. update &> log.txt results in an empty file while text is getting printed to the console, after the console was ready to take input again.
    – Herr Derb
    Aug 21 at 15:28






  • 1




    You should find out what processes update creates and what file descriptors it writes to. Try with e.g. strace or similar.
    – RudiC
    Aug 21 at 22:13












up vote
1
down vote

favorite









up vote
1
down vote

favorite











I have to work with a command (lets call it update) which somehow prints its output asynchronously to the terminal (mq_timedsend). The output is not recognized as the commands output and therefore the stdout of the command is not usable (piping like update| grep -m 1 "$s" does not work). Unfortunately, I have to life with this.



Invoking the command sooner or later will print $s or $f as the creators were apparently also not aware of exit codes. I need to be able to parse after $s and $f and set the exit code manually.



I'm still not very versioned with bash and all its possibilities. How could a script or even a single chained command which will execute the update command and will wait until the specific text ($s or $f) appears in the console look like? Is this even possible?






bash output exit-code async







share|improve this question















I have to work with a command (lets call it update) which somehow prints its output asynchronously to the terminal (mq_timedsend). The output is not recognized as the commands output and therefore the stdout of the command is not usable (piping like update| grep -m 1 "$s" does not work). Unfortunately, I have to life with this.



Invoking the command sooner or later will print $s or $f as the creators were apparently also not aware of exit codes. I need to be able to parse after $s and $f and set the exit code manually.



I'm still not very versioned with bash and all its possibilities. How could a script or even a single chained command which will execute the update command and will wait until the specific text ($s or $f) appears in the console look like? Is this even possible?






bash output exit-code async




bash output exit-code async






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Aug 22 at 8:06

























asked Aug 21 at 12:06









Herr Derb

1062




1062




closed as unclear what you're asking by andcoz, schily, Isaac, msp9011, maulinglawns Aug 22 at 10:16


Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.






closed as unclear what you're asking by andcoz, schily, Isaac, msp9011, maulinglawns Aug 22 at 10:16


Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.













  • Are you searching for literally $s in update output? What happens if you try update | grep -m 1 -F '$s'?
    – andcoz
    Aug 21 at 12:16










  • Nothing, as the command update does not produce a direct output. It most possibly starts another background process which finally prints to the console.
    – Herr Derb
    Aug 21 at 12:23











  • Perhaps update is using STDERR, try update 2>&1 | grep -m 1 -F '$s'
    – andcoz
    Aug 21 at 14:04










  • no I'm afraid not. update &> log.txt results in an empty file while text is getting printed to the console, after the console was ready to take input again.
    – Herr Derb
    Aug 21 at 15:28






  • 1




    You should find out what processes update creates and what file descriptors it writes to. Try with e.g. strace or similar.
    – RudiC
    Aug 21 at 22:13
















  • Are you searching for literally $s in update output? What happens if you try update | grep -m 1 -F '$s'?
    – andcoz
    Aug 21 at 12:16










  • Nothing, as the command update does not produce a direct output. It most possibly starts another background process which finally prints to the console.
    – Herr Derb
    Aug 21 at 12:23











  • Perhaps update is using STDERR, try update 2>&1 | grep -m 1 -F '$s'
    – andcoz
    Aug 21 at 14:04










  • no I'm afraid not. update &> log.txt results in an empty file while text is getting printed to the console, after the console was ready to take input again.
    – Herr Derb
    Aug 21 at 15:28






  • 1




    You should find out what processes update creates and what file descriptors it writes to. Try with e.g. strace or similar.
    – RudiC
    Aug 21 at 22:13















Are you searching for literally $s in update output? What happens if you try update | grep -m 1 -F '$s'?
– andcoz
Aug 21 at 12:16




Are you searching for literally $s in update output? What happens if you try update | grep -m 1 -F '$s'?
– andcoz
Aug 21 at 12:16












Nothing, as the command update does not produce a direct output. It most possibly starts another background process which finally prints to the console.
– Herr Derb
Aug 21 at 12:23





Nothing, as the command update does not produce a direct output. It most possibly starts another background process which finally prints to the console.
– Herr Derb
Aug 21 at 12:23













Perhaps update is using STDERR, try update 2>&1 | grep -m 1 -F '$s'
– andcoz
Aug 21 at 14:04




Perhaps update is using STDERR, try update 2>&1 | grep -m 1 -F '$s'
– andcoz
Aug 21 at 14:04












no I'm afraid not. update &> log.txt results in an empty file while text is getting printed to the console, after the console was ready to take input again.
– Herr Derb
Aug 21 at 15:28




no I'm afraid not. update &> log.txt results in an empty file while text is getting printed to the console, after the console was ready to take input again.
– Herr Derb
Aug 21 at 15:28




1




1




You should find out what processes update creates and what file descriptors it writes to. Try with e.g. strace or similar.
– RudiC
Aug 21 at 22:13




You should find out what processes update creates and what file descriptors it writes to. Try with e.g. strace or similar.
– RudiC
Aug 21 at 22:13















active

oldest

votes






















active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
-

Popular posts from this blog

How to check contact read email or not when send email to Individual?

Image
Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this question asked Sep 26 at 0:12 ToanLuong 49 9 add a comment  |  up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this questi...
Read more

Displaying single band from multi-band raster using QGIS

Image
Clash Royale CLAN TAG #URR8PPP 1 How can I extract a single band from multi-band raster in QGIS? I have an remote sensed image which has 6 bands (including NDVI band), I want to display each band separately, but have no idea how to do. I have seen some questions similar here but none worked for me. The original image (has 6 bands) is: I want to display the band 6 which should be like this: But I tried gdal_translate, and couldn't get the correct result. What I have got is: qgis raster multi-band share | improve this question edited Mar 5 at 0:53 Summer asked Mar 4 at 6:42 Summer Summer 23 6 Is this any help gis.stackexchange.com/questions/220658/… ? if not gis.stackexchange.com/questions/62133/… might help. – Michael Stimson Mar 4 at 6:46 Thanks for answering but when I used gdal_translate, qgis showed that 'Error 4: Kayena.tif: No such file or directory". Would you know how to fi...
Read more

How many registers does an x86_64 CPU actually have?

Image
Clash Royale CLAN TAG #URR8PPP up vote 2 down vote favorite I am currently learning reverse engineering and am studying the flags register. I had in my mind that rflags was just another name for one of the 16 general purpose registers, for example rax or rbx . But it looks like rflags is actually an additional register. So that makes 17 registers in total... how many more could there be? I have spent at least an hour on this and found numerous different answers. The best answer so far is this, which says that there are 40 registers in total. 16 General Purpose Registers 2 Status Registers 6 Code Segment Registers 16 SSE Registers 8 FPU/MMX Registers But if I add that up, I get 48. Could anybody provide an official answer on how many registers an x86_64 CPU has (e.g. an Intel i7). Additionally, I have seen references to 'hardware' and 'architectural' registers. What are those registers and how many are there? register x86-64 share | improve this...
Read more