I discover when I blundered into firmware security, this was not
installed. I didn't find it in the package manager either.
This is a diversion of course. I found it looking for other stuff.
eg;
My kernel messages claim a fail for mdmonitor which seems to be for raid software, which I don't run.
So I went looking for that program which use to allow stopping, starting
and starting at boot of all processes.
I thought if there is a mdmonitor entry I'll just stop it.
I couldn't find that program.. Is it deprecated?
I discover when I blundered into firmware security, this was not
installed. I didn't find it in the package manager either.
This is a diversion of course. I found it looking for other stuff.
eg;
My kernel messages claim a fail for mdmonitor which seems to be for
raid software, which I don't run. So I went looking for that program
which use to allow stopping, starting and starting at boot of all
processes. I thought if there is a mdmonitor entry I'll just stop it.
I couldn't find that program.. Is it deprecated?
--
faeychild
Running kde on 6.6.74-desktop-1.mga9 kernel.
Mageia release 9 (Official) for x86_64
On 9/2/25 13:30, faeychild wrote:
I discover when I blundered into firmware security, this was not
installed. I didn't find it in the package manager either.
This is a diversion of course. I found it looking for other stuff.
eg;
My kernel messages claim a fail for mdmonitor which seems to be for raid
software, which I don't run.
So I went looking for that program which use to allow stopping, starting
and starting at boot of all processes.
I thought if there is a mdmonitor entry I'll just stop it.
I couldn't find that program.. Is it deprecated?
OK there is a similar deal (not as flexible) under "System Monitor > Processes"
It doesn't list mdmonitor.
I'm not playing this game today
This is another Sunday bypass.
I was passing by the computer and decided to stupidly check up on the
kernel ndmonitor message
And this morphed into a search of MGA6 to find "KSysguard" and then back
to MGA9 where it no longer exists and all this started.
Why do I do this to myself?? I'm walking away, really watch me. :-)
I've gone..........
# urpmf fwupdmgr|grep bin/|sort -u
fwupd:/usr/bin/fwupdmgr
# urpmf mdmonitor|grep service|sort -u mdadm:/usr/lib/systemd/system/mdmonitor.service mdadm:/usr/lib/systemd/system/mdmonitor-takeover.service
So "urpmi fwupd", and "systemctl disable mdmonitor.service".
Regards, Dave Hodgins
I assume that the .xml files had to download the first time. spaces had nothing to do with it. I am momentarily delusional
So "urpmi fwupd", and "systemctl disable mdmonitor.service".
Regards, Dave Hodgins
On Sun, 09 Feb 2025 16:42:19 -0500, faeychild <faeychild@nomail.afraid.org> wrote:
<snip>
I assume that the .xml files had to download the first time. spaces had
nothing to do with it. I am momentarily delusional
Correct. In drakrpm-edit-media, under Options, then Global options I always set xml meta
data download to always.
The effect of setting the global options in the gui add the entries to the urpmi.cfg file ...
$ head -n 5 /etc/urpmi/urpmi.cfg
{
downloader: wget
verify-rpm: 1
xml-info: always
}
I just edit the file instead of using the gui. Next time there are changes for urpmi to download, it
will download the xml files. Makes getting the list of available updates a little slower, but means no
waiting for downloads when looking things up with urpmf or urpmq. On a system with more than
one user, it also means the xml data is only downloaded by root, instead of once for each user that
uses urpmf or urpmq.
Regards, Dave Hodgins
I do not have raid in use on any of my machines. Should mdmonitor be running ?
Do I need to set xml meta data download to always in drakrpm-edit-media, under Options, then Global options ?
On Mon, 10 Feb 2025 10:13:35 -0500, Jim <jim.beard@verizon.net> wrote:
<snip>
I do not have raid in use on any of my machines. Should mdmonitor be running ?
For people who need it, if it's not enabled their system will not boot. For those who don't, it
just causes the journal message, and a slight delay booting.
It isn't disabled automatically for people who are not currently using it, as they may attach
other drives that are set up to use it.
Sysop: | Luis Silva |
---|---|
Location: | Lisbon |
Users: | 764 |
Nodes: | 10 (0 / 10) |
Uptime: | 127:27:46 |
Calls: | 278 |
Files: | 46,971 |
Messages: | 13,508 |