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

CheckPoint Exam 156-585 Topic 6 Question 69 Discussion

Actual exam question for CheckPoint's 156-585 exam
Question #: 69
Topic #: 6
[All 156-585 Questions]

You need to run a kernel debug over a longer period of time as the problem occurs only once or twice a week. Therefore, you need to add a timestamp to the kernel debug and write the output to a file but you can't afford to fill up all the remaining disk space and you only have 10 GB free for saving the debugs. What is the correct syntax for this?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Kattie
2 months ago
B, definitely. Gotta love that redirect action – it's like the duct tape of the tech world. Just don't forget to put a little duct tape on the hard drive too, just in case!
upvoted 0 times
Selma
5 days ago
User 3: Selma, good point about the duct tape analogy. Always good to have a backup plan!
upvoted 0 times
...
Fatima
8 days ago
User 2: Fatima, you're right! Redirecting output to a file is the way to go.
upvoted 0 times
...
Angelo
14 days ago
Tarra: Will do, thanks for the reminder!
upvoted 0 times
...
Leota
18 days ago
User 3: Tarra, make sure you monitor that disk space though.
upvoted 0 times
...
Daisy
1 months ago
User 1: B) fw ctl kdebug -T -f -m 10 -s 1000000 > debugfilename
upvoted 0 times
...
Tarra
1 months ago
User 2: Yeah, redirecting output is the way to go.
upvoted 0 times
...
Shawnda
1 months ago
User 1: B) fw ctl kdebug -T -f -m 10 -s 1000000 > debugfilename
upvoted 0 times
...
...
Belen
2 months ago
Option B, huh? Sounds like the way to go. Just gotta make sure I don't typo the filename or else I'll be the one who has to explain to the team why the server's been down for days. Wouldn't want to be that guy, that's for sure!
upvoted 0 times
...
Antonio
2 months ago
Ah, the old kernel debug conundrum. B looks like the way to go, but I'm going to triple-check that syntax just to be safe. Can't have the server crashing on my watch because I couldn't follow a simple command, you know?
upvoted 0 times
...
Eleonore
2 months ago
Option B, eh? Sounds like it'll do the trick. I'm just glad I don't have to worry about running out of space. Wouldn't want to be the one who has to explain to the boss why the server's down because I ran out of disk space, am I right?
upvoted 0 times
...
Fausto
2 months ago
Hmm, well I'll be. B looks like the way to go, but I'd better double-check the syntax just to be sure I don't end up filling up the whole hard drive. Wouldn't want to be the one who brings the server down for a week just because I couldn't read the manual properly.
upvoted 0 times
Helga
1 months ago
User2: Yeah, I agree. Let's double-check just to be safe.
upvoted 0 times
...
Carmen
1 months ago
User1: I think B is the correct syntax for that.
upvoted 0 times
...
...
Osvaldo
2 months ago
But option B will overwrite the file each time, while option A will append to the file and prevent it from filling up the disk space.
upvoted 0 times
...
Svetlana
2 months ago
I disagree, I believe the correct syntax is B) fw ctl kdebug -T -f -m 10 -s 1000000 > debugfilename.
upvoted 0 times
...
Osvaldo
3 months ago
I think the correct syntax is A) fw ctl kdebug -T -f -m 10 -s 1000000 -o debugfilename.
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