Re: Passing variable to another CGI.pm program

[blue_cowdawg]

Why pass the name? Use the UID that you are going to glean from /etc/password.

Better yet why not just put the functionality of both CGI scripts into one CGI? This method is a good example of a justification to create modules.

Update: I'm not a big fan of "pipe-fitting" processes together. I remember inheriting a project that suffered from performance issues what consisted of scriptA --pipe--> scriptB --pipe--> scriptC --> and nausuem and back to scriptA types of chains. First thing I did was create modules with the working "guts" of all the scripts and replaced all the scripts. Now if scriptA needed some functionality in scriptB it could access that functionality locally rather than piping.