File: lockfile.h

package info (click to toggle)
flang 20181226-2
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 181,072 kB
  • sloc: cpp: 1,182,685; ansic: 598,652; objc: 103,775; f90: 57,054; python: 15,041; fortran: 13,601; lisp: 10,416; perl: 2,460; asm: 2,148; sh: 1,544; awk: 995; cs: 565; xml: 403; lex: 295; makefile: 225; pascal: 130
file content (68 lines) | stat: -rw-r--r-- 2,076 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
/*
 * Copyright (c) 2006-2018, NVIDIA CORPORATION.  All rights reserved.
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *     http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 *
 */

/**
   \file

   Four routines to be able to lock access to a file in the Linux
   approved manner.  This seems to be the only method that works
   over NFS.
 */

#ifdef __cplusplus
extern "C" {
#endif

/**
   \brief Creates a uniquely-named file in the current directory.

   To work, this must be created on the same filesystem as the file which we are
   attempting to lock.  If there are multiple processes running each competing
   for the same lock, each gets a unique file here.
 */
int __pg_make_lock_file(char *dir);

/**
   \brief The argument is the name of the lock.

   Each process tries to create a hard link with this name to its own
   uniquely-named file from __pg_make_lock_file().  The one that succeeds is the
   new lock owner.  The others fail and try again.  There is a fail-over to
   handle the case where the process with the lock dies, which is inherently
   unsafe, but we haven't come up with a better solution.
 */
void __pg_get_lock(char *lname);

/**
   \brief The argument is the same name for the lock.

   The lock is released by deleting (calling unlink) for the hard link we had
   just created.
 */
void __pg_release_lock(char *lname);

/**
   \brief Clean up by deleting the uniquely named file we had created earlier.

   These routines only allow one lock to be managed at a time.  They dynamically
   allocate and free memory.
 */
void __pg_delete_lock_file(void);

#ifdef __cplusplus
}
#endif