From: <techmail@safe2surf.nl>
To: netfilter@lists.netfilter.org
Subject: Debugging
Date: Mon, 20 Oct 2003 00:24:12 +0200 [thread overview]
Message-ID: <002801c3968f$b95b8b60$0501a8c0@robert> (raw)
[-- Attachment #1: Type: text/plain, Size: 437 bytes --]
Hi,
Perhaps this is a stupid question which has been asked too many times,
but I wasn't able to find it.
If I do "service iptables start" nothing happens, so when I do "service
iptables status" it says "Firewall is stopped."
Because I want to know where in the process the error is I'd like to
know how to debug it. Is there any information on debugging to see what
error it displays?
Kind regards,
Robert Hazenveld
[-- Attachment #2: Type: text/html, Size: 2663 bytes --]
next reply other threads:[~2003-10-19 22:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-19 22:24 techmail [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-29 6:21 Debugging James Colannino
2006-01-29 16:21 ` Debugging Steve Graegert
2006-01-29 18:14 ` Debugging Glynn Clements
2006-01-30 19:09 ` Debugging James Colannino
[not found] ` <20060129105131.6813f695.leslie.polzer@gmx.net>
2006-01-30 19:13 ` Debugging James Colannino
2006-01-30 19:21 ` Debugging James Colannino
2005-09-09 12:40 Debugging Lares Moreau
2005-09-09 15:30 ` Debugging Randy.Dunlap
2005-05-14 0:05 Debugging Scott Becker
2005-05-17 2:11 ` Debugging Hollis Blanchard
2005-05-18 15:59 ` Debugging Scott Becker
2005-08-29 15:12 ` Debugging pjones
[not found] <09B04A55822EFF4DA48D2E0BB2941D4A15C51F@wardrive.citadelcomputer.com.au>
2003-10-19 23:26 ` Debugging techmail
2003-10-19 22:45 Debugging Daniel Chemko
2003-10-09 7:23 debugging Ingo Flaschberger
2003-03-11 11:05 bug in asm-ppc/div64.h Bastien Nocera
2003-03-11 14:21 ` Debugging Giuliano Pochini
2003-03-11 19:28 ` Debugging Olaf Hering
2003-03-13 8:28 ` Debugging Giuliano Pochini
2003-03-13 8:52 ` Debugging Olaf Hering
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='002801c3968f$b95b8b60$0501a8c0@robert' \
--to=techmail@safe2surf.nl \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.