A technician is capturing show command output into a session log for a change ticket after a rural ISP's overnight maintenance window and does not want the CLI pausing output with a --More-- prompt partway through a long listing. Which pipe modifier prevents that pagination?
Select an answer to reveal the explanation.
Short Explanation
That --More-- prompt is handy when you're reading interactively, but it's a nuisance when you're just trying to capture clean output into a log. Tack on no-more and Junos dumps the whole thing at once, no interruptions.
Full Explanation
The no-more pipe modifier disables the CLI's default interactive pagination, which normally pauses long output at each screen and waits for a keypress before continuing; appending it causes the full result to print in one continuous stream, which is exactly what's wanted when the goal is a clean, uninterrupted capture for a session log or ticket record. Count is unrelated to pagination behavior; it discards the actual output entirely and reports only a total line count, which would defeat the purpose of capturing the detailed listing at all. Last only trims the output to a specified number of trailing lines, which could still trigger pagination if that trimmed output remains long, and it changes what content appears rather than how it's displayed. Find repositions the start of displayed output to the first match of a search string but does not affect whether pagination occurs afterward. A closely related setting worth knowing is the terminal length configuration option, which can disable pagination for an entire session rather than one command at a time, useful when many commands need capturing in a row during the same maintenance window.