Re: bitmap font error on F38

2023-04-27 Thread Ranjan Maitra
George,

My thanks to you for your detailed descriptions. Here are some findings:

On Wed Apr26'23 11:25:02AM, George N. White III wrote:
> From: "George N. White III" 
> Date: Wed, 26 Apr 2023 11:25:02 -0300
> To: Community support for Fedora users 
> Reply-To: Community support for Fedora users 
> Subject: Re: bitmap font error on F38
> 
> On Fri, Apr 21, 2023 at 4:01 PM Ranjan Maitra  wrote:
> 
> > Hi,
> >
> > I am also having the following error with pdflatex upon upgrading to F38
> > from F37.
> >
> >  pathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+120/600 --dpi 720
> > eurm10
> >  mktexpk: don't know how to create bitmap font for eurm10.
> >  mktexpk: perhaps eurm10 is missing from the map file.
> >  kpathsea: Appending font creation commands to missfont.log.
> >  (see the transcript file for additional information)
> >  !pdfTeX error: pdflatex (file eurm10): Font eurm10 at 720 not found
> >   ==> Fatal error occurred, no output PDF file produced!
> >
> >
> > How do I get around this issue?
> >
> 
> TeX uses fontmap files that should tell pdflatex to use eurm10 font data,
> which includes .PostScript (.pfb format) files.   Sometimes users run
> things that generate fontmap and format files in their user directory and
> which then hides recent changes to the system files.
> 
> OpenType supports upright variants:
> 
> See:
> https://tex.stackexchange.com/questions/145926/upright-greek-font-fitting-to-computer-modern
>

Thanks for this. There is an example there which essentially rewrites the 
upgreek variants. I think that I can make it work for me, but!

> Your example "works for me" in Debian with their TeX Live packages, and on
> Fedora using CTAN TeX Live 2023.  The eurm10 fonts are present, but I
> didn't have
> upgreek.sty.
> 
> This F38 system has:
> 
> Installed Packages
> Name : texlive-amsfonts
> Epoch: 10
> Version  : svn61937
> Release  : 65.fc38
> Architecture : noarch
> Size : 5.9 M
> Source   : texlive-2022-65.fc38.src.rpm
> Repository   : @System
> From repo: fedora
> Summary  : TeX fonts from the American Mathematical Society
> URL  : http://tug.org/texlive/
> License  : OFL-1.1
> Description  : An extended set of fonts for use in mathematics, including:
>  : extra mathematical symbols; blackboard bold letters
> (uppercase
>  : only); fraktur letters; subscript sizes of bold math italic
> and
>  : bold Greek letters; subscript sizes of large symbols such as
>  : sum and product; added sizes of the Computer Modern small
> caps
>  : font; cyrillic fonts (from the University of Washington);
> Euler
>  : mathematical fonts. All fonts are provided as Adobe Type 1
>  : files, and all except the Euler fonts are provided as
> Metafont
>  : source. The distribution also includes the canonical Type 1
>  : versions of the Computer Modern family of fonts. Plain TeX
> and
>  : LaTeX macros for using the fonts are provided.
> 
> and includes:
> 
> $ find /usr/share/texlive/texmf-dist/fonts -name eurm10\*
> /usr/share/texlive/texmf-dist/fonts/tfm/public/amsfonts/euler/eurm10.tfm
> /usr/share/texlive/texmf-dist/fonts/afm/public/amsfonts/euler/eurm10.afm
> /usr/share/texlive/texmf-dist/fonts/type1/public/amsfonts/euler/eurm10.pfb
> /usr/share/texlive/texmf-dist/fonts/type1/public/amsfonts/euler/eurm10.pfm
>

So, I have this package installed/updated, and:

 $ find /usr/share/texlive/texmf-dist/fonts -name eurm10\*
 /usr/share/texlive/texmf-dist/fonts/type1/public/amsfonts/euler/eurm10.pfm
 /usr/share/texlive/texmf-dist/fonts/type1/public/amsfonts/euler/eurm10.pfb
 /usr/share/texlive/texmf-dist/fonts/afm/public/amsfonts/euler/eurm10.afm
 /usr/share/texlive/texmf-dist/fonts/tfm/public/amsfonts/euler/eurm10.tfm

