in reply to CGI: A Tale of Two Usernames

A couple of alternatives ideas:

1. Run the web server as mptsuser. If you can't change this webserver, maybe you can install another apache for yourself on a different port.
  or
2. Write a perl script that is run as mptsuser by cron once a minute. Change your cgi script so that it creates a file telling the cron script what to do. If the one minute delay is bad, put a loop in your cron script so that it sleeps for a few seconds and checks for the file, repeating until just under a minute has passed.

Replies are listed 'Best First'.
Re^2: CGI: A Tale of Two Usernames
by wolfger (Deacon) on Dec 17, 2004 at 16:33 UTC
    I only wish I had such privelages on this box... And I wish we were using Apache instead of Websphere!
    Thanks for the suggestions, anyhow. I already decided on a course of action similar to #2. Since this CGI was already making a socket connection to another server to check on some process statuses, I decided to just run a second socket connection to a script running on mptsuser on 127.0.0.1 so that mptsuser can launch whatever the CGI tells it to. Maybe not the best solution, but the only one (so far) that doesn't make me dependant on somebody else doing what I want (or increasing my permissions) in a timely fashion this close to the holidays...

    --
    Linux, sci-fi, and Nat Torkington, all at Penguicon 3.0