From owner-freebsd-doc Wed Jun 14 7:40: 7 2000 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id E491137C1BE for ; Wed, 14 Jun 2000 07:40:04 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id HAA74112; Wed, 14 Jun 2000 07:40:04 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from mfi01.iij.ad.jp (mfi01.iij.ad.jp [202.232.2.116]) by hub.freebsd.org (Postfix) with ESMTP id 4431037C21D for ; Wed, 14 Jun 2000 07:31:51 -0700 (PDT) (envelope-from nokubi@ff.iij4u.or.jp) Received: from ppp-client.ff.iij4u.or.jp (h141.p029.iij4u.or.jp [210.130.29.141]) by mfi01.iij.ad.jp (8.8.8/MFI1.3) with ESMTP id XAA04483 for ; Wed, 14 Jun 2000 23:31:48 +0900 (JST) Received: (from h-nokubi@localhost) by ppp-client.ff.iij4u.or.jp (8.9.3/3.5Wpl7-ppp) id XAA52526; Wed, 14 Jun 2000 23:06:12 +0900 (JST) Message-Id: <200006141431.XAA04483@mfi01.iij.ad.jp> Date: Wed, 14 Jun 2000 23:06:12 +0900 (JST) From: nokubi@ff.iij4u.or.jp Reply-To: nokubi@ff.iij4u.or.jp To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: docs/19262: Is fsync.2 NAME section wrong? Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 19262 >Category: docs >Synopsis: Is fsync.2 NAME section wrong? >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Wed Jun 14 07:40:03 PDT 2000 >Closed-Date: >Last-Modified: >Originator: NOKUBI Hirotaka >Release: FreeBSD 3.4-STABLE i386 >Organization: >Environment: FreeBSD fifthluna.nokubi.or.jp 3.4-STABLE FreeBSD 3.4-STABLE #13: Mon Jan 31 00:17:41 JST 2000 root@sassaby.nokubi.or.jp:/usr/src/sys/compile/FIFTHLUNA i386 >Description: Because I'm not native English speaker, I'm not sure about this. But I have strange feeling about fsync.2 and sync.2 NAME section. They say like this: fsync - synchronize a file's in-core state with that on disk sync - synchronize disk block in-core status with that on disk I think that fsync(2) and sync(2) write changes from memory to disk. But these sentences make me feel like that they read from disk to memory and discard changes. If it's my misunderstanding, please forget about this PR. >How-To-Repeat: man 2 fsync man 2 sync >Fix: SUSV2 saids like this: fsync - synchronise changes to a file sync - schedule filesystem updates >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message