Package Details: modprobed-db 2.46-1

Git Clone URL: https://aur.archlinux.org/modprobed-db.git (read-only, click to copy)
Package Base: modprobed-db
Description: Keeps track of EVERY kernel module ever used - useful for make localmodconfig
Upstream URL: https://wiki.archlinux.org/index.php/Modprobed-db
Licenses: MIT
Conflicts: modprobed_db
Replaces: modprobed_db
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 256
Popularity: 0.38
First Submitted: 2013-11-15 22:21 (UTC)
Last Updated: 2022-05-05 18:47 (UTC)

Latest Comments

1 2 3 4 5 6 .. 15 Next › Last »

xiota commented on 2023-09-20 09:01 (UTC)

Please remove replaces directive. Thank you. (No need to reply via comment; AUR now sends commit notifications.)

ezkha commented on 2023-04-15 16:37 (UTC) (edited on 2023-05-18 16:49 (UTC) by ezkha)

Fixed: See issue #19. This user error can really apply to any package. Be careful people.

When running trying to enable the user unit, I keep getting Failed to enable unit: Unit file $HOME/.config/systemd/default.target.wants/modprobed-db.service.

I noticed that the default.target.wants directory isn't created. I can still successfully manually start the user service.

graysky commented on 2020-07-06 09:54 (UTC)

@merlock - The reboot logic is the ExecStop= line should be allowing the call when the service is stopped.

merlock commented on 2020-07-06 03:33 (UTC)

@graysky:

v2.44 fixed it.

Note that I did a drop-in override to change the interval from 6h to 1h. Is that going to have an effect the 'on reboot' logic?

graysky commented on 2020-07-05 20:08 (UTC)

@merlock - Thanks for pointing it out/not by design. Should be fixed in v2.44. Please try it.

merlock commented on 2020-07-05 13:49 (UTC) (edited on 2020-07-05 13:56 (UTC) by merlock)

@graysky:

Noticed that v2.43 doesn't seem to set up a persistent timer.

NEXT LEFT LAST PASSED UNIT ACTIVATES
n/a n/a Sun 2020-07-05 09:38:49 EDT 1s ago modprobed-db.timer modprobed-db.service

Is this now by design?

bugsmanagement commented on 2018-11-25 02:28 (UTC) (edited on 2018-11-25 02:30 (UTC) by bugsmanagement)

@graysky

Ahh, look over once more, the magic happens here:

"sort -k 1,1 "$DB" /tmp/.inmem | uniq > /tmp/.potential_new_db"

Missed it the first time and focused a bit too much on "cp /tmp/.potential_new_db "$DB"" :)

graysky commented on 2018-11-23 11:10 (UTC)

@bugsmanagement - It does not overwrite. Try the experiment: load your module, update, rmmod, update. It's still there.

bugsmanagement commented on 2018-11-22 22:20 (UTC)

Forgive me for my lack of understanding, but looking over your script, it appears to me that it overwrites than updates the database? What I worry about, ie, I connect to my VPN provider, which accordingly loads the tun module, modprobed-db updates the database. Coincidentally after reboot, tun module is not loaded, modprobed-db then polls, see no tun module, and overwrites the database omitting the tun module?

1 2 3 4 5 6 .. 15 Next › Last »