Malloy - thanks for responding.
Unfortunately using restart_count does not address my issue.
In the http.conf I have the following:
...
PerlConfigRequire conf/startup.pl
...
My test startup.pl has this:
our $INPUT;
print STDERR "Input:";
$INPUT = <STDIN>;
print STDERR "you entered $INPUT";
My issue is during the first start everything works as I need it to,
"Input:" is printed out to the terminal and the script waits for input.
The problem is for the automatic restart everything is tied to the log files.
Everything printed to STDERR goes into the logs and a user cannot
enter any input.
For the restart how can I print messages and prompt for input?
Thanks.
---Alex
Quoting Malloy <jackwor...@gmail.com>:
Dealing with Restarts
Ideally the code running at the server startup shouldn't be affected by the
apache restart. If however this is not the case, you can use
Apache2::ServerUtil::restart_count.
More Info: http://perl.apache.org/docs/2.0/user/handlers/server.html
On Wed, Aug 19, 2009 at 4:54 AM, <ama...@solutionsforprogress.com> wrote:
I am in the process of porting a mod_perl app to mod_perl2.
The original mod_perl app has an interactive startup during which a DB
password is prompted for.
During the mod_perl2 startup this feature works fine at first but mod_perl2
always does a restart and during the second restart STDERR is being
redirected to the log files and STDIN is ignored.
So I am trying to figure out how to either:
1) Prevent the automatic restart or
2) Have STDERR and STDIN be tied to the terminal during the restart the
same way they are during the initial start
Here info about my system: Apache/2.2.9 (Debian) mod_apreq2-20051231/2.6.0
mod_perl/2.0.4 Perl/v5.10.0
Thank you in advance for any help/insight.
--Alex
--
Jack Malloy