Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!steinmetz!thuban!putnam From: putnam@thuban.steinmetz (putnam) Newsgroups: comp.windows.news Subject: Re: Help with user.ps Message-ID: <6661@steinmetz.steinmetz.UUCP> Date: Sun, 12-Jul-87 10:47:18 EDT Article-I.D.: steinmet.6661 Posted: Sun Jul 12 10:47:18 1987 Date-Received: Mon, 13-Jul-87 01:16:11 EDT References: <75200002@sfu_css> Sender: root@steinmetz.steinmetz.UUCP Reply-To: putnam@thuban.UUCP (putnam) Organization: General Electric CRD, Schenectady, NY Lines: 38 In article <75200002@sfu_css> keith@sfu_css.cs.sfu writes: > > I am having a problems with my user.ps file when starting > up NeWS. I have a bunch of (psterm) forkunix > lines, and sometimes it works completely, sometimes it > doesn't fire up anything, and sometimes it just fires > up the last one in the file. > > My question is > is this a known bug and is there a fix ?? This is known behavior. (I hesitate to call it a bug or someone will claim its a feature.) The following is in my user.ps file and seems to fix the problem - the basic idea was suggested by sun when i asked them about this problem. You might note that my psterm takes arguments to specify a label, size and location - these have been forwarded to Sun. /forkunixandwait % string => - { 2 dict begin /top { framebuffer /TopChild get } def /original_top top def forkunix { top original_top ne { exit } if pause } loop end } def { (/usr/kbs/kbs/putnam/sbin/psterm -C -f -t h19) forkunixandwait (/usr/kbs/kbs/putnam/sbin/psterm -l shell -t h19 -X 0 -Y 358 -W 596 -H 431) forkunixandwait (/usr/sungod/NeWS/demo/roundclock) forkunixandwait } fork pop Well, shall we go? -- jefu (jeff putnam) Yes, lets go. -- UUCP: steinmetz!putnam (They do not move.) -- ARPA: putnam@ge-crd.com