Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Your problem is <code>if</code> statement below:</p> <pre><code>while true do if read txt &lt;"$pipe" .... done </code></pre> <p>What is happening is that your job queue server is opening and closing the pipe each time around the loop. This means that some of the clients are getting a "broken pipe" error when they try to write to the pipe - that is, the reader of the pipe goes away after the writer opens it.</p> <p>To fix this, change your loop in the server open the pipe once for the entire loop:</p> <pre><code>while true do if read txt .... done &lt; "$pipe" </code></pre> <p>Done this way, the pipe is opened once and kept open.</p> <p>You will need to be careful of what you run inside the loop, as all processing inside the loop will have stdin attached to the named pipe. You will want to make sure you redirect stdin of all your processes inside the loop from somewhere else, otherwise they may consume the data from the pipe.</p> <p>Edit: With the problem now being that you are getting EOF on your reads when the last client closes the pipe, you can use jilles method of duping the file descriptors, or you can just make sure you are a client too and keep the write side of the pipe open:</p> <pre><code>while true do if read txt .... done &lt; "$pipe" 3&gt; "$pipe" </code></pre> <p>This will hold the write side of the pipe open on fd 3. The same caveat applies with this file descriptor as with stdin. You will need to close it so any child processes dont inherit it. It probably matters less than with stdin, but it would be cleaner.</p>
    singulars
    1. This table or related slice is empty.
    1. POUsing named pipes with bash - Problem with data loss
      singulars
      1. PTQuestion
    1. PTAnswer
    1. UScamh
    1. UScamh
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POUsing named pipes with bash - Problem with data loss
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWow, great answer. Makes sense. Thanks. Will give it a try immediately.
      singulars
      1. PO
      1. USasoundmove
    2. COOk, now you solved the key issue, I have another one: how do you get the read to wait for input? I'll post a reply to myself further below with sample code.
      singulars
      1. PO
      1. USasoundmove
    3. CO@asoundmove: I've updated the answer with solution to EOF on read.
      singulars
      1. PO
      1. UScamh
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload