File locks - Revision history

Xemul at 10:43, 22 February 2017

2017-02-22T10:43:08Z

Kir: rewording

2016-09-20T23:28:10Z

rewording

Kir at 23:26, 20 September 2016

2016-09-20T23:26:04Z

Xemul at 16:10, 20 September 2016

2016-09-20T16:10:12Z

Xemul: Created page with "Some app may use file locks for synchronization. Generally they will use flock or posix file locks, which were achieved by flock or fcntl system calls. For dump/restore, it is..."

2016-09-17T14:12:21Z

Created page with "Some app may use file locks for synchronization. Generally they will use flock or posix file locks, which were achieved by flock or fcntl system calls. For dump/restore, it is..."

New page

Some app may use file locks for synchronization. Generally they will use flock or posix file locks, which were achieved by flock or fcntl system calls. For dump/restore, it is hard to be handled perfectly, because we can't guarantee all potential users are dumped for a specific file lock. Right now, we assume that all file lock users are taken into dump, and we should use the --file-locks option on both dump and restore stages if our app may use any file locks. Remember that file locks dump/restore is only safe for container dumping in theory.

[[Category: Empty articles]]
[[Category: Files]]

← Older revision		Revision as of 10:43, 22 February 2017
Line 1:		Line 1:
−	Some app may use file locks for synchronization. Generally they will use flock or POSIX file locks, which were achieved by <code>flock</code> or <code>fcntl</code> system calls. For dump/restore, it is hard to be handled perfectly, because we can't guarantee all potential users are dumped for a specific file lock. Right now, we assume that all file lock users are taken into dump, and the ~~<code>~~--file-locks~~</code>~~ option should be used on both dump and restore stages if our app may use any file locks. Remember that file locks dump/restore can only be absolutely safe for container dumping (as a container, naturally, contains all the file locks users).	+	Some app may use file locks for synchronization. Generally they will use flock or POSIX file locks, which were achieved by <code>flock</code> or <code>fcntl</code> system calls. For dump/restore, it is hard to be handled perfectly, because we can't guarantee all potential users are dumped for a specific file lock. Right now, we assume that all file lock users are taken into dump, and the {{Opt\|--file-locks}} option should be used on both dump and restore stages if our app may use any file locks. Remember that file locks dump/restore can only be absolutely safe for container dumping (as a container, naturally, contains all the file locks users).

	Currently supported lock types are:		Currently supported lock types are:

← Older revision		Revision as of 23:28, 20 September 2016
Line 1:		Line 1:
−	Some app may use file locks for synchronization. Generally they will use flock or POSIX file locks, which were achieved by flock or fcntl system calls. For dump/restore, it is hard to be handled perfectly, because we can't guarantee all potential users are dumped for a specific file lock. Right now, we assume that all file lock users are taken into dump, and ~~we should use~~ the <code>--file-locks</code> option on both dump and restore stages if our app may use any file locks. Remember that file locks dump/restore is only safe for container dumping ~~in theory~~.	+	Some app may use file locks for synchronization. Generally they will use flock or POSIX file locks, which were achieved by <code>flock</code> or <code>fcntl</code> system calls. For dump/restore, it is hard to be handled perfectly, because we can't guarantee all potential users are dumped for a specific file lock. Right now, we assume that all file lock users are taken into dump, and the <code>--file-locks</code> option should be used on both dump and restore stages if our app may use any file locks. Remember that file locks dump/restore can only be absolutely safe for container dumping (as a container, naturally, contains all the file locks users).

	Currently supported lock types are:		Currently supported lock types are:

@@ Line 1: / Line 1: @@
-Some app may use file locks for synchronization. Generally they will use flock or posix file locks, which were achieved by flock or fcntl system calls. For dump/restore, it is hard to be handled perfectly, because we can't guarantee all potential users are dumped for a specific file lock. Right now, we assume that all file lock users are taken into dump, and we should use the --file-locks option on both dump and restore stages if our app may use any file locks. Remember that file locks dump/restore is only safe for container dumping in theory.
+Some app may use file locks for synchronization. Generally they will use flock or POSIX file locks, which were achieved by flock or fcntl system calls. For dump/restore, it is hard to be handled perfectly, because we can't guarantee all potential users are dumped for a specific file lock. Right now, we assume that all file lock users are taken into dump, and we should use the <code>--file-locks</code> option on both dump and restore stages if our app may use any file locks. Remember that file locks dump/restore is only safe for container dumping in theory.
-Supported lock types are
+Currently supported lock types are:
+* <code>flock()</code> locks
-* flock() locks
+* POSIX (<code>fcntl</code>) locks
 * file leases
 * OFD locks