06-03-2019
I have replaced this "history section" with a "matched man page section".
This was accomplished by moving the man page entries to an SQL database (currently over 210K unique entries) and doing Full Test searches of the DB to get scores of the matches and the to choose on of the top scores at random. The Man DB that I created for this may be larger than the entire DB before, and it is certainly by far the largest table in the DB.
I think this will work better than "history" sections, since we can learn new commands and man entries when viewing tags and posts.
After I runs a bit longer and it well tested, I will redo how the repositories are done; since I can now pull the info for all repositories for the DB and not read from the file system.
It should be a lot faster when I rewrite the repo pages to use the DB.
Also, our SEO scores should go up, I am guessing, and I anticipate the number of links in our index will continue to increase. Currently, GSC shows about 320K links. I expect this to continue to rise due to the changes I have made this month.
This User Gave Thanks to Neo For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I tried looking for the answer online and came up with only a few semi-answers as to why file and directory names are case sensitive in Unix. Right off the bat, I'll say this doesn't bother me. But I run into tons of Windows and OpenVMS admins in my day job who go batty when they have to deal... (3 Replies)
Discussion started by: deckard
3 Replies
2. Solaris
is there any way to determine the last command entered on a unix machine???
Thanx (3 Replies)
Discussion started by: mm00123
3 Replies
3. SuSE
When we login to any remote connections in SuSE Linux, say for example, telnet , the following line is displayed "Last Login : Date and time is displayed"
I would like to disable this. In SuSE 9, I could find the solution .
Please suggest me a solution to disable the line displayed for SuSE... (3 Replies)
Discussion started by: Laksmi
3 Replies
4. Shell Programming and Scripting
Hi All,
My question is how can i stop my users on system from deleting their history.
How can i stop the users from running 'history -c'.
I have searched thoroughly on the forum but didn't find any satisfactory solution to the problem.
kindly help if you any suggestions
Thanx in... (3 Replies)
Discussion started by: xander
3 Replies
5. UNIX and Linux Applications
Hi everybody Im Megadrink!!!
This is my first thred.
Ive recently been introduced to Unix and i was interested in Unix's History. Can anyone give me a breif History On Unix. Just when it was invented/released. Maybe someother cool things about it.
Thx for the information in advance!! :D (2 Replies)
Discussion started by: Megadrink
2 Replies
6. Linux
Hi All,
Is there a way to check command executed by users in Linux for a specific date? I know we can use history, but it doesn't shows yesterday's executed commands.
rgds, (3 Replies)
Discussion started by: ronny_nch
3 Replies
7. UNIX for Dummies Questions & Answers
Hello All, Good Morning.
I am trying to erase history list in my linux box, but my below command is failing. What is the actual way to clear it?
> history clear
-bash: history: clear: numeric argument required
Also when I run my commands in my command prompt, my team lead can see my... (7 Replies)
Discussion started by: NARESH1302
7 Replies
8. Shell Programming and Scripting
commands to view the history file in unix.
I am not sure whether it is bash_history.sh (1 Reply)
Discussion started by: ramkumar15
1 Replies
9. What is on Your Mind?
I am pleased to announce this new video in 1080 HD for UNIX lovers honoring thirty years of UNIX history spanning from 1969 to 1999 presented in 150 seconds (two and a half minutes) in 1080 HD, celebrating the 50th anniversary of UNIX.
The Great History of UNIX (1969-1999) | 30 Years of UNIX... (8 Replies)
Discussion started by: Neo
8 Replies
10. UNIX for Advanced & Expert Users
hello all
i have application which according to AWS monitoring is reaching to high spikes of IO at random time .
and causing the server to crash and restart .
my question is how can i find out what cause the spike and if i can't with the native linux tools
what free open source minimon... (6 Replies)
Discussion started by: umen
6 Replies
LEARN ABOUT MINIX
mandoc.db
MANDOC.DB(5) File Formats Manual MANDOC.DB(5)
NAME
mandoc.db - manual page database
DESCRIPTION
The mandoc.db file format is used to store information about installed manual pages to facilitate semantic searching for manuals. Each
manual page tree contains its own mandoc.db file; see FILES for examples.
Such database files are generated by makewhatis(8) and used by man(1), apropos(1) and whatis(1).
The file format uses three datatypes:
- 32-bit signed integer numbers in big endian (network) byte ordering
- NUL-terminated strings
- lists of NUL-terminated strings, terminated by a second NUL character
Numbers are aligned to four-byte boundaries; where they follow strings or lists of strings, padding with additional NUL characters occurs.
Some, but not all, numbers point to positions in the file. These pointers are measured in bytes, and the first byte of the file is
considered to be byte 0.
Each file consists of:
- One magic number, 0x3a7d0cdb.
- One version number, currently 1.
- One pointer to the macros table.
- One pointer to the final magic number.
- The pages table (variable length).
- The macros table (variable length).
- The magic number once again, 0x3a7d0cdb.
The pages table contains one entry for each physical manual page file, no matter how many hard and soft links it may have in the file
system. The pages table consists of:
- The number of pages in the database.
- For each page:
- One pointer to the list of names.
- One pointer to the list of sections.
- One pointer to the list of architectures or 0 if the page is machine-independent.
- One pointer to the one-line description string.
- One pointer to the list of filenames.
- For each page, the list of names. Each name is preceded by a single byte indicating the sources of the name. The meaning of the bits
is:
- 0x10: The name appears in a filename.
- 0x08: The name appears in a header line, i.e. in a .Dt or .TH macro.
- 0x04: The name is the first one in the title line, i.e. it appears in the first .Nm macro in the NAME section.
- 0x02: The name appears in any .Nm macro in the NAME section.
- 0x01: The name appears in an .Nm block in the SYNOPSIS section.
- For each page, the list of sections. Each section is given as a string, not as a number.
- For each architecture-dependent page, the list of architectures.
- For each page, the one-line description string taken from the .Nd macro.
- For each page, the list of filenames relative to the root of the respective manpath. This list includes hard links, soft links, and
links simulated with .so roff(7) requests. The first filename is preceded by a single byte having the following significance:
- FORM_SRC = 0x01: The file format is mdoc(7) or man(7).
- FORM_CAT = 0x02: The manual page is preformatted.
- Zero to three NUL bytes for padding.
The macros table consists of:
- The number of different macro keys, currently 36. The ordering of macros is defined in <mansearch.h> and the significance of the
macro keys is documented in apropos(1).
- For each macro key, one pointer to the respective macro table.
- For each macro key, the macro table (variable length).
Each macro table consists of:
- The number of entries in the table.
- For each entry:
- One pointer to the value of the macro key. Each value is a string of text taken from some macro invocation.
- One pointer to the list of pages.
- For each entry, the value of the macro key.
- Zero to three NUL bytes for padding.
- For each entry, one or more pointers to pages in the pages table, pointing to the pointer to the list of names, followed by the number
0.
FILES
/usr/share/man/mandoc.db The manual page database for the base system.
/usr/X11R6/man/mandoc.db The same for the X(7) Window System.
/usr/local/man/mandoc.db The same for packages(7).
A program to dump mandoc.db files in a human-readable format suitable for diff(1) is provided in the directory
/usr/src/regress/usr.bin/mandoc/db/dbm_dump/.
SEE ALSO
apropos(1), man(1), whatis(1), makewhatis(8)
HISTORY
A manual page database /usr/lib/whatis first appeared in 2BSD. The present format first appeared in OpenBSD 6.1.
AUTHORS
The original version of makewhatis(8) was written by Bill Joy in 1979. The present database format was designed by Ingo Schwarze
<schwarze@openbsd.org> in 2016.
Debian August 1, 2016 MANDOC.DB(5)