Thomas Liske

Please be aware of the description in `notify.d/README.md` (regarding `600-mail`): ``` Files located in /etc/needrestart/notify.d are used to notify running user sessions about usage of outdated libraries. ``` Needrestart has...

It looks like needrestart is running in nagios plugin mode. This should only happen if needrestart is run with the `-p` parameter. Can you check how it is called?

> I've found an interesting patch by diffing Ubuntu's version of needrestart between 20.04 (reportedly working) and 22.04 (reportedly not working): > > ``` > cat debian/patches/168.patch > From e74dfa6950a298419ffa7a21858f9c1686716f58...

I'm going to close this issue since it's seems not to be an upstream issue.

Does this only happen when running needrstart as non-root? Do you have any special filesystem setup?

Thesis: the overflay might be the trigger. Needrestart checks the device and inode stats info from the filesystem with the values provided in `/proc/$PID/maps`. I'm going to reproduce and debug...

I've wrote a little script containing most of needrestart's inode validation logic. Could you please give it a try? The script expects a lines from `/proc/$PID/maps`, please use the lines...

> Hello, thanks a lot for looking into this! > > I saved your script as `test.pl` and executed the following commands: > > ``` > needrestart -v -m a...

There is no need to create a new option. You can add a pattern to the `blacklist_mappings` option. Maybe any path containing a `.cache` component should be ignored :thinking:

You can add `wsdd` to the `blacklist` option (using it's absolute path). To debug why needrestart decides that `wsdd` should always be restarted you can run `needrestart -vrl`.