> For the .sty file you need to install the Walter Schmidt (was)package:
> texlive-was.

Yes, I have this installed from the Fedora sources.

> 
> TeX Live 2003 from CTAN has:
> 
> $ find /usr/local/texlive/2023/texmf-dist/fonts -name eurm10\*
> /usr/local/texlive/2023/texmf-dist/fonts/afm/public/amsfonts/euler/eurm10.afm
> /usr/local/texlive/2023/texmf-dist/fonts/tfm/public/amsfonts/euler/eurm10.tfm
> /usr/local/texlive/2023/texmf-dist/fonts/type1/public/amsfonts/euler/eurm10.pfb
> /usr/local/texlive/2023/texmf-dist/fonts/type1/public/amsfonts/euler/eurm10.pfm
> 
> Check that the generated fontmap has eurm10 entries:
> 
> $ grep -F 'eurm10' 
> /usr/share/texlive/texmf-var/fonts/map/pdftex/updmap/pdftex.map
> eurm10 EURM10  eurm9 EURM10  eurmo10 EURM10 " .167 SlantFont " 

So, unlike you, I have only one entry here:


 $ grep -F 'eurm10' 
/usr/share/texlive/texmf-var/fonts/map/pdftex/updmap/pdftex.map
 eurmo10 EURM10 " .167 SlantFont "  Note that support for PostScript fonts is disappearing, so it should not be
> surprising to
> encounter surprises when trying to use pfb fonts because fewer people are
> using them 

Re: F38 and NUT -- SOLVED

2023-04-27 Thread Greg Woods
FINALLY! It occurred to me to try this:

[root@seveneves ups]# journalctl -u nut-driver@seveneves-ups
Apr 27 09:16:34 seveneves.gregandeva.net systemd[1]: Starting
nut-driver@seveneves-ups.service - Network UPS Tools - device driver for
NUT device 'seveneves-ups'...
Apr 27 09:16:34 seveneves.gregandeva.net nut-driver@seveneves-ups[466866]:
Network UPS Tools - Generic HID driver 0.47 (2.8.0)
Apr 27 09:16:34 seveneves.gregandeva.net nut-driver@seveneves-ups[466866]:
USB communication driver (libusb 1.0) 0.43
Apr 27 09:16:34 seveneves.gregandeva.net nut-driver@seveneves-ups[466866]:
Fatal error: 'maxretry' is not a valid variable name for this driver.

So it seems that an edit to ups.conf was also needed. Commenting out the
maxtry line (which has been there literally for years) gets things working
again. Thanks again to Robert and Jeff for pointing me in the right
direction.

--Greg
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: F38 and NUT

2023-04-27 Thread Chris Adams
Once upon a time, Greg Woods  said:
> Looks like I spoke too soon; I noticed that the nut-monitor service had
> stopped running. I restarted it, and:

NUT is a bit of a bear to get configured, but as far as the systemd
portion, I only have nut.target enabled.  It looks like that pulls in
all the rest of the necessary bits.

The config files I have edited under /etc/ups are:

- nut.conf
  set "MODE=standalone"

- ups.conf
  add a section for the UPS

