summaryrefslogtreecommitdiff
path: root/src/system-update-generator
diff options
context:
space:
mode:
authorZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2015-01-26 07:34:32 +0100
committerLennart Poettering <lennart@poettering.net>2015-01-27 01:29:02 +0100
commit6b321a790142449e0cf3685ffa5294e147d692f7 (patch)
tree2425fc5c6a7462290e4b99b2b6ccd1440c3efbb0 /src/system-update-generator
parent7fd68245a1778e187376736285fd89b968b9731c (diff)
system-update-generator: accept a dangling symlink
The offline update mechanism is explicitly designed to work with a separate /var. systemd-update-generator is supposed to run early, before filesystems are mounted, so it cannot check if the /system-update symlink actually points to anything. The update is run *after* filesystems are mounted, so it should be able to access the target of the symlink without trouble. https://bugzilla.redhat.com/show_bug.cgi?id=1178978
Diffstat (limited to 'src/system-update-generator')
-rw-r--r--src/system-update-generator/system-update-generator.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/system-update-generator/system-update-generator.c b/src/system-update-generator/system-update-generator.c
index 464ee22b20..455a84109b 100644
--- a/src/system-update-generator/system-update-generator.c
+++ b/src/system-update-generator/system-update-generator.c
@@ -37,7 +37,7 @@ static const char *arg_dest = "/tmp";
static int generate_symlink(void) {
const char *p = NULL;
- if (access("/system-update", F_OK) < 0) {
+ if (laccess("/system-update", F_OK) < 0) {
if (errno == ENOENT)
return 0;