Skip to contentSkip to conversation

sem_overview.7: Fix typo (semget => shmget)

PATCH In review Bo Borgerson 2 participants 2 messages Mar 30, 2010 – May 22, 2010 1 message not in the archive Man-pages: manual pages for Linux -- Sections 2, 3, 4, 5, and 7

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 sem_overview.7: Fix typo (semget => shmget)

Hi,

The sem_overview(7) man page makes reference to "a System V shared memory segment created using semget(2)". Was this intended to be "shmget(2)"?

Please see attached patch against current git master.

Thanks,

Bo

Quoted 1 line

From cc406c10dd443f79e9073f053619a9c475ec97ad Mon Sep 17 00:00:00 2001

From: Bo Borgerson <[email protected]>
Date: Mon, 29 Mar 2010 18:12:33 -0700
Subject: [PATCH] sem_overview.7: Fix typo (semget => shmget)

In reference to creation of a SysV shared memory segment.

---
 man7/sem_overview.7 |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
man7/sem_overview.7 +1 -1
index ef354fe..fb706d2 100644
@@ -88,7 +88,7 @@ A thread-shared semaphore is placed in an area of memory shared
 between by the threads of a process, for example, a global variable.
 A process-shared semaphore must be placed in a shared memory region
 (e.g., a System V shared memory segment created using
-.BR semget (2),
+.BR shmget (2),
 or a POSIX shared memory object built created using
 .BR shm_open (3)).
 
Signature · 1 line
1.6.3.3

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw
Quoted 6 lines · Bo Borgerson

Hi,

The sem_overview(7) man page makes reference to "a System V shared memory segment created using semget(2)".  Was this intended to be "shmget(2)"?

Please see attached patch against current git master.

Thanks. Patch applied for 3.25.

Cheers,

Michael

Signature · 7 lines
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Author of "The Linux Programming Interface" http://blog.man7.org/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html