linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Wilk <jwilk@jwilk.net>
To: Michael Kerrisk <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: [PATCH 1/4] fanotify.7: tfix
Date: Mon,  2 Sep 2019 08:55:33 +0200	[thread overview]
Message-ID: <20190902065536.4878-1-jwilk@jwilk.net> (raw)

Signed-off-by: Jakub Wilk <jwilk@jwilk.net>
---
 man7/fanotify.7 | 26 +++++++++++++-------------
 1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/man7/fanotify.7 b/man7/fanotify.7
index b8e0755aa..fb64f06c1 100644
--- a/man7/fanotify.7
+++ b/man7/fanotify.7
@@ -927,7 +927,7 @@ and waits until an event of type
 .B FAN_CREATE
 has occurred.
 The event mask indicates which type of filesystem object\(emeither
-a file or a directory\(emwas created".
+a file or a directory\(emwas created.
 Once all events have been read from the buffer and processed accordingly,
 the program simply terminates.
 .PP
@@ -1008,7 +1008,7 @@ main(int argc, char **argv)
     struct fanotify_event_info_fid *fid;
 
     if (argc != 2) {
-        fprintf(stderr, "Invalid number of command line arguments.\e\n");
+        fprintf(stderr, "Invalid number of command line arguments.\en");
         exit(EXIT_FAILURE);
     }
 
@@ -1031,7 +1031,7 @@ main(int argc, char **argv)
         exit(EXIT_FAILURE);
     }
 
-    printf("Listening for events.\e\n");
+    printf("Listening for events.\en");
 
     /* Read events from the event queue into a buffer */
 
@@ -1047,22 +1047,22 @@ main(int argc, char **argv)
             FAN_EVENT_OK(metadata, len);
             metadata = FAN_EVENT_NEXT(metadata, len)) {
         fid = (struct fanotify_event_info_fid *) (metadata + 1);
-        file_handle = (struct file_handle *) fid->handle;
+        file_handle = (struct file_handle *) fid\->handle;
 
         /* Ensure that the event info is of the correct type */
 
-        if (fid->hdr.info_type != FAN_EVENT_INFO_TYPE_FID) {
-            fprintf(stderr, "Received unexpected event info type.\e\n");
+        if (fid\->hdr.info_type != FAN_EVENT_INFO_TYPE_FID) {
+            fprintf(stderr, "Received unexpected event info type.\en");
             exit(EXIT_FAILURE);
         }
 
-        if (metadata->mask == FAN_CREATE)
+        if (metadata\->mask == FAN_CREATE)
             printf("FAN_CREATE (file created):");
 
-        if (metadata->mask == FAN_CREATE | FAN_ONDIR)
+        if (metadata\->mask == FAN_CREATE | FAN_ONDIR)
             printf("FAN_CREATE | FAN_ONDIR (subdirectory created):");
 
-        /* metadata->fd is set to FAN_NOFD when FAN_REPORT_FID is enabled.
+        /* metadata\->fd is set to FAN_NOFD when FAN_REPORT_FID is enabled.
            To obtain a file descriptor for the file object corresponding to
            an event you can use the struct file_handle that\(aqs provided
            within the fanotify_event_info_fid in conjunction with the
@@ -1074,7 +1074,7 @@ main(int argc, char **argv)
         if (ret == \-1) {
             if (errno == ESTALE) {
                 printf("File handle is no longer valid. "
-                        "File has been deleted\e\n");
+                        "File has been deleted\en");
                 continue;
             } else {
                 perror("open_by_handle_at");
@@ -1093,15 +1093,15 @@ main(int argc, char **argv)
             exit(EXIT_FAILURE);
         }
 
-        path[path_len] = \(aq\e\0\(aq;
-        printf("\etDirectory \(aq%s\(aq has been modified.\e\n", path);
+        path[path_len] = \(aq\e0\(aq;
+        printf("\etDirectory \(aq%s\(aq has been modified.\en", path);
 
         /* Close associated file descriptor for this event */
 
         close(event_fd);
     }
 
-    printf("All events processed successfully. Program exiting.\e\n");
+    printf("All events processed successfully. Program exiting.\en");
     exit(EXIT_SUCCESS);
 }
 .EE
-- 
2.23.0


             reply	other threads:[~2019-09-02 11:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-02  6:55 Jakub Wilk [this message]
2019-09-02  6:55 ` [PATCH 2/4] fanotify_mark.2: ffix Jakub Wilk
2019-09-05 13:46   ` Michael Kerrisk (man-pages)
2019-09-02  6:55 ` [PATCH 3/4] fanotify_mark.2: Add kernel version numbers for some FAN_* constants Jakub Wilk
2019-09-05 13:47   ` Michael Kerrisk (man-pages)
2019-09-02  6:55 ` [PATCH 4/4] fanotify_mark.2: Document FAN_MOVE_SELF Jakub Wilk
2019-09-05 14:05   ` Michael Kerrisk (man-pages)
2019-09-05 13:45 ` [PATCH 1/4] fanotify.7: tfix Michael Kerrisk (man-pages)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190902065536.4878-1-jwilk@jwilk.net \
    --to=jwilk@jwilk.net \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).