ocmd aka .OINK piping mechanism

From: John Irwin (ji10@mrc-lmb.cam.ac.uk)
Date: Mon Jul 08 1996 - 05:00:42 CDT


Hi O users!

This question is for anyone using the .OINK pipe for communicating with O.

Here is what the doc in ocmd.c says:

   Demo program to show how external programs can enter input into the
   O input stream. You must start O first, it should have created a
   named pipe called .OINK in the directory you are running it from.
   Now start ocmd with a file containing O commands, and redirect the
   output to .OINK:

I don't see the .OINK pipe in "ls -la" in the directory where I started O,
or anywhere else... I can start the ocmd command as described, but O does
not seem to be listening, suggesting that the pipe is indeed not created.
Perhaps my version of O doesn't support OINK? Has anyone using
4d_ono_5.10.3 seen the pipe? What version of O do I need?

I'd be interested to hear from anyone who has used this piping mechanism.

I'd be interested to hear from anyone who has got around the "inquisition"
at the beginning of O. I'd like to bring up O without having to hit return
a couple of times. I have used

O "startup.o" "menu.o   " "access.o "

but I can't seem to feed it "all.dat" and "Yes" in the same way to bypass
those last two questions.

Any help will be much appreciated.

John

--
John Irwin, Structural Studies, MRC-Laboratory of Molecular Biology, Hills
Road, Cambridge CB2 2QH, GB. Phone +44 1223 402213. Fax +44 1223 213556.
email ji10@mrc-lmb.cam.ac.uk. PGP key 0x53A1318D at
http://gerard2.mrc-lmb.cam.ac.uk/doc/ji10.asc.



This archive was generated by hypermail 2b29 : Tue Mar 20 2007 - 03:13:17 CST