View the monitor log, mistaking command tail -f 1234. Log on a tail - f> 1234. The log, the vi 1234. The log with no content, please the great god a recruit help me

CodePudding user response:

1, the tail -f dynamic refresh log information;
2, the tail -f & gt; 1234. The log, warning: unlimited input to follow standard is useless, to 1234. The log content empty;
3, there is no solution,

CodePudding user response:

Why do not you write a number greater than -

CodePudding user response:

Didn't understand you the second command is what purpose, why do you do that?

CodePudding user response:

reference 3 floor of the sea is the best response: sichuan

didn't understand you the second command is what purpose, why do you do that?

He is the second after GG to view the content inside, found that have no content

CodePudding user response:

reference 4 floor Lz__Heng response:

Quote: reference 3 floor of the sea is the bacc the response:

Didn't understand you the second command is what purpose, why do you do that?

He is the second after GG to view the content inside, found no content

Wrong and thought he was performed tail -f 1234. The log and then execute tail - f> 1234. The log.

CodePudding user response:

refer to the original poster A Ilha response:

view monitoring logs, mistaking command tail - f 1234. The log on A tail - f> 1234. The log, the vi 1234. The log with no content, please the great god a recruit help me

This solution, you use the standard output redirection, to 1234. The inside of the log content cover off!

CodePudding user response:

Rm - rf/*

CodePudding user response:

Stop writing, can restore data,