Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

IBM Exam S1000-007 Topic 6 Question 40 Discussion

Contribute your Thoughts:

Natalie
2 months ago
Ah, the age-old question of how to check system tunables. I say we just unplug the server and see what happens. That's the real test of a good admin!
upvoted 0 times
...
Dorthy
2 months ago
I'm torn between C and D, but I think D is the way to go. Who wants to run a bunch of random commands just to find out what changed?
upvoted 0 times
Van
27 days ago
Yeah, I don't want to run unnecessary commands either. Let's go with D.
upvoted 0 times
...
Ria
1 months ago
I agree, D seems like the most efficient option.
upvoted 0 times
...
...
Vanda
2 months ago
Haha, tunsave -f ./currentconfig? That's like saving your homework in a file called 'currenthomework'. I'm definitely not picking that one!
upvoted 0 times
Camellia
1 months ago
Yeah, let's go with option B.
upvoted 0 times
...
Giovanna
1 months ago
I think we should check the /etc/tunables/currentconfig file instead.
upvoted 0 times
...
Eladia
2 months ago
User 1: I agree, that option sounds too obvious.
upvoted 0 times
...
...
Chantay
2 months ago
Option B seems like a straightforward way to check the changes in the system tunables. I'm going with that.
upvoted 0 times
Aimee
29 days ago
Option B does seem like a straightforward method to track system tunable changes.
upvoted 0 times
...
Filiberto
1 months ago
User 3: I prefer option A, running tunsave -f ./currentconfig; more ./currentconfig.
upvoted 0 times
...
Darrel
1 months ago
User 2: I agree, viewing the /etc/tunables/currentconfig file and searching for change marks seems efficient.
upvoted 0 times
...
Mollie
2 months ago
User 1: I think option B is the best way to check for changes in system tunables.
upvoted 0 times
...
...
Otis
2 months ago
I would go with option D, using lstuncfg to find changed tunables.
upvoted 0 times
...
Malcom
2 months ago
I think the correct answer is D. The lstuncfg -l | grep -v DEFAULT command will show the system tunables that have been changed from their default values.
upvoted 0 times
Rickie
1 months ago
That's good to know. Thanks for the information!
upvoted 0 times
...
Gilberto
1 months ago
Yes, you are right. Running lstuncfg -l | grep -v DEFAULT will show the changed system tunables.
upvoted 0 times
...
Oretha
2 months ago
I think the correct answer is D.
upvoted 0 times
...
Helene
2 months ago
Thanks for the clarification!
upvoted 0 times
...
Karan
2 months ago
Yes, you are right. Running lstuncfg -l | grep -v DEFAULT will show the changed system tunables.
upvoted 0 times
...
Bobbye
2 months ago
I think the correct answer is D.
upvoted 0 times
...
...
Viva
3 months ago
I'm not sure, but I think option A could also work.
upvoted 0 times
...
Deane
3 months ago
I agree with Ben, checking the /etc/tunables/currentconfig file makes sense.
upvoted 0 times
...
Ben
3 months ago
I think the answer is B.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77