1PROGRESS(1) General Commands Manual PROGRESS(1)
2
3
4
6 progress - Coreutils Progress Viewer
7
9 progress [ -qdwmM ] [ -W secs ] [ -c command ] [ -a command ] [ -p pid
10 ]
11 progress -v | --version
12 progress -h | --help
13
14
16 This manual page briefly documents the progress command.
17
18 This tool can be described as a Tiny, Dirty, Linux-Only C command that
19 looks for coreutils basic commands (cp, mv, dd, tar, gzip/gunzip, cat,
20 etc.) currently running on your system and displays the percentage of
21 copied data.
22
23 It can now also estimate throughput (using flag -w).
24
25
27 -q (--quiet)
28 hides all messages
29
30 -d (--debug)
31 shows all warning/error messages
32
33 -w (--wait)
34 estimate I/O throughput and estimated remaining time (slower
35 display)
36
37 -W (--wait-delay secs)
38 wait 'secs' seconds for I/O estimation (implies -w)
39
40 -m (--monitor)
41 loop while monitored processes are still running
42
43 -M (--monitor-continuously)
44 like monitor but never stop (similar to watch progress)
45
46 -c (--command cmd)
47 monitor only this command name (ex: firefox). This option can be
48 used multiple times on the command line.
49
50 -a (--additional-command cmd)
51 add this command to the default list. This option can be used
52 multiple times on the command line.
53
54 -p (--pid id)
55 monitor only this numeric process ID (ex: `pidof firefox`). This
56 option can be used multiple times on the command line.
57
58 -i (--ignore-file file)
59 do not report a process for 'file'. If the file does not exist
60 yet, you must give a full and clean absolute path. This option
61 can be used multiple times on the command line.
62
63 -o (--open-mode {r|w})
64 report only files opened for read or write by the process. This
65 option is useful when you want to monitor only output files (or
66 input ones) of a process.
67
68 -v (--version)
69 show program version and exit
70
71 -h (--help)
72 display help message and exit
73
74
76 It's possible to give permanent options using PROGRESS_ARGS environment
77 variable. See example below. Command line arguments take precedence
78 over environment.
79
80
82 Continuously monitor all current and upcoming instances of coreutils
83 commands
84
85 watch progress -q
86
87 See how your download is progressing
88
89 watch progress -wc firefox
90
91 Look at your Web server activity
92
93 progress -c httpd
94
95 Launch and monitor any heavy command using $!
96
97 cp bigfile newfile & progress -mp $!
98
99
100 Use environment variable to set permanent (multiple) arguments
101
102 export PROGRESS_ARGS='-M --ignore-file ~/.xsession-errors'
103
104
106 Please report bugs at: http://github.com/Xfennec/progress/issues
107
108
110 http://github.com/Xfennec/progress
111
112
114 This manual page was written by Thomas Zimmermann <bugs@vdm-design.de>,
115 for the openSUSE project (and may be used by others).
116
117
118
119progress January 22, 2016 PROGRESS(1)