2012-07-18 19:07:51 +02:00
|
|
|
#pragma once
|
2011-07-22 04:21:18 +02:00
|
|
|
|
|
|
|
/***
|
|
|
|
This file is part of systemd.
|
|
|
|
|
|
|
|
Copyright 2011 Lennart Poettering
|
|
|
|
|
|
|
|
systemd is free software; you can redistribute it and/or modify it
|
2012-04-12 00:20:58 +02:00
|
|
|
under the terms of the GNU Lesser General Public License as published by
|
|
|
|
the Free Software Foundation; either version 2.1 of the License, or
|
2011-07-22 04:21:18 +02:00
|
|
|
(at your option) any later version.
|
|
|
|
|
|
|
|
systemd is distributed in the hope that it will be useful, but
|
|
|
|
WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
|
2012-04-12 00:20:58 +02:00
|
|
|
Lesser General Public License for more details.
|
2011-07-22 04:21:18 +02:00
|
|
|
|
2012-04-12 00:20:58 +02:00
|
|
|
You should have received a copy of the GNU Lesser General Public License
|
2011-07-22 04:21:18 +02:00
|
|
|
along with systemd; If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
***/
|
|
|
|
|
2015-05-11 22:53:54 +02:00
|
|
|
typedef enum UnitFileScope UnitFileScope;
|
|
|
|
typedef enum UnitFileState UnitFileState;
|
|
|
|
typedef enum UnitFilePresetMode UnitFilePresetMode;
|
|
|
|
typedef enum UnitFileChangeType UnitFileChangeType;
|
2016-10-20 14:48:33 +02:00
|
|
|
typedef enum UnitFileFlags UnitFileFlags;
|
install: follow unit file symlinks in /usr, but not /etc when looking for [Install] data
Some distributions use alias unit files via symlinks in /usr to cover
for legacy service names. With this change we'll allow "systemctl
enable" on such aliases.
Previously, our rule was that symlinks are user configuration that
"systemctl enable" + "systemctl disable" creates and removes, while unit
files is where the instructions to do so are store. As a result of the
rule we'd never read install information through symlinks, since that
would mix enablement state with installation instructions.
Now, the new rule is that only symlinks inside of /etc are
configuration. Unit files, and symlinks in /usr are now valid for
installation instructions.
This patch is quite a rework of the whole install logic, and makes the
following addional changes:
- Adds a complete test "test-instal-root" that tests the install logic
pretty comprehensively.
- Never uses canonicalize_file_name(), because that's incompatible with
operation relative to a specific root directory.
- unit_file_get_state() is reworked to return a proper error, and
returns the state in a call-by-ref parameter. This cleans up confusion
between the enum type and errno-like errors.
- The new logic puts a limit on how long to follow unit file symlinks:
it will do so only for 64 steps at max.
- The InstallContext object's fields are renamed to will_process and
has_processed (will_install and has_installed) since they are also
used for deinstallation and all kinds of other operations.
- The root directory is always verified before use.
- install.c is reordered to place the exported functions together.
- Stricter rules are followed when traversing symlinks: the unit suffix
must say identical, and it's not allowed to link between regular units
and templated units.
- Various modernizations
- The "invalid" unit file state has been renamed to "bad", in order to
avoid confusion between UNIT_FILE_INVALID and
_UNIT_FILE_STATE_INVALID. Given that the state should normally not be
seen and is not documented this should not be a problematic change.
The new name is now documented however.
Fixes #1375, #1718, #1706
2015-10-08 22:31:56 +02:00
|
|
|
typedef enum UnitFileType UnitFileType;
|
2015-05-11 22:53:54 +02:00
|
|
|
typedef struct UnitFileChange UnitFileChange;
|
|
|
|
typedef struct UnitFileList UnitFileList;
|
|
|
|
typedef struct UnitFileInstallInfo UnitFileInstallInfo;
|
|
|
|
|
2015-12-03 21:13:37 +01:00
|
|
|
#include <stdbool.h>
|
|
|
|
|
2011-07-22 04:21:18 +02:00
|
|
|
#include "hashmap.h"
|
2015-12-03 21:13:37 +01:00
|
|
|
#include "macro.h"
|
2015-03-15 02:46:59 +01:00
|
|
|
#include "path-lookup.h"
|
install: follow unit file symlinks in /usr, but not /etc when looking for [Install] data
Some distributions use alias unit files via symlinks in /usr to cover
for legacy service names. With this change we'll allow "systemctl
enable" on such aliases.
Previously, our rule was that symlinks are user configuration that
"systemctl enable" + "systemctl disable" creates and removes, while unit
files is where the instructions to do so are store. As a result of the
rule we'd never read install information through symlinks, since that
would mix enablement state with installation instructions.
Now, the new rule is that only symlinks inside of /etc are
configuration. Unit files, and symlinks in /usr are now valid for
installation instructions.
This patch is quite a rework of the whole install logic, and makes the
following addional changes:
- Adds a complete test "test-instal-root" that tests the install logic
pretty comprehensively.
- Never uses canonicalize_file_name(), because that's incompatible with
operation relative to a specific root directory.
- unit_file_get_state() is reworked to return a proper error, and
returns the state in a call-by-ref parameter. This cleans up confusion
between the enum type and errno-like errors.
- The new logic puts a limit on how long to follow unit file symlinks:
it will do so only for 64 steps at max.
- The InstallContext object's fields are renamed to will_process and
has_processed (will_install and has_installed) since they are also
used for deinstallation and all kinds of other operations.
- The root directory is always verified before use.
- install.c is reordered to place the exported functions together.
- Stricter rules are followed when traversing symlinks: the unit suffix
must say identical, and it's not allowed to link between regular units
and templated units.
- Various modernizations
- The "invalid" unit file state has been renamed to "bad", in order to
avoid confusion between UNIT_FILE_INVALID and
_UNIT_FILE_STATE_INVALID. Given that the state should normally not be
seen and is not documented this should not be a problematic change.
The new name is now documented however.
Fixes #1375, #1718, #1706
2015-10-08 22:31:56 +02:00
|
|
|
#include "strv.h"
|
|
|
|
#include "unit-name.h"
|
2011-07-22 04:21:18 +02:00
|
|
|
|
2015-05-11 22:53:54 +02:00
|
|
|
enum UnitFileScope {
|
2011-07-22 04:21:18 +02:00
|
|
|
UNIT_FILE_SYSTEM,
|
|
|
|
UNIT_FILE_GLOBAL,
|
|
|
|
UNIT_FILE_USER,
|
|
|
|
_UNIT_FILE_SCOPE_MAX,
|
|
|
|
_UNIT_FILE_SCOPE_INVALID = -1
|
2015-05-11 22:53:54 +02:00
|
|
|
};
|
2011-07-22 04:21:18 +02:00
|
|
|
|
2015-05-11 22:53:54 +02:00
|
|
|
enum UnitFileState {
|
2011-07-22 04:21:18 +02:00
|
|
|
UNIT_FILE_ENABLED,
|
|
|
|
UNIT_FILE_ENABLED_RUNTIME,
|
|
|
|
UNIT_FILE_LINKED,
|
|
|
|
UNIT_FILE_LINKED_RUNTIME,
|
|
|
|
UNIT_FILE_MASKED,
|
|
|
|
UNIT_FILE_MASKED_RUNTIME,
|
|
|
|
UNIT_FILE_STATIC,
|
|
|
|
UNIT_FILE_DISABLED,
|
2014-11-07 21:21:05 +01:00
|
|
|
UNIT_FILE_INDIRECT,
|
2016-02-24 15:44:46 +01:00
|
|
|
UNIT_FILE_GENERATED,
|
2016-03-07 19:07:30 +01:00
|
|
|
UNIT_FILE_TRANSIENT,
|
install: follow unit file symlinks in /usr, but not /etc when looking for [Install] data
Some distributions use alias unit files via symlinks in /usr to cover
for legacy service names. With this change we'll allow "systemctl
enable" on such aliases.
Previously, our rule was that symlinks are user configuration that
"systemctl enable" + "systemctl disable" creates and removes, while unit
files is where the instructions to do so are store. As a result of the
rule we'd never read install information through symlinks, since that
would mix enablement state with installation instructions.
Now, the new rule is that only symlinks inside of /etc are
configuration. Unit files, and symlinks in /usr are now valid for
installation instructions.
This patch is quite a rework of the whole install logic, and makes the
following addional changes:
- Adds a complete test "test-instal-root" that tests the install logic
pretty comprehensively.
- Never uses canonicalize_file_name(), because that's incompatible with
operation relative to a specific root directory.
- unit_file_get_state() is reworked to return a proper error, and
returns the state in a call-by-ref parameter. This cleans up confusion
between the enum type and errno-like errors.
- The new logic puts a limit on how long to follow unit file symlinks:
it will do so only for 64 steps at max.
- The InstallContext object's fields are renamed to will_process and
has_processed (will_install and has_installed) since they are also
used for deinstallation and all kinds of other operations.
- The root directory is always verified before use.
- install.c is reordered to place the exported functions together.
- Stricter rules are followed when traversing symlinks: the unit suffix
must say identical, and it's not allowed to link between regular units
and templated units.
- Various modernizations
- The "invalid" unit file state has been renamed to "bad", in order to
avoid confusion between UNIT_FILE_INVALID and
_UNIT_FILE_STATE_INVALID. Given that the state should normally not be
seen and is not documented this should not be a problematic change.
The new name is now documented however.
Fixes #1375, #1718, #1706
2015-10-08 22:31:56 +02:00
|
|
|
UNIT_FILE_BAD,
|
2011-07-22 04:21:18 +02:00
|
|
|
_UNIT_FILE_STATE_MAX,
|
|
|
|
_UNIT_FILE_STATE_INVALID = -1
|
2015-05-11 22:53:54 +02:00
|
|
|
};
|
2011-07-22 04:21:18 +02:00
|
|
|
|
2015-05-11 22:53:54 +02:00
|
|
|
enum UnitFilePresetMode {
|
2014-06-16 19:49:31 +02:00
|
|
|
UNIT_FILE_PRESET_FULL,
|
|
|
|
UNIT_FILE_PRESET_ENABLE_ONLY,
|
|
|
|
UNIT_FILE_PRESET_DISABLE_ONLY,
|
2014-07-10 04:29:24 +02:00
|
|
|
_UNIT_FILE_PRESET_MAX,
|
2014-06-16 19:49:31 +02:00
|
|
|
_UNIT_FILE_PRESET_INVALID = -1
|
2015-05-11 22:53:54 +02:00
|
|
|
};
|
2014-06-16 19:49:31 +02:00
|
|
|
|
2015-05-11 22:53:54 +02:00
|
|
|
enum UnitFileChangeType {
|
2011-07-22 04:21:18 +02:00
|
|
|
UNIT_FILE_SYMLINK,
|
|
|
|
UNIT_FILE_UNLINK,
|
2016-04-17 01:31:53 +02:00
|
|
|
UNIT_FILE_IS_MASKED,
|
2016-05-04 16:10:57 +02:00
|
|
|
UNIT_FILE_IS_DANGLING,
|
2011-07-22 04:21:18 +02:00
|
|
|
_UNIT_FILE_CHANGE_TYPE_MAX,
|
2016-04-19 06:04:35 +02:00
|
|
|
_UNIT_FILE_CHANGE_INVALID = INT_MIN
|
2015-05-11 22:53:54 +02:00
|
|
|
};
|
2011-07-22 04:21:18 +02:00
|
|
|
|
2016-10-20 14:48:33 +02:00
|
|
|
enum UnitFileFlags {
|
|
|
|
UNIT_FILE_RUNTIME = 1,
|
|
|
|
UNIT_FILE_FORCE = 1 << 1,
|
2016-10-20 15:20:11 +02:00
|
|
|
UNIT_FILE_DRY_RUN = 1 << 2,
|
2016-10-20 14:48:33 +02:00
|
|
|
};
|
|
|
|
|
2016-04-17 16:16:44 +02:00
|
|
|
/* type can either one of the UnitFileChangeTypes listed above, or a negative error.
|
|
|
|
* If source is specified, it should be the contents of the path symlink.
|
|
|
|
* In case of an error, source should be the existing symlink contents or NULL
|
|
|
|
*/
|
2015-05-11 22:53:54 +02:00
|
|
|
struct UnitFileChange {
|
2016-04-17 16:16:44 +02:00
|
|
|
int type; /* UnitFileChangeType or bust */
|
2011-07-22 04:21:18 +02:00
|
|
|
char *path;
|
|
|
|
char *source;
|
2015-05-11 22:53:54 +02:00
|
|
|
};
|
2011-07-22 04:21:18 +02:00
|
|
|
|
2016-04-17 21:56:46 +02:00
|
|
|
static inline bool unit_file_changes_have_modification(const UnitFileChange* changes, unsigned n_changes) {
|
|
|
|
unsigned i;
|
|
|
|
for (i = 0; i < n_changes; i++)
|
|
|
|
if (IN_SET(changes[i].type, UNIT_FILE_SYMLINK, UNIT_FILE_UNLINK))
|
|
|
|
return true;
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
2015-05-11 22:53:54 +02:00
|
|
|
struct UnitFileList {
|
2011-07-22 04:21:18 +02:00
|
|
|
char *path;
|
|
|
|
UnitFileState state;
|
2015-05-11 22:53:54 +02:00
|
|
|
};
|
2011-07-22 04:21:18 +02:00
|
|
|
|
install: follow unit file symlinks in /usr, but not /etc when looking for [Install] data
Some distributions use alias unit files via symlinks in /usr to cover
for legacy service names. With this change we'll allow "systemctl
enable" on such aliases.
Previously, our rule was that symlinks are user configuration that
"systemctl enable" + "systemctl disable" creates and removes, while unit
files is where the instructions to do so are store. As a result of the
rule we'd never read install information through symlinks, since that
would mix enablement state with installation instructions.
Now, the new rule is that only symlinks inside of /etc are
configuration. Unit files, and symlinks in /usr are now valid for
installation instructions.
This patch is quite a rework of the whole install logic, and makes the
following addional changes:
- Adds a complete test "test-instal-root" that tests the install logic
pretty comprehensively.
- Never uses canonicalize_file_name(), because that's incompatible with
operation relative to a specific root directory.
- unit_file_get_state() is reworked to return a proper error, and
returns the state in a call-by-ref parameter. This cleans up confusion
between the enum type and errno-like errors.
- The new logic puts a limit on how long to follow unit file symlinks:
it will do so only for 64 steps at max.
- The InstallContext object's fields are renamed to will_process and
has_processed (will_install and has_installed) since they are also
used for deinstallation and all kinds of other operations.
- The root directory is always verified before use.
- install.c is reordered to place the exported functions together.
- Stricter rules are followed when traversing symlinks: the unit suffix
must say identical, and it's not allowed to link between regular units
and templated units.
- Various modernizations
- The "invalid" unit file state has been renamed to "bad", in order to
avoid confusion between UNIT_FILE_INVALID and
_UNIT_FILE_STATE_INVALID. Given that the state should normally not be
seen and is not documented this should not be a problematic change.
The new name is now documented however.
Fixes #1375, #1718, #1706
2015-10-08 22:31:56 +02:00
|
|
|
enum UnitFileType {
|
|
|
|
UNIT_FILE_TYPE_REGULAR,
|
|
|
|
UNIT_FILE_TYPE_SYMLINK,
|
|
|
|
UNIT_FILE_TYPE_MASKED,
|
|
|
|
_UNIT_FILE_TYPE_MAX,
|
|
|
|
_UNIT_FILE_TYPE_INVALID = -1,
|
|
|
|
};
|
|
|
|
|
2015-05-11 22:53:54 +02:00
|
|
|
struct UnitFileInstallInfo {
|
2013-01-28 05:11:31 +01:00
|
|
|
char *name;
|
|
|
|
char *path;
|
|
|
|
|
|
|
|
char **aliases;
|
|
|
|
char **wanted_by;
|
|
|
|
char **required_by;
|
2014-11-07 21:21:05 +01:00
|
|
|
char **also;
|
2014-06-17 00:15:31 +02:00
|
|
|
|
|
|
|
char *default_instance;
|
2016-10-17 02:56:31 +02:00
|
|
|
char *symlink_target;
|
install: follow unit file symlinks in /usr, but not /etc when looking for [Install] data
Some distributions use alias unit files via symlinks in /usr to cover
for legacy service names. With this change we'll allow "systemctl
enable" on such aliases.
Previously, our rule was that symlinks are user configuration that
"systemctl enable" + "systemctl disable" creates and removes, while unit
files is where the instructions to do so are store. As a result of the
rule we'd never read install information through symlinks, since that
would mix enablement state with installation instructions.
Now, the new rule is that only symlinks inside of /etc are
configuration. Unit files, and symlinks in /usr are now valid for
installation instructions.
This patch is quite a rework of the whole install logic, and makes the
following addional changes:
- Adds a complete test "test-instal-root" that tests the install logic
pretty comprehensively.
- Never uses canonicalize_file_name(), because that's incompatible with
operation relative to a specific root directory.
- unit_file_get_state() is reworked to return a proper error, and
returns the state in a call-by-ref parameter. This cleans up confusion
between the enum type and errno-like errors.
- The new logic puts a limit on how long to follow unit file symlinks:
it will do so only for 64 steps at max.
- The InstallContext object's fields are renamed to will_process and
has_processed (will_install and has_installed) since they are also
used for deinstallation and all kinds of other operations.
- The root directory is always verified before use.
- install.c is reordered to place the exported functions together.
- Stricter rules are followed when traversing symlinks: the unit suffix
must say identical, and it's not allowed to link between regular units
and templated units.
- Various modernizations
- The "invalid" unit file state has been renamed to "bad", in order to
avoid confusion between UNIT_FILE_INVALID and
_UNIT_FILE_STATE_INVALID. Given that the state should normally not be
seen and is not documented this should not be a problematic change.
The new name is now documented however.
Fixes #1375, #1718, #1706
2015-10-08 22:31:56 +02:00
|
|
|
|
|
|
|
UnitFileType type;
|
2016-10-17 02:56:31 +02:00
|
|
|
bool auxiliary;
|
2015-05-11 22:53:54 +02:00
|
|
|
};
|
2013-01-28 05:11:31 +01:00
|
|
|
|
2016-04-30 22:21:41 +02:00
|
|
|
bool unit_type_may_alias(UnitType type) _const_;
|
2016-05-01 00:34:13 +02:00
|
|
|
bool unit_type_may_template(UnitType type) _const_;
|
2016-04-30 22:21:41 +02:00
|
|
|
|
2016-04-17 21:43:16 +02:00
|
|
|
int unit_file_enable(
|
|
|
|
UnitFileScope scope,
|
2016-10-20 14:48:33 +02:00
|
|
|
UnitFileFlags flags,
|
2016-04-17 21:43:16 +02:00
|
|
|
const char *root_dir,
|
|
|
|
char **files,
|
|
|
|
UnitFileChange **changes,
|
|
|
|
unsigned *n_changes);
|
|
|
|
int unit_file_disable(
|
|
|
|
UnitFileScope scope,
|
2016-10-20 14:48:33 +02:00
|
|
|
UnitFileFlags flags,
|
2016-04-17 21:43:16 +02:00
|
|
|
const char *root_dir,
|
|
|
|
char **files,
|
|
|
|
UnitFileChange **changes,
|
|
|
|
unsigned *n_changes);
|
|
|
|
int unit_file_reenable(
|
|
|
|
UnitFileScope scope,
|
2016-10-20 14:48:33 +02:00
|
|
|
UnitFileFlags flags,
|
2016-04-17 21:43:16 +02:00
|
|
|
const char *root_dir,
|
|
|
|
char **files,
|
|
|
|
UnitFileChange **changes,
|
|
|
|
unsigned *n_changes);
|
|
|
|
int unit_file_preset(
|
|
|
|
UnitFileScope scope,
|
2016-10-20 14:48:33 +02:00
|
|
|
UnitFileFlags flags,
|
2016-04-17 21:43:16 +02:00
|
|
|
const char *root_dir,
|
|
|
|
char **files,
|
|
|
|
UnitFilePresetMode mode,
|
|
|
|
UnitFileChange **changes,
|
|
|
|
unsigned *n_changes);
|
|
|
|
int unit_file_preset_all(
|
|
|
|
UnitFileScope scope,
|
2016-10-20 14:48:33 +02:00
|
|
|
UnitFileFlags flags,
|
2016-04-17 21:43:16 +02:00
|
|
|
const char *root_dir,
|
|
|
|
UnitFilePresetMode mode,
|
|
|
|
UnitFileChange **changes,
|
|
|
|
unsigned *n_changes);
|
|
|
|
int unit_file_mask(
|
|
|
|
UnitFileScope scope,
|
2016-10-20 14:48:33 +02:00
|
|
|
UnitFileFlags flags,
|
2016-04-17 21:43:16 +02:00
|
|
|
const char *root_dir,
|
|
|
|
char **files,
|
|
|
|
UnitFileChange **changes,
|
|
|
|
unsigned *n_changes);
|
|
|
|
int unit_file_unmask(
|
|
|
|
UnitFileScope scope,
|
2016-10-20 14:48:33 +02:00
|
|
|
UnitFileFlags flags,
|
2016-04-17 21:43:16 +02:00
|
|
|
const char *root_dir,
|
|
|
|
char **files,
|
|
|
|
UnitFileChange **changes,
|
|
|
|
unsigned *n_changes);
|
|
|
|
int unit_file_link(
|
|
|
|
UnitFileScope scope,
|
2016-10-20 14:48:33 +02:00
|
|
|
UnitFileFlags flags,
|
2016-04-17 21:43:16 +02:00
|
|
|
const char *root_dir,
|
|
|
|
char **files,
|
|
|
|
UnitFileChange **changes,
|
|
|
|
unsigned *n_changes);
|
|
|
|
int unit_file_revert(
|
|
|
|
UnitFileScope scope,
|
|
|
|
const char *root_dir,
|
|
|
|
char **files,
|
|
|
|
UnitFileChange **changes,
|
|
|
|
unsigned *n_changes);
|
|
|
|
int unit_file_set_default(
|
|
|
|
UnitFileScope scope,
|
2016-10-20 14:48:33 +02:00
|
|
|
UnitFileFlags flags,
|
2016-04-17 21:43:16 +02:00
|
|
|
const char *root_dir,
|
|
|
|
const char *file,
|
|
|
|
UnitFileChange **changes,
|
|
|
|
unsigned *n_changes);
|
|
|
|
int unit_file_get_default(
|
|
|
|
UnitFileScope scope,
|
|
|
|
const char *root_dir,
|
|
|
|
char **name);
|
|
|
|
int unit_file_add_dependency(
|
|
|
|
UnitFileScope scope,
|
2016-10-20 14:48:33 +02:00
|
|
|
UnitFileFlags flags,
|
2016-04-17 21:43:16 +02:00
|
|
|
const char *root_dir,
|
|
|
|
char **files,
|
|
|
|
const char *target,
|
|
|
|
UnitDependency dep,
|
|
|
|
UnitFileChange **changes,
|
|
|
|
unsigned *n_changes);
|
2011-07-22 04:21:18 +02:00
|
|
|
|
install: follow unit file symlinks in /usr, but not /etc when looking for [Install] data
Some distributions use alias unit files via symlinks in /usr to cover
for legacy service names. With this change we'll allow "systemctl
enable" on such aliases.
Previously, our rule was that symlinks are user configuration that
"systemctl enable" + "systemctl disable" creates and removes, while unit
files is where the instructions to do so are store. As a result of the
rule we'd never read install information through symlinks, since that
would mix enablement state with installation instructions.
Now, the new rule is that only symlinks inside of /etc are
configuration. Unit files, and symlinks in /usr are now valid for
installation instructions.
This patch is quite a rework of the whole install logic, and makes the
following addional changes:
- Adds a complete test "test-instal-root" that tests the install logic
pretty comprehensively.
- Never uses canonicalize_file_name(), because that's incompatible with
operation relative to a specific root directory.
- unit_file_get_state() is reworked to return a proper error, and
returns the state in a call-by-ref parameter. This cleans up confusion
between the enum type and errno-like errors.
- The new logic puts a limit on how long to follow unit file symlinks:
it will do so only for 64 steps at max.
- The InstallContext object's fields are renamed to will_process and
has_processed (will_install and has_installed) since they are also
used for deinstallation and all kinds of other operations.
- The root directory is always verified before use.
- install.c is reordered to place the exported functions together.
- Stricter rules are followed when traversing symlinks: the unit suffix
must say identical, and it's not allowed to link between regular units
and templated units.
- Various modernizations
- The "invalid" unit file state has been renamed to "bad", in order to
avoid confusion between UNIT_FILE_INVALID and
_UNIT_FILE_STATE_INVALID. Given that the state should normally not be
seen and is not documented this should not be a problematic change.
The new name is now documented however.
Fixes #1375, #1718, #1706
2015-10-08 22:31:56 +02:00
|
|
|
int unit_file_get_state(UnitFileScope scope, const char *root_dir, const char *filename, UnitFileState *ret);
|
2016-04-07 17:40:11 +02:00
|
|
|
int unit_file_exists(UnitFileScope scope, const LookupPaths *paths, const char *name);
|
2011-07-22 04:21:18 +02:00
|
|
|
|
2016-04-29 15:59:51 +02:00
|
|
|
int unit_file_get_list(UnitFileScope scope, const char *root_dir, Hashmap *h, char **states, char **patterns);
|
install: follow unit file symlinks in /usr, but not /etc when looking for [Install] data
Some distributions use alias unit files via symlinks in /usr to cover
for legacy service names. With this change we'll allow "systemctl
enable" on such aliases.
Previously, our rule was that symlinks are user configuration that
"systemctl enable" + "systemctl disable" creates and removes, while unit
files is where the instructions to do so are store. As a result of the
rule we'd never read install information through symlinks, since that
would mix enablement state with installation instructions.
Now, the new rule is that only symlinks inside of /etc are
configuration. Unit files, and symlinks in /usr are now valid for
installation instructions.
This patch is quite a rework of the whole install logic, and makes the
following addional changes:
- Adds a complete test "test-instal-root" that tests the install logic
pretty comprehensively.
- Never uses canonicalize_file_name(), because that's incompatible with
operation relative to a specific root directory.
- unit_file_get_state() is reworked to return a proper error, and
returns the state in a call-by-ref parameter. This cleans up confusion
between the enum type and errno-like errors.
- The new logic puts a limit on how long to follow unit file symlinks:
it will do so only for 64 steps at max.
- The InstallContext object's fields are renamed to will_process and
has_processed (will_install and has_installed) since they are also
used for deinstallation and all kinds of other operations.
- The root directory is always verified before use.
- install.c is reordered to place the exported functions together.
- Stricter rules are followed when traversing symlinks: the unit suffix
must say identical, and it's not allowed to link between regular units
and templated units.
- Various modernizations
- The "invalid" unit file state has been renamed to "bad", in order to
avoid confusion between UNIT_FILE_INVALID and
_UNIT_FILE_STATE_INVALID. Given that the state should normally not be
seen and is not documented this should not be a problematic change.
The new name is now documented however.
Fixes #1375, #1718, #1706
2015-10-08 22:31:56 +02:00
|
|
|
Hashmap* unit_file_list_free(Hashmap *h);
|
2011-07-22 04:21:18 +02:00
|
|
|
|
2015-05-15 09:54:10 +02:00
|
|
|
int unit_file_changes_add(UnitFileChange **changes, unsigned *n_changes, UnitFileChangeType type, const char *path, const char *source);
|
2011-07-22 04:21:18 +02:00
|
|
|
void unit_file_changes_free(UnitFileChange *changes, unsigned n_changes);
|
2016-04-17 16:16:44 +02:00
|
|
|
void unit_file_dump_changes(int r, const char *verb, const UnitFileChange *changes, unsigned n_changes, bool quiet);
|
2011-07-22 04:21:18 +02:00
|
|
|
|
2014-06-16 20:33:29 +02:00
|
|
|
int unit_file_query_preset(UnitFileScope scope, const char *root_dir, const char *name);
|
2011-07-22 04:21:18 +02:00
|
|
|
|
2013-05-03 04:51:50 +02:00
|
|
|
const char *unit_file_state_to_string(UnitFileState s) _const_;
|
|
|
|
UnitFileState unit_file_state_from_string(const char *s) _pure_;
|
2016-04-19 06:04:35 +02:00
|
|
|
/* from_string conversion is unreliable because of the overlap between -EPERM and -1 for error. */
|
2011-07-22 04:21:18 +02:00
|
|
|
|
2013-05-03 04:51:50 +02:00
|
|
|
const char *unit_file_change_type_to_string(UnitFileChangeType s) _const_;
|
|
|
|
UnitFileChangeType unit_file_change_type_from_string(const char *s) _pure_;
|
2014-06-16 19:49:31 +02:00
|
|
|
|
|
|
|
const char *unit_file_preset_mode_to_string(UnitFilePresetMode m) _const_;
|
|
|
|
UnitFilePresetMode unit_file_preset_mode_from_string(const char *s) _pure_;
|