Mixing
sysctl command returning info not asked about
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
I want to grep a particular kernel setting as follows
$ sudo sysctl -a --ignore | grep -i max_map_count 2>/dev/null
sysctl: reading key "net.ipv6.conf.all.stable_secret"
sysctl: reading key "net.ipv6.conf.default.stable_secret"
sysctl: reading key "net.ipv6.conf.docker0.stable_secret"
sysctl: reading key "net.ipv6.conf.enp2s0.stable_secret"
sysctl: reading key "net.ipv6.conf.lo.stable_secret"
sysctl: reading key "net.ipv6.conf.wlp3s0.stable_secret"
vm.max_map_count = 262144
Since I am both ignoring info about unknown keys (i.e. the --ignore option) and redirecting potential error output to /dev/null, what are these reading jey lines printed?
io-redirection sysctl
asked 5 hours ago
pkaramol
396113
add a comment |Â
up vote
1
down vote
favorite
I want to grep a particular kernel setting as follows
$ sudo sysctl -a --ignore | grep -i max_map_count 2>/dev/null
sysctl: reading key "net.ipv6.conf.all.stable_secret"
sysctl: reading key "net.ipv6.conf.default.stable_secret"
sysctl: reading key "net.ipv6.conf.docker0.stable_secret"
sysctl: reading key "net.ipv6.conf.enp2s0.stable_secret"
sysctl: reading key "net.ipv6.conf.lo.stable_secret"
sysctl: reading key "net.ipv6.conf.wlp3s0.stable_secret"
vm.max_map_count = 262144
Since I am both ignoring info about unknown keys (i.e. the --ignore option) and redirecting potential error output to /dev/null, what are these reading jey lines printed?
io-redirection sysctl
asked 5 hours ago
pkaramol
396113
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I want to grep a particular kernel setting as follows
$ sudo sysctl -a --ignore | grep -i max_map_count 2>/dev/null
sysctl: reading key "net.ipv6.conf.all.stable_secret"
sysctl: reading key "net.ipv6.conf.default.stable_secret"
sysctl: reading key "net.ipv6.conf.docker0.stable_secret"
sysctl: reading key "net.ipv6.conf.enp2s0.stable_secret"
sysctl: reading key "net.ipv6.conf.lo.stable_secret"
sysctl: reading key "net.ipv6.conf.wlp3s0.stable_secret"
vm.max_map_count = 262144
Since I am both ignoring info about unknown keys (i.e. the --ignore option) and redirecting potential error output to /dev/null, what are these reading jey lines printed?
io-redirection sysctl
asked 5 hours ago
pkaramol
396113
I want to grep a particular kernel setting as follows
$ sudo sysctl -a --ignore | grep -i max_map_count 2>/dev/null
sysctl: reading key "net.ipv6.conf.all.stable_secret"
sysctl: reading key "net.ipv6.conf.default.stable_secret"
sysctl: reading key "net.ipv6.conf.docker0.stable_secret"
sysctl: reading key "net.ipv6.conf.enp2s0.stable_secret"
sysctl: reading key "net.ipv6.conf.lo.stable_secret"
sysctl: reading key "net.ipv6.conf.wlp3s0.stable_secret"
vm.max_map_count = 262144
Since I am both ignoring info about unknown keys (i.e. the --ignore option) and redirecting potential error output to /dev/null, what are these reading jey lines printed?
io-redirection sysctl
io-redirection sysctl
asked 5 hours ago
pkaramol
396113
asked 5 hours ago
pkaramol
396113
asked 5 hours ago
pkaramol
396113
asked 5 hours ago
pkaramol
396113
asked 5 hours ago
pkaramol
396113
396113
add a comment |Â
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
6
down vote
accepted
You are redirecting the stderr of the grep to /dev/null but the stderr messages are coming from sysctl. Try
sudo sysctl -a --ignore 2>/dev/null | grep -i max_map_count
answered 5 hours ago
Doug O'Neal
2,7521716
add a comment |Â
up vote
3
down vote
An explanation of the stable_secrect messages can be found here. In short, the keys exist but are not initialized causing the message.
Concerning your actual command and goal, the pipe | only redirects stdout not stderr which is printed before the rest is sent to the pipe.
To have the expected behaviour you could use one of the commands as follows.
sudo sysctl -a --ignore 2> /dev/null | grep max_map_count
sudo sysctl -a --ignore 2>&1 | grep max_map_count
sudo sysctl -a --ignore |& grep max_map_count
Alternatively you also could use find.
find /proc/sys -name '*max_map_count*' -exec grep -H . "" ;
Better would be, as you already know what you are searching for.
sysctl vm.max_map_count
answered 5 hours ago
Thomas
3,67141225
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
6
down vote
accepted
You are redirecting the stderr of the grep to /dev/null but the stderr messages are coming from sysctl. Try
sudo sysctl -a --ignore 2>/dev/null | grep -i max_map_count
answered 5 hours ago
Doug O'Neal
2,7521716
add a comment |Â
up vote
6
down vote
accepted
You are redirecting the stderr of the grep to /dev/null but the stderr messages are coming from sysctl. Try
sudo sysctl -a --ignore 2>/dev/null | grep -i max_map_count
answered 5 hours ago
Doug O'Neal
2,7521716
add a comment |Â
up vote
6
down vote
accepted
up vote
6
down vote
accepted
You are redirecting the stderr of the grep to /dev/null but the stderr messages are coming from sysctl. Try
sudo sysctl -a --ignore 2>/dev/null | grep -i max_map_count
answered 5 hours ago
Doug O'Neal
2,7521716
You are redirecting the stderr of the grep to /dev/null but the stderr messages are coming from sysctl. Try
sudo sysctl -a --ignore 2>/dev/null | grep -i max_map_count
answered 5 hours ago
Doug O'Neal
2,7521716
answered 5 hours ago
Doug O'Neal
2,7521716
answered 5 hours ago
Doug O'Neal
2,7521716
answered 5 hours ago
Doug O'Neal
2,7521716
2,7521716
add a comment |Â
add a comment |Â
up vote
3
down vote
An explanation of the stable_secrect messages can be found here. In short, the keys exist but are not initialized causing the message.
Concerning your actual command and goal, the pipe | only redirects stdout not stderr which is printed before the rest is sent to the pipe.
To have the expected behaviour you could use one of the commands as follows.
sudo sysctl -a --ignore 2> /dev/null | grep max_map_count
sudo sysctl -a --ignore 2>&1 | grep max_map_count
sudo sysctl -a --ignore |& grep max_map_count
Alternatively you also could use find.
find /proc/sys -name '*max_map_count*' -exec grep -H . "" ;
Better would be, as you already know what you are searching for.
sysctl vm.max_map_count
answered 5 hours ago
Thomas
3,67141225
add a comment |Â
up vote
3
down vote
An explanation of the stable_secrect messages can be found here. In short, the keys exist but are not initialized causing the message.
Concerning your actual command and goal, the pipe | only redirects stdout not stderr which is printed before the rest is sent to the pipe.
To have the expected behaviour you could use one of the commands as follows.
sudo sysctl -a --ignore 2> /dev/null | grep max_map_count
sudo sysctl -a --ignore 2>&1 | grep max_map_count
sudo sysctl -a --ignore |& grep max_map_count
Alternatively you also could use find.
find /proc/sys -name '*max_map_count*' -exec grep -H . "" ;
Better would be, as you already know what you are searching for.
sysctl vm.max_map_count
answered 5 hours ago
Thomas
3,67141225
add a comment |Â
up vote
3
down vote
up vote
3
down vote
An explanation of the stable_secrect messages can be found here. In short, the keys exist but are not initialized causing the message.
Concerning your actual command and goal, the pipe | only redirects stdout not stderr which is printed before the rest is sent to the pipe.
To have the expected behaviour you could use one of the commands as follows.
sudo sysctl -a --ignore 2> /dev/null | grep max_map_count
sudo sysctl -a --ignore 2>&1 | grep max_map_count
sudo sysctl -a --ignore |& grep max_map_count
Alternatively you also could use find.
find /proc/sys -name '*max_map_count*' -exec grep -H . "" ;
Better would be, as you already know what you are searching for.
sysctl vm.max_map_count
answered 5 hours ago
Thomas
3,67141225
An explanation of the stable_secrect messages can be found here. In short, the keys exist but are not initialized causing the message.
Concerning your actual command and goal, the pipe | only redirects stdout not stderr which is printed before the rest is sent to the pipe.
To have the expected behaviour you could use one of the commands as follows.
sudo sysctl -a --ignore 2> /dev/null | grep max_map_count
sudo sysctl -a --ignore 2>&1 | grep max_map_count
sudo sysctl -a --ignore |& grep max_map_count
Alternatively you also could use find.
find /proc/sys -name '*max_map_count*' -exec grep -H . "" ;
Better would be, as you already know what you are searching for.
sysctl vm.max_map_count
answered 5 hours ago
Thomas
3,67141225
answered 5 hours ago
Thomas
3,67141225
answered 5 hours ago
Thomas
3,67141225
answered 5 hours ago
Thomas
3,67141225
3,67141225
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f473660%2fsysctl-command-returning-info-not-asked-about%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password