- upsd.conf
  add "LISTEN ::" (not needed for most, I'm monitoring UPS status remotely)

- upsd.users
  add a section for a monitoring user

- upsmon.conf
  add a MONITOR line for the UPS+user

-- 
Chris Adams 
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: F38 and NUT

2023-04-27 Thread Greg Woods
On Thu, Apr 27, 2023 at 9:38 AM Greg Woods  wrote:

>
> On the positive side, the repetitive error:
> Apr 26 12:49:09 seveneves.gregandeva.net nut-monitor[326253]: Poll UPS
> [seveneves-ups@localhost] failed - Driver not connected
>
> is no longer happening
>

Looks like I spoke too soon; I noticed that the nut-monitor service had
stopped running. I restarted it, and:


Apr 27 09:52:26 seveneves.gregandeva.net nut-monitor[11136]: Poll UPS
[seveneves-ups@localhost] failed - Driver not connected

This is being logged every 5 seconds. So I'm more-or-less back to square
one.

--Greg
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: How to restart sudo rpmconf -a

2023-04-27 Thread stan via users
On Thu, 27 Apr 2023 01:18:50 -0400
Jeffrey Walton  wrote:

> Hi Everyone,
> 
> I dnf-system-upgraded my last machine from F37 to F38. I screwed up at
> post-upgrade at 'sudo rpmconf -a'.
[snip] 
> How do I restart rpmconf?

I don't know if this will work, but you could go into
/var/log/dnf.rpm.log and get the list of files that were updated.
Then try reinstalling each and every one of them [1], since you have no
idea which had new configuration and which didn't.  That should write a
new rpmnew or rpmsave.  Then it would just be necessary to run
rpmconf again.

1. You can probably write a script in your scripting language of
choice to extract the names, and put them in a separate file.

e.g. 

#! /bin/bash

dnf -y reinstall \
[list of packages, one per line, goes here, each line terminated with \]


Then just run the file.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: F38 and NUT

2023-04-27 Thread Greg Woods
Thanks to Jeff and Robert for the hint about the nut-driver-enumerator
service. This is indeed new with F37; I looked at the F36 RPM and there is
no nut-driver-enumerator.service file. On the F37 system the service file
is there but it is disabled by default. I enabled it and rebooted, but it
did not fix my problem. The enumerator service appears to run:

[root@seveneves mythtv]# systemctl status nut-driver-enumerator
Apr 27 09:16:33 seveneves.gregandeva.net systemd[1]: Starting
nut-driver-enumerator.service - Network UPS Tools - enumeration of
configure-file devices into systemd unit instances...
Apr 27 09:16:33 seveneves.gregandeva.net nut-driver-enumerator[466627]:
Error reading the list of systemd service instances for UPS drivers, or
none are defined - before manipulations
Apr 27 09:16:33 seveneves.gregandeva.net nut-driver-enumerator[466627]: Thu
Apr 27 03:16:33 PM UTC 2023 : Detected changes in global section of
'/etc/ups/ups.conf', will restart all drivers
Apr 27 09:16:33 seveneves.gregandeva.net nut-driver-enumerator[466627]: OK
Apr 27 09:16:33 seveneves.gregandeva.net nut-driver-enumerator[466627]:
Adding new systemd service instance for power device [seveneves-ups]...
Apr 27 09:16:33 seveneves.gregandeva.net nut-driver-enumerator[466673]:
Created symlink
/etc/systemd/system/nut-driver.target.wants/nut-driver@seveneves-ups.service
→ /usr/lib/systemd/system/nut-driver@.service.
Apr 27 09:16:34 seveneves.gregandeva.net nut-driver-enumerator[466627]:
Enabled instance: 'nut-driver@seveneves-ups' for NUT configuration section
'seveneves-ups'
Apr 27 09:16:34 seveneves.gregandeva.net nut-driver-enumerator[466627]:
Adding 'Wants'+After dependency for 'seveneves-ups' on
'systemd-udev.service systemd-udev-settle.service'...
Apr 27 09:16:34 seveneves.gregandeva.net nut-driver-enumerator[466627]: OK
Apr 27 09:16:34 seveneves.gregandeva.net nut-driver-enumerator[466627]: OK
Apr 27 09:16:34 seveneves.gregandeva.net nut-driver-enumerator[466627]:
Started instance: 'nut-driver@seveneves-ups' for NUT configuration section
'seveneves-ups'
Apr 27 09:16:34 seveneves.gregandeva.net nut-driver-enumerator[466627]: ===
The currently defined service instances are:
Apr 27 09:16:34 seveneves.gregandeva.net nut-driver-enumerator[466627]:
seveneves-ups
Apr 27 09:16:34 seveneves.gregandeva.net nut-driver-enumerator[466627]: ===
The currently defined configurations in '/etc/ups/ups.conf' are:
Apr 27 09:16:34 seveneves.gregandeva.net nut-driver-enumerator[466627]:
seveneves-ups
Apr 27 09:16:34 seveneves.gregandeva.net nut-driver-enumerator[466627]: Thu
Apr 27 03:16:34 PM UTC 2023 : OK: No more changes to reconcile between
systemd service instances and device configurations in '/etc/ups/ups.conf'
Apr 27 09:16:34 seveneves.gregandeva.net systemd[1]:
nut-driver-enumerator.service: Deactivated successfully.
Apr 27 09:16:34 seveneves.gregandeva.net systemd[1]: Finished
nut-driver-enumerator.service - Network UPS Tools - enumeration of
configure-file devices into systemd unit instances.
Apr 27 09:17:54 seveneves.gregandeva.net systemd[1]: Starting
nut-driver-enumerator.service - Network UPS Tools - enumeration of
configure-file devices into systemd unit instances...
Apr 27 09:17:54 seveneves.gregandeva.net nut-driver-enumerator[467256]: Thu
Apr 27 03:17:54 PM UTC 2023 : OK: No changes to reconcile between systemd
service instances and device configurations in '/etc/ups/ups.conf'
Apr 27 09:17:54 seveneves.gregandeva.net systemd[1]:
nut-driver-enumerator.service: Deactivated successfully.
Apr 27 09:17:54 seveneves.gregandeva.net systemd[1]: Finished
nut-driver-enumerator.service - Network UPS Tools - enumeration of
configure-file devices into systemd unit instances.

But I still get the same error:

[root@seveneves ups]# upsc seveneves-ups@localhost
Error: Driver not connected
[root@seveneves ups]# systemctl status nut-server
● nut-server.service - Network UPS Tools - power devices information server
 Loaded: loaded (/usr/lib/systemd/system/nut-server.service; enabled;
preset: disabled)
 Active: active (running) since Thu 2023-04-27 09:20:04 MDT; 9min ago
   Main PID: 1716 (upsd)
  Tasks: 1 (limit: 38356)
 Memory: 884.0K
CPU: 13ms
 CGroup: /system.slice/nut-server.service
 └─1716 /usr/sbin/upsd -F

Apr 27 09:20:04 seveneves.gregandeva.net nut-server[1716]: listening on
127.0.0.1 port 3493
Apr 27 09:20:04 seveneves.gregandeva.net nut-server[1716]: not listening on
192.168.1.56 port 3493
Apr 27 09:20:04 seveneves.gregandeva.net upsd[1716]: listening on 127.0.0.1
port 3493
Apr 27 09:20:04 seveneves.gregandeva.net nut-server[1716]: Can't connect to
UPS [seveneves-ups] (usbhid-ups-seveneves-ups): No such file or directory
Apr 27 09:20:04 seveneves.gregandeva.net nut-server[1716]: Running as
foreground process, not saving a PID file
Apr 27 09:20:04 seveneves.gregandeva.net upsd[1716]: not listening on
192.168.1.56 port 3493
Apr 27 09:20:04 seveneves.gregandeva.net upsd[1716]: Can't connect to UPS

Post F38 upgrade/install printing in mirror image from HP P3015

2023-04-27 Thread Max Pyziur

Greetings,

I'm stumbling through both an F38 upgrade and a new installation (the 
latter due to an F38 major upgrade problem). Thankfully, data has been 
saved and recovered.


But problems arise (sort of like knowing how to drive a 2000 model year 
vehicle and then being confronted with a 2020 model year one).


Two problems:
1) On both machines, printing to my HP P3015 produces a mirror image when 
printing from a browser.


2) When using paps to print text files, the result is raw postscript, 
meaning multiple pages when one was expected.


Advice?

Max
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Updating grub after dnf-system-upgrade

2023-04-27 Thread Tom Horsley
On Thu, 27 Apr 2023 01:47:58 -0400
Jeffrey Walton wrote:

> (I have open questions about systems that claim both BIOS and UEFI,
> but I have not been able to find answers. If I need to back up a bit,
> then please say so).

This may or may not be helpful, but when I make a "universal" boot
USB stick these are my notes for installing both bios and uefi grub:

mount /dev/sdc1 /mnt
mkdir /mnt/boot
grub2-install --target=i386-pc --recheck --boot-directory=/mnt/boot /dev/sdc
grub2-install --target x86_64-efi --removable --boot-directory=/mnt/boot 
--efi-directory=/mnt
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: F38 and NUT

2023-04-27 Thread Robert Nichols

On 4/26/23 18:30, Greg Woods wrote:

Since upgrading to F37, I am having problems getting Nut to work properly. The 
errors I get from the journal are:

Apr 26 17:01:42 seveneves.gregandeva.net  
nut-server[326151]: Can't connect to UPS [seveneves-ups] (usbhid-ups-seveneves-ups): 
No such file or directory
Apr 26 17:01:42 seveneves.gregandeva.net  
upsd[326151]: Can't connect to UPS [seveneves-ups] (usbhid-ups-seveneves-ups): No 
such file or directory


