This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Jason, The error logging removes the spaces. It has nothing to do with the way pqact is executing the line. So, assuming /home/bin/nexradII_bz is executable by the LDM account, and the /home/ldm/data/nexradII/KTLX/ directory exists and is writable by the ldm- I guess my first question would be is /home/bin/nexradII_bz correct? Should it be: /home/ldm/bin/nexradII_bz? I don't know many setups that stich a bin directory in /home. Steve Chiswell Unidata User Support On Fri, 5 Oct 2001, Jason J. Levit wrote: > > Hi Steve, > > I tried adding a "-v" for verbose output to my decompression program, > and this is how it shows up in the logs: > > Oct 05 17:09:01 storm pqact[780]: child 784 exited with status 127 > Oct 05 17:09:01 storm pqact[780]: child 782 exited with status 127 > Oct 05 17:09:01 storm pqact[780]: pbuf_flush (5) write: Broken pipe > Oct 05 17:09:01 storm pqact[780]: pipe_dbufput: > /home/bin/nexradII_bz-v/home/ldm/data/nexradII/KTLX/20011005170654.ridds > write error > > So, now the "-v" shows up without any spaces between the commands in > the output. Why is LDM smushing the lines in PIPE together? I've never > seen this one before....thanks for all your help. > > Jason > > -- > ---------------------------------------------------------------------------- > Jason J. Levit, N9MLA Research Scientist, > address@hidden Center for Analysis and Prediction of Storms > Room 1022 University of Oklahoma > 405/325-3503 http://www.caps.ou.edu/ >