Well then :) thats interesting
Makes me think of chroot and child processes without STDIN/STDOUT/STDERR and with different $PATH or other vars ...
ENOTTY getpwent -> getlogin man page on HP-UX
[ENOTTY] None of the standard input, standard outp +ut, or standard error is a terminal, or for the first of these that is a terminal, no current login is registered on that terminal, or the session leader process of the calling process has no con‐ trolling terminal.
So not exactly on point but same ballpark ... apache is creating some kind of limited child processes ... i've seen this on win32 ...
Next step I might take would be strace :)
Or just kick the report up the chain (mod_perl, apache, ossupport..??)
Maybe consult some crontab ... faqs..
Neat :)
In reply to Re^7: [SOLVED] Configuring Apache VirtualHosts using mod_perl 2
by Anonymous Monk
in thread [SOLVED] Configuring Apache VirtualHosts using mod_perl 2
by FloydATC
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |