From: Robert Vangel <vangelr@rfgt.net>
To: netfilter@lists.netfilter.org
Subject: Re: sysctl vs. echo > /proc...
Date: Tue, 31 May 2005 16:24:52 +0800 [thread overview]
Message-ID: <429C1F54.1030000@rfgt.net> (raw)
In-Reply-To: <429BFCCA.9010505@riverviewtech.net>
[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]
Taylor, Grant wrote:
> Hey fellow TuX users out there, I have a question for you.
>
> Does any one know the (technical) difference in using sysctl verses
> echoing values in to the appropriate areas in side of the /proc file
> system? Which is the more current (expected in the future) practice?
> Any ideas and / or thoughts on this matter would be greatly
> appreciated. Consider this very simple and common example:
>
> sysctl -w net.ipv4.ip_forward=1
>
> verses
> echo "1" > /proc/sys/net/ipv4/ip_forward
>
>
> Grant. . . .
>
I don't think there is any real different between the two methods.
Really calling sysctl to do it is just another step when using echo
would do it anyway.
On the other hand, if sysctl can be used to log anything so you can
possibly reverse any changes may be an idea, but the only things I have
ever changed (that I can think of) in /proc are ip_forward and
tcp_conntrack_max, which have been with an echo and then editing
/etc/sysctl.conf to match.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3166 bytes --]
prev parent reply other threads:[~2005-05-31 8:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 5:57 sysctl vs. echo > /proc Taylor, Grant
2005-05-31 8:24 ` Robert Vangel [this message]
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=429C1F54.1030000@rfgt.net \
--to=vangelr@rfgt.net \
--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.