- All Exams Instant Download
After kernel debug with "fw ctl debug" you received a huge amount of information It was saved in a very large file that is difficult to open and analyze with standard text editors Suggest a solution to solve this issue.
After kernel debug with "fw ctl debug" you received a huge amount of information It was saved in a very large file that is difficult to open and analyze with standard text editors Suggest a solution to solve this issue.
A . Use "fw ctl zdebug’ because of 1024KB buffer size
B . Divide debug information into smaller files Use "fw ctl kdebug -f -o "filename" -m 25 – s "1024"
C . Reduce debug buffer to 1024KB and run debug for several times
D . Use Check Point InfoView utility to analyze debug output
Answer: B
Latest 156-585 Dumps Valid Version with 75 Q&As
Latest And Valid Q&A | Instant Download | Once Fail, Full Refund
B is correct: kdebug is used for collecting the debug data. Correct syntax for kdebug is this:
fw ctl kdebug [-p <<em>List of Fields</em>>] [-T] -f -o /<<em>Path</em>>/<<em>Name of Output File</em>> -m <<em>Number of Cyclic Files</em>> [-s <<em>Size of Each Cyclic File in KB</em>>]I think B is correct:
Dividing the debug output file into multiple file limited to certain size:
[Expert@HostName]# fw ctl kdebug -f -o -m -s
I agree that B can’t be the answer here, however A is not correct either as A related to ‘fw ctl zdebug’ and not fw ctl debug as stated in the question, therefore in my option the correct answer here is C.
I think the answer is A
The command for B isn’t even valid “fw ctl kdebug -f -o “filename” -m 25 – s “1024” (you’d use the -m flag to denote the module, not a number, and -buf rather than -s to define the buffer size)