Ticket 23940 - Fix sackd.8 manpage
Summary: Fix sackd.8 manpage
Status: RESOLVED FIXED
Alias: None
Product: Slurm
Classification: Unclassified
Component: Documentation (show other tickets)
Version: 25.05.4
Hardware: Linux Linux
: C - Contributions
Assignee: Stephen Kendall
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2025-10-21 21:30 MDT by Gennaro Oliva
Modified: 2025-10-22 16:21 MDT (History)
0 users

See Also:
Site: -Other-
Slinky Site: ---
Alineos Sites: ---
Atos/Eviden Sites: ---
Confidential Site: ---
Coreweave sites: ---
Cray Sites: ---
DS9 clusters: ---
Google sites: ---
HPCnow Sites: ---
HPE Sites: ---
IBM Sites: ---
NOAA SIte: ---
NoveTech Sites: ---
Nvidia HWinf-CS Sites: ---
OCF Sites: ---
Recursion Pharma Sites: ---
SFW Sites: ---
SNIC sites: ---
Tzag Elita Sites: ---
Linux Distro: ---
Machine Name:
CLE Version:
Version Fixed: 25.11.0-0rc1
Target Release: ---
DevPrio: ---
Emory-Cloud Sites: ---

Attachments
patch (380 bytes, text/plain)
2025-10-21 21:30 MDT, Gennaro Oliva 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this ticket.
Description Gennaro Oliva 2025-10-21 21:30:57 MDT 
Created attachment 43415 [details]
patch

This patch fixes a formatting error in the sackd.8 manpage. The original
source used the invalid escape sequence \fb, which makes groff attempt to
select a non-existent font 'b' and triggers the warning:
troff:<standard input>:91: warning: cannot select font 'b'.
The patch corrects this by replacing \fb with the proper escape sequence \fB
to select bold font.
Comment 3 Stephen Kendall 2025-10-22 15:36:00 MDT 
Thanks for pointing out this issue. We'll get it fixed soon.

Best regards,
Stephen
Comment 4 Stephen Kendall 2025-10-22 16:21:16 MDT 
We have checked in a fix for this issue.
https://github.com/SchedMD/slurm/commit/f0f1b28ac65e6eb0a894e81af9c14a9035033e69

I also noticed another formatting issue slightly further down on that page and fixed it as well.
https://github.com/SchedMD/slurm/commit/4213ad67e2e579006dcd8ebe9f5a62543215416e

Both of these fixes will be included in the next major release, 25.11.

Best regards,
Stephen