1wmudmount(1) General Commands Manual wmudmount(1)
2
6 wmudmount - A WindowMaker filesystem mounting dockapp using udisks
7
9 wmdgumount [options]
10
12 wmudmount is a filesystem mounter that uses udisks to handle notifica‐
13 tion of new volumes and mounting of the filesystems as a non-root user.
14 It also includes a mode to display the mounted filesystems with the
15 least free space percentage (similar to wmfsm).
16
18 --help Display usage information.
19 -V, --version
21 Display the version number and exit.
22 --no-default-config
24 Prevent reading of the default configuration files.
25 --conf <filename>
27 Specify a configuration file to use in addition to the default.
28 -v, --verbose
30 Print more messages to the console. May be repeated.
31 -q, --quiet
33 Print fewer messages to the console. May be repeated.
34 -n, --notify <level>
36 Specify what level of notification to display (using the desktop
37 notification service). Valid levels are:
38 none - No messages
40 error - Only provide failure messages, e.g. "Mount failed"
41 warn - Only provide failure and warning messages
42 info - Provide informational messages, e.g. "Device added"
43 (default)
44 --exclude-system-volumes, --include-system-volumes
46 --fsm-exclude-system-volumes, --fsm-include-system-volumes
47 --pager-exclude-system-volumes, --pager-include-system-volumes
48 Whether to include volumes in the paging list and/or the FSM
49 display that require the administrator authorization for mount‐
50 ing (i.e. those reported as "system internal" by udisks and
51 those listed in fstab without the "user" option).
52 --return-to-fsm-timeout <seconds>
54 Specify the number of seconds the mouse pointer must be away
55 from the dockapp before the display changes back to the FSM
56 view. The default is 60, set negative to disable.
57 --allow-insecure-memory, --no-allow-insecure-memory
59 Normally, the password dialog will insist that secure memory be
60 allocated to hold the entered password; this can prevent the
61 password from being written to swap in a low-memory situation.
62 If your system does not allow users to allocate secure memory,
63 you can use --allow-insecure-memory to allow the use of normal,
64 insecure memory.
65 --allow-core-files, --no-allow-core-files
67 The dumping of core files is disabled so entered passwords will
68 not be written to disk if a coredump signal is received. Nor‐
69 mally, the program will exit if this cannot be done; if neces‐
70 sary, --allow-core-files may be used to allow execution despite
71 the risk.
72 --blink-full-filesystems, --no-blink-full-filesystems
74 Normally, the "disk space used" bar for a read-write filesystem
75 will blink when it is over 95% full. --no-blink-full-filesystems
76 may be used to prevent this.
77 --non-wmaker
79 Create windows differently, in a manner more friendly to non-
80 Window Maker window managers. If you wind up with both a docked
81 icon and an unmanaged window, try setting this.
82
84 The configuration files may contain the following options:
85 verbose
87 quiet
88 non-wmaker
89 notify = <level>
90 exclude-system-volumes
91 include-system-volumes
92 fsm-exclude-system-volumes
93 fsm-include-system-volumes
94 pager-exclude-system-volumes
95 pager-include-system-volumes
96 return-to-fsm-timeout = <seconds>
97 allow-insecure-memory
98 no-allow-insecure-memory
99 allow-core-files
100 no-allow-core-files
101 blink-full-filesystems
102 no-blink-full-filesystems
103 Same as the corresponding command line options.
104 warn = <level>
106 Sets the verbosity level, error, warn (default), info, or debug.
107 command = <command-spec>
109 Allows adding arbitrary commands to the right-click menu. A com‐
110 mand-spec is of the form title;command. The command is NOT
111 passed through the shell, but the search path is used. The fol‐
112 lowing printf-style escapes may be used:
113 %p - The udisks dbus path for the device
115 %d - The /dev path for the device
116 %m - The mountpoint of the filesystem
117 %% - A literal "%"
118 If any of the above are not available (e.g. the filesystem is
120 not mounted), commands using them will be greyed-out in the
121 right-click menu.
122 For example, "command = Console; urxvt -cd %m" would create a
124 menu item that will open a terminal window at the filesystem's
125 mountpoint.
126 click-command = <command-spec>
128 Same as command, plus this command will be executed when click‐
129 ing a device in the display.
130 double-click-command = <command-spec>
132 Same as command, plus this command will be executed when double-
133 clicking a device in the display.
134 include-volume = <spec>
136 exclude-volume = <spec>
137 fsm-include-volume = <spec>
138 fsm-exclude-volume = <spec>
139 pager-include-volume = <spec>
140 pager-exclude-volume = <spec>
141 Allows for specificly identifying volumes to include or exclude
142 from the paging and/or the FSM display, overriding the general
143 behavior chosen by --include-system-volumes or --exclude-sys‐
144 tem-volumes.
145 The values for <spec> are similar to those for the first field
147 in /etc/fstab: If it begins with "LABEL=", the remainder of the
148 spec is matched against the volume's label. If it begins with
149 "UUID=", the remainder of the spec is matched against the vol‐
150 ume's UUID. Otherwise, the spec is matched against the volume's
151 device and current mountpoint.
152 If multiple include and exclude entries match a volume, the last
154 one wins. Specifying include-volume is equivalent to specifying
155 both fsm-include-volume and pager-include-volume (and similarly
156 for the exclude variants).
157
159 The dockapp consists of a display window, two "action" buttons on the
160 left, and two "paging" buttons on the right. The paging buttons are
161 used for paging through the available devices; the mouse scrollwheel
162 may also be used while over the dockapp for the same purpose. The
163 action buttons vary depending on which device is focused.
164 Hovering the mouse over the display will show a tooltip with informa‐
166 tion on the current device, and over the action buttons will show a
167 tooltip describing the button's action. Right-clicking the display
168 gives a popup menu with additional options for the current device. Mid‐
169 dle-clicking moves back to FSM mode.
170 The "default" mode is the FSM display. In this mode, the filesystem
172 usage information for all filesystems reported as mounted by udisks is
173 periodically queried and the 6 with the highest percentage used are
174 displayed, along with a bar indicating the percentage. If the percent‐
175 age is over 95%, the bar turns red and (optionally) blinks. The action
176 buttons are not used. If no click-command is set, clicking a filesystem
177 line will go to that device's page, if any.
178 The other mode is for displaying a device. In this mode, the top of the
180 display window shows the device label or /dev node name, with an icon
181 representing the device below. The right action button is used for
182 removing the media as applicable, e.g. locking a crypto device, eject‐
183 ing a CD, or detaching a USB stick for safe removal.
184 When displaying a filesystem device, the mountpoint and usage percent
186 bar (if mounted) are at the bottom of the display. The icon has a blue
187 background if the filesystem is mounted, or a red background if an
188 operation is currently in progress. The left action button is used to
189 mount or unmount the filesystem.
190 When displaying a locked crypto device, the type of the device (e.g.
192 "LUKS device") is displayed at the bottom. The left action button is
193 used to unlock the device; the passphrase will be loaded from the sys‐
194 tem keyring if possible, and you will be prompted if necessary.
195 The right-click menu gives access to a few additional actions, includ‐
197 ing relabeling a filesystem and forgetting a saved crypto device pass‐
198 word.
199
201 None yet.
202
204 /etc/wmudmount.conf
205 System configuration.
206 $HOME/.wmudmountrc
208 User configuration.
209
211 SIGUSR1
212 Perform the same action as clicking the left action button.
213 SIGUSR2
215 Perform the same action as clicking the right action button.
216 SIGRTMIN+0
218 Perform the same action as clicking the left paging button. To
219 find the expected signal number of SIGRTMIN+0, use the --verbose
220 option.
221 SIGRTMIN+1
223 Perform the same action as clicking the right paging button. To
224 find the expected signal number of SIGRTMIN+1, use the --verbose
225 option.
226
228 wmudmount was written by Brad Jorsch <anomie@users.sourceforge.net>.
229 Email regarding wmudmount should be sent to anomie@users.source‐
231 forge.net.
232 February 12, 2017 wmudmount(1)