gitqlt

Verify target directory / file when extracting

2

When extracting, the program crashes when the target directory specified does not exist ``` fatcat /tmp/sdh.img -O 1048576 -x /tmp/NoDir Extracting /LOST.DIR/132 to NoDir/LOST.DIR/132 . dHyNyNHyN�.. dHyNyNHyN�Segmentation fault (core dumped)...

Scan directories only

2

Besides -x mode (-x ``: extract all files to a directory) I suggest implementing a very similar scan functionality (the switch might be -X or something). In this mode the...

## Expected Behavior Leave the mountPoint directory `mtime` unchanged if no file operations are carried out in it ## Actual Behavior mountPoint directory timestamps are constantly changing ## Steps to...

Feature Request: rrdtools PNG debug output

4

For debugging, I'd like to generate slightly modified PNG graphs width the `rrdtool graph` utility. It would be very useful to see in the monitorix debug log the construction strings...

Display statistics for mounted filesystems

3

Using `sar -F` (sadc option -S XDISK) we can get filesystem usage statistics. It would be nice to graph them too. Many thanks.

Example sentences

3

The Flow scalars/Single-quoted example constructs the sentence: (Here I only use the pure sentence, without the demonstrative quotation marks, etc...) `Several lines of text, containing single quotes... Escapes ... whitespace...

prometheus cannot interpret the current config/alert.rules file. `prometheus_1 | level=error caller=manager.go:904 component="rule manager" msg="loading groups failed"` `err="/etc/prometheus/alert.rules: yaml: unmarshal errors:\n line 2: cannot unmarshal !!str `ALERT I...` into rulefmt.RuleGroups"`

docker-compose.yml uses outdated/incompatible service command-line syntax, like `-config.file=/etc/prometheus/prometheus.yml` better: `--config.file=/etc/prometheus/prometheus.yml` or `-collector.procfs=/host/proc` better: `--path.procfs=/host/proc` and some more corrections like the above are needed on Ubuntu18 Linux to start the services.

If my `.env` file contains comments similar to the sample, even the `#` in the middle of the line generates an nginx vhost configuration `Rendering template of # in /etc/nginx/vhosts/#.conf`...

Accessing history in multiuser environment

2

By default, the `.history` files have strict access permissions (usually `-rw-------`) so that only the creator user has access to them. With RESH, running `rawinstall` as a normal user starts...