Do you have nut-driver-enumerator.service enabled?

--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Why is updatedb running now?

2023-04-27 Thread Barry Scott


> On 26 Apr 2023, at 20:51, Tom Horsley  wrote:
> 
> I copied /usr/lib/systemd/system/plocate-updatedb.timer to
> /etc/systemd/system/plocate-updatedb.timer and changed
> RandomizedDelaySec from 12h to 2h which is supposed to mean
> it runs sometime between midnight and 2am.
> 
> It did work that way of fedora 37, yet with the same changes
> in fedora 38 it is running at around 3:30 in the afternoon.
> 
> What magic am I missing?

First there is no need to copy a service to make a small modification.
You can use a override file. This is what systemctl edit  will setup 
for you.

Then in the override file you would just need two lines.
The section header and the attribute you want to override.

[Timer]
RandomizedDelaySec=2h

After you made the change did you do systemctl daemon-reload?
You can check what is being used live with systemctl list-timers.

Barry


> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


[389-users] Re: 389 DS memory growth

2023-04-27 Thread Thierry Bordaz

Hi Alexander,

Memory footprint is larger with valgrind. You may reduce cache tuning to 
let your instance fit on the server. Disable autoh-tune 
(nsslapd-cache-autosize=0) and reduce nsslapd-cachememsize and 
nsslapd-dbcachesize.


regards
Thierry

On 4/27/23 02:05, Nazarenko, Alexander wrote:


Hi, Theirry,

We have followed the directions to investigate a memory leak which 
occurs as we reach many hundreds of thousands of entries, and got the 
log file, which shows some warnings:


==26735== Warning: set address range perms: large range [0x59eaf000, 
0xb3067000) (defined)


==26735== Thread 18:

==26735== Conditional jump or move depends on uninitialized value(s)

…

==26735== Thread 30:

==26735== Syscall param pwrite64(buf) points to uninitialised byte(s)

==26735== at 0x7998023: ??? (in /usr/lib64/libpthread-2.17.so)

and similar strings. Memory was running to 90% of 16G servers, and 
never comes back.


Thoughts, suggestions are much appreciated.

- Alex

*From: *Thierry Bordaz 
*Date: *Tuesday, April 18, 2023 at 12:37 PM
*To: *"Nazarenko, Alexander" , 
"General discussion list for the 389 Directory server project." 
<389-users@lists.fedoraproject.org>

*Subject: *Re: [389-users] 389 DS memory growth

Thanks for the update.

I failed to reproduced any significant growth with 
groups(100)/members(1000) provisioning. The same with searches on 
person returning 1000 person entries (bound as DM). We will wait for 
your profiling info.


regards
Theirry

On 4/18/23 18:12, Nazarenko, Alexander wrote:

This is understood, thank you. It is not a big concern for us, as
our servers are at least 16Gb.

We are not using pbkdf2 either.

This is the heap growth above 20Gb (and up) that is the concern,
due to queries like (objectclass=person) hiting the server.

At some point in the near future we plan profile a typical server
for memory usage, and plan to keep posted.

