Summary: | start-stop-daemon's -r option doesn't function as specified (with apache 1.3.27) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | adam morley <axm135> |
Component: | Current packages | Assignee: | Donny Davies (RETIRED) <woodchip> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | azarah, mholzer |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
adam morley
2003-04-24 20:16:48 UTC
Could be because apache tries to run php which is not in the chroot .... I'm using mod_php --- I was under the impression I wouldn't need php b/c of that. Besides --- I should get a different error (or so I would think) since php isn't there. Heck, I don't even have php installed on this machine --- and so I would think I'd get the same kind of error (or at least an error of some kind) running apache alone. Ok, I just saw the PHP in there. Anyhow, if it also do this with 'chroot...', then Im guessing its not a start-stop-daemon problem, but rather with chroot/apache/config ? Okay, I'm dumb --- the libraries weren't executable, and apparently they have to be inside a chroot. I've fixed that; it works now. Would an ebuild for apache inside a chroot be of any use? or is that not really too helpful? this is ridiculous. this is bugs.gentoo.org not i-need-technical-support.gentoo.org > I intially thought it might be grsec, and filed a bug, and it was ignored,
> mostly, I think because I was suggesting a feature add at the same time.
Ummmmmmmmmm, NO.
I told you to debug your problem yourself. You want to customise and hack
your system up into pieces in order to make it the way you want? Fine. I
do that too. But I dont then turn around and expect everybody else to fix
my mistakes for me.
You on the other hand, have now submitted this garbage TWICE.
I think its safe for you to assume that anything else you submit to
this "bug tracker system" is going to be pretty much ignored by me.
Have a nice day.
What led me to believe my request had been misunderstood was that I filed it as a feature add, and I received this back (this is bug 19724): > umm, this is bugs.gentoo.org, not free-technical-support.gentoo.org > > the apache ebuild doesnt support chroot'ing the daemon on its own. > if you want to do that, then set it up yuorself. and debug it > yourself. So I tried, and failed. I worked on it some more, and still couldn't figure out what was wrong, asked other linux users I knew, and finally came here to state that as far as I could tell it was a bug. I'm sorry if I've wasted your time, but I was trying to get something to work, thought I'd found a bug, and had hoped it would be helpful to track it down, since I didn't know anyone else running Apache inside a chroot on linux. Again, sorry Donny. Where should I go in the future to ensure that I track down all possible options before submitting a bug report? |