From: Yu Watanabe Date: Mon, 4 Apr 2022 18:56:10 +0000 (+0900) Subject: fix typo X-Git-Tag: v251-rc2~202^2~2 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=e7e25c21c60a6b811985610ee0374ab4293b3cf3;p=thirdparty%2Fsystemd.git fix typo --- diff --git a/man/udevadm.xml b/man/udevadm.xml index b0e448e5687..5994abde8ea 100644 --- a/man/udevadm.xml +++ b/man/udevadm.xml @@ -791,7 +791,7 @@ udevadm lock takes an (advisory) exclusive lock(s) on a block device (or - multiple therof), as per Locking Block Device + multiple thereof), as per Locking Block Device Access and invokes a program with the lock(s) taken. When the invoked program exits the lock(s) are automatically released. diff --git a/src/udev/udevadm-lock.c b/src/udev/udevadm-lock.c index fae464704f4..3e5d7b356f2 100644 --- a/src/udev/udevadm-lock.c +++ b/src/udev/udevadm-lock.c @@ -41,7 +41,7 @@ static int help(void) { printf("%s [OPTIONS...] COMMAND\n" "%s [OPTIONS...] --print\n" - "\n%sLock a block device and run a comand.%s\n\n" + "\n%sLock a block device and run a command.%s\n\n" " -h --help Print this message\n" " -V --version Print version of the program\n" " -d --device=DEVICE Block device to lock\n" @@ -247,7 +247,7 @@ static int lock_device( /* flock() doesn't support a time-out. Let's fake one then. The traditional way to do * this is via alarm()/setitimer()/timer_create(), but that's racy, given that the - * SIGALRM might aleady fire between the alarm() and the flock() in which case the + * SIGALRM might already fire between the alarm() and the flock() in which case the * flock() is never cancelled and we lock up (this is a short time window, but with * short timeouts on a loaded machine we might run into it, who knows?). Let's * instead do the lock out-of-process: fork off a child that does the locking, and