*- Alwes*

*From: *Thierry Bordaz 

*Date: *Tuesday, April 18, 2023 at 11:47 AM
*To: *"General discussion list for the 389 Directory server
project." <389-users@lists.fedoraproject.org>
, "Nazarenko, Alexander"


*Subject: *Re: [389-users] 389 DS memory growth

Hi,

Note that the initial memory footprint of an instance 1.3.11 is
larger that an 1.3.10 one.

On RHEL 7.9 2Gb VM, an instance 1.3.11 is 1Gb while 1.3.10 is 0.5Gb.
Instances have the same DS tuning.

The difference comes from extra chunks of anonymous memory (heap)
that are possibly related to the new rust plugin handling
pbkdf2_sha512.

7ffb0812e000 64328   0   0 -   [ anon ]
7ffb0c00 1204    1060    1060 rw---   [ anon ]
7ffb0c12d000 64332   0   0 -   [ anon ]
7ffb1000 1028    1028    1028 rw---   [ anon ]
7ffb10101000 64508   0   0 -   [ anon ]
7ffb1400 1020    1020    1020 rw---   [ anon ]
7ffb140ff000 64516   0   0 -   [ anon ]
7ffb1800 1024    1024    1024 rw---   [ anon ]
7ffb1810 64512   0   0 -   [ anon ]
7ffb1c00 1044    1044    1044 rw---   [ anon ]
7ffb1c105000 64492   0   0 -   [ anon ]
7ffb2000 540 540 540 rw---   [ anon ]
7ffb20087000 64996   0   0 -   [ anon ]
7ffb271ce000 4   0   0 -   [ anon ]

This is just the initial memory footprint and does not explain
regular growth.
Thanks to progier who raised that point.

regards
thierry

On 4/17/23 03:07, Nazarenko, Alexander wrote:

Hello colleagues,

On March 22nd we updated the 389-ds-base.x86_64 and
389-ds-base-libs.x86_64 packages on our eight RHEL 7.9
production servers from version 1.3.10.2-17.el7_9 to version
1.3.11.1-1.el7_9.  We also updated the kernel from kernel
3.10.0-1160.80.1.el7.x86_64 to
kernel-3.10.0-1160.88.1.el7.x86_64 during the same update.

Approximately 12 days later, on April 3rd, all the hosts
started exhibiting memory growth issues whereby the “slapd”
process was using over 90% of the available system memory of
32GB, which was NOT happening for a couple of years prior to
applying any of the available package updates on the systems.

Two of the eight hosts act as Primaries (formerly referred to
as masters), while 6 of the hosts act as read-only replicas. 
Three of the read-only replicas are used by our authorization
system while the other three read-only replicas are used by
customer-based applications.

Currently we use system controls to restrict the memory usage.

My question is whether this is something that other users also
experience, and what is the recommended way to 

Re: Updating grub after dnf-system-upgrade

2023-04-27 Thread Samuel Sieb

On 4/26/23 22:47, Jeffrey Walton wrote:

I just dnf-upgraded my last system from F37 to F38. One of the
post-upgrade task is "Update GRUB bootloader on BIOS systems"
(https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/):

 Systems with the BIOS firmware have the GRUB RPM packages updated.
 However, the installed or embedded bootloader is never updated
 automatically. It is a good idea to update it between Fedora release
 versions.

I have a system that is is using BIOS, and it not using UEFI or
SecureBoot (though UEFI is available):

When I run the command:

 $ sudo mount | grep "/boot "
 /dev/mmcblk0p2 on /boot type ext4 (rw,relatime)


If it was UEFI, there would be a /boot/efi mount as well.


Do I install grub2 on /dev/mmcblk0 or /dev/mmcblk0p2? I think it is
the former, but I want to make sure. That is, is this correct:

 sudo grub2-install /dev/mmcblk0


Yes.


(I have open questions about systems that claim both BIOS and UEFI,
but I have not been able to find answers. If I need to back up a bit,
then please say so).


Not sure what you mean by that.  The system can support both options, 
but only one will be active at a time.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue