in reply to RPC

Well, there are a few cases left to try, don't you think? Run the code via RPC within the client machine. On the server, stub out the client bits and run the subroutine w/o RPC.

Not being shy about making wild guesses in public, I suspect that the second case will turn up a problem. For example, are you sure what the current working directory is when the sub is called via RPC? I'll even guess that your open is failing, causing the <USERS> line to die which probably means that RPC won't be responding anymore.

Oh, and fire your code reviewers if they didn't tell you to check for failure of open! (:

P.S. The quotes around 'USERS' are just fine.

        - tye (but my friends call me "Tye")

Replies are listed 'Best First'.
Re: (tye)Re: RPC
by Necos (Friar) on May 08, 2001 at 04:17 UTC
    Heya Tye. The sub I wrote was initially tested with die during the first coding session. Unfortunately, I'm the only coder here that knows Perl. Perl is also the only language I know (it's probably the easiest language since FORTRAN and VB). I was not expecting to run into this problem, so I had avoided large error handling subs. I guess now I must put them in to ensure these programs work properly. I guess I'll have to give up a little bit of the speed now. Oh well, I think the programs will work fine with heavy error handlers (I hope!!!). Thanks for pointing out the cwd possibility. I'll look into that later today. Thanks your your help guys. Any other pointers, style advise, or what-have-you will be much appreciated. Necos

      or die "..." is not "large error handling" and does not make your code run any slower. I suppose you could argue that it will make your code take a few milliseconds longer to compile. If you eventually compile it enough times to make up for the time you've now spent trying to track down this problem, especially when you consider how much you get paid per hour vs. how much your computer costs per hour, then let us know. We'll all be very surprised. (:

              - tye (but my friends call me "Tye")
        Well, I seemed to have fixed the problem... Apparently, what converter said was right. The string literal 'USERS' was clobbering the open command. Go figure... In any case, I learned a valuable lesson: Write error handlers at all times!!! Also, if at all possible, make them good ones... ^_^. Necos