mirror of
https://github.com/xen-project/xen.git
synced 2026-10-28 18:21:39 +01:00
Olaf Hering
9d628ff6cc
On a fedora system, if you run `sudo sh install.sh` you break your system. The installation clobbers /var/run, a symlink to /run. A subsequent boot fails when /var/run and /run are different since accesses through /var/run can't find items that now only exist in /run and vice-versa. Skip populating /var/run/xen during make install. The directory is already created by some scripts. Adjust all remaining scripts to create XEN_RUN_DIR at runtime. Use the shell variable XEN_RUN_DIR instead of hardcoded paths. XEN_RUN_STORED is covered by XEN_RUN_DIR because xenstored is usually started afterwards. Reported-by: Jason Andryuk <jandryuk@gmail.com> Signed-off-by: Olaf Hering <olaf@aepfle.de> Tested-by: Jason Andryuk <jandryuk@gmail.com> Reviewed-by: Anthony PERARD <anthony.perard@citrix.com>
19 lines
683 B
Plaintext
19 lines
683 B
Plaintext
[Unit]
|
|
Description=Xenconsoled - handles logging from guest consoles and hypervisor
|
|
Requires=proc-xen.mount xenstored.service
|
|
After=proc-xen.mount xenstored.service
|
|
ConditionPathExists=/proc/xen/capabilities
|
|
|
|
[Service]
|
|
Type=simple
|
|
Environment=XENCONSOLED_ARGS=
|
|
Environment=XENCONSOLED_TRACE=none
|
|
Environment=XENCONSOLED_LOG_DIR=@XEN_LOG_DIR@/console
|
|
EnvironmentFile=-@CONFIG_DIR@/@CONFIG_LEAF_DIR@/xencommons
|
|
ExecStartPre=/bin/grep -q control_d /proc/xen/capabilities
|
|
ExecStartPre=/bin/mkdir -p ${XENCONSOLED_LOG_DIR} @XEN_RUN_DIR@
|
|
ExecStart=@sbindir@/xenconsoled -i --log=${XENCONSOLED_TRACE} --log-dir=${XENCONSOLED_LOG_DIR} $XENCONSOLED_ARGS
|
|
|
|
[Install]
|
|
WantedBy=multi-user.target
|