On Fri, 2004-03-26 at 18:53, Costas Magkos wrote:
[...]
> Is there a way to test whether a chroot works? Does anyone know if the
> above syslog option is really needed? According to the man page of
> syslog it is needed.
use lsof
# lsof -p [pid number of bind process]
check:
- if the loaded l
On Fri, 2004-03-26 at 18:53, Costas Magkos wrote:
[...]
> Is there a way to test whether a chroot works? Does anyone know if the
> above syslog option is really needed? According to the man page of
> syslog it is needed.
use lsof
# lsof -p [pid number of bind process]
check:
- if the loaded l
On Tue, 2003-03-18 at 16:04, debian-security wrote:
> >
> >check out flowscan
> >
> >http://www.caida.org/tools/utilities/flowscan/
> >
> >it gets close to what you want, assuming all the traffic is
> >passing through a cisco router.
A better choice (IMHO) would be flow-tools at
http://www.spl
On Tue, 2003-03-18 at 16:04, debian-security wrote:
> >
> >check out flowscan
> >
> >http://www.caida.org/tools/utilities/flowscan/
> >
> >it gets close to what you want, assuming all the traffic is
> >passing through a cisco router.
A better choice (IMHO) would be flow-tools at
http://www.spl
that
the 'standard' debian method of using a chroot environment (the link
from my original post) is moving the libraries into the chroot
environment and not using them.
--
J.J. van GorkumKnowledge Zone
--
If UNIX isn't the solution, you've got the wrong problem.
gt; that variable and you should be ok. I've done this with Bind 8, and now
> upgraded them to 9.
You are missing the point here, if I do it the way bind tells me in the
man pages bind is NOT using the libraries inside the chroot environment.
That is wat I try to proove with the lsmod
that
the 'standard' debian method of using a chroot environment (the link
from my original post) is moving the libraries into the chroot
environment and not using them.
--
J.J. van GorkumKnowledge Zone
--
If UNIX isn't the solution, you've got the
gt; that variable and you should be ok. I've done this with Bind 8, and now
> upgraded them to 9.
You are missing the point here, if I do it the way bind tells me in the
man pages bind is NOT using the libraries inside the chroot environment.
That is wat I try to proove with the lsmod
5239779 TCP
localhost:domain (LISTEN)
Look at the difference in the libraries, as I can see when I start named
as stated in the script the libraries in the chrooted environment are
not used
Am I wrong here?
--
J.J. van GorkumKnowledge Zone
--
If UNIX
5239779 TCP
localhost:domain (LISTEN)
Look at the difference in the libraries, as I can see when I start named
as stated in the script the libraries in the chrooted environment are
not used
Am I wrong here?
--
J.J. van GorkumKnowledge Zone
--
If UNIX
10 matches
Mail list logo