http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5761
------- Additional Comments From [EMAIL PROTECTED] 2007-12-31 19:08 -------
(In reply to comment #22)
> Ok, so if I understand it correctly
if you DO, please fill ME in, cuz, networking between-n-betwixt fbsd jails seems
to be ~ 33% voudou :-/ at least, available info/expertise is a bit sparse ...
> you are trying to install spamassassin on
> JAIL, that's where make test fails, and you can't run netstat -nr on that
> machine so we still don't know if there is something funky with the routing to
> 127.0.0.1 there. Is there anything besides netstat that you can run on JAIL to
> see what the route is to 127.0.0.1? Perhaps traceroute 127.0.0.1 would do it?
well, fwiw, @JAIL
traceroute 127.0.0.1
traceroute to 127.0.0.1 (127.0.0.1), 64 hops max, 52 byte packets
1 localhost (127.0.0.1) 0.270 ms 0.093 ms 0.103 ms
is that what you're looking for?
> Are there any lines in /etc/rc.conf on JAIL that say anything about 127.0.0.1?
alas, nope
egrep "127|localhost" /etc/rc.conf
(empty)
just in case, again note that spamd runs/operates in the jail ... just the tests
are failing.
also, googl'ing on routing/jails/freebsd, i note, e.g., @
http://www.securitytracker.com/alerts/2004/Jun/1010412.html
"A vulnerability was reported in jail(2) in the FreeBSD kernel. Jailed processes
may be able to modify host routing tables."
This reminds me that jailed procs should not, of course, mod the router tables.
Now, my naive question is ... are the tests, in spawning, or attempting to
spawn, new proces withing the jail, attemptin -- and failing -- to make such
router table mods?
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.