[...]We need to back up a bit. I tried something different just for giggles because I thought we might be on the wrong track with setuid. I wrote a little script that this
#!/bin/bash /usr/opt/httpd-2.0.49/bin/httpd -d t -f conf/httpd.conf -DAPACHE2 -DONE_PROCESS -DNO_DETATCH > stdout 2>&1 & tusc -p -f -v -o strace $!
after running the script I went to a browser and hit
http://cars-l:8529/TestAPI__request_rec
The strace looks quite different this way (and the process does not exit). Turns out the setuid thing was the falt of my tusc command being setuid. (Sorry. insert sheepish look here)
Trace from this latest test is more what I expected to see:
stat64("/opt/local/wrfopt/build/mod_perl-1.99_14/t/response/TestAPI/request_rec.pm",
0x6ff66648) = 0
st_dev: 64 0x000005
st_ino: 171526
st_mode: S_IFREG|0644
st_nlink: 1
st_rdev: 0
st_size: 2503
st_blksize: 8192
st_blocks: 1
st_uid: 1073741829
st_gid: 27549760
st_atime: Tue Aug 10 16:50:28 2004
st_mtime: Fri Apr 18 02:18:58 2003
st_ctime: Mon Aug 9 20:40:52 2004
[...]Hangs at this point.
The compile with no LFS:
Blows right by the call to stat no problem. Get output in the browser say Ok to all 42 tests.
The only notable difference being the call to stat as opposed to stat64.
Excellent. So you've almost nailed it, William! Now try to see if there are any discussions on the web re: stat vs. stat64, e.g.:
http://www.google.ca/search?hl=fr&ie=UTF-8&q=stat+stat64+hangs&btnG=Rechercher&meta=
may be some more keywords should be added, like your platform name...
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
