A typical execution goes as follows (the line immediately below "PICKS OK" shows the input from the terminal):
$find_picks PICKS OK 010207.050000 010207.050059 010207.050012 /dat/picks/man/0102 010207.050009.970 010207.050019.100 $
Usually, find_picks is used to answer queries via the network. For example, when /etc/inetd.conf contains a settings line that goes like:
win-find_picks stream tcp nowait auto /home/auto/find_picks find_picks
and /etc/services a setting line that goes like:
win-find_picks 7130/tcp # WIN system find_picks,
find_picks uses TCP port 7130 to answer queries from the client (the line immediately below "PICKS OK" shows the input from the terminal).
$telnet server 7130 Trying 192.168.100.100... Connected to server. Escape character is '^]'. PICKS OK 010207.050000 010207.050059 010207.050012 /dat/picks/man/0102 010207.050009.970 010207.050019.100 Connection closed by foreign host. $
When obtaining the names of pick files belonging to event waveform files, win(1W) can send queries via TCP/IP to the pick file server associated with find_picks. This method works for relatively slow line IP connections. Otherwise, pick files will be searched by the NFS and this can be time-consuming.
The NFS environment does not necessarily guarantee the matching of the pick directory name on the client side with that on the server side. In such a case, some ingenuity may be required.