IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
"We use it to pass $DAEMON_OPTS variable to pmxcfs, which is empty per
default.
pmxcfs accepts following options at the moment:
> Usage:
> pmxcfs [OPTION...]
>
> Help Options:
> -h, --help Show help options
>
> Application Options:
> -d, --debug Turn on debug messages
> -f, --foreground Do not daemonize server
> -l, --local Force local mode (ignore corosync.conf,
> force quorum)
"help" can be safely ignored, as can "foreground" - it would break
the service as the Type is forking and thus systemd would expect that
the starting process returns rather quickly and kill it after the
timeout thinking the start failed when this is set.
Then there is "debug", while this is quite safe to use I do not
expect to find it in the wild. 1) it *spams* the logs in such a heavy
manner that it's useless for a user 2) if wished it can be
enabled/disable on the fly by writing 1/0 to /etc/pve/.debug (which
is what we tell people in docs, et al. anyway) So this parameter is
also quite safe to ignore, IMO.
Then there is "local", now this can be enabled but is such evil
and wrong so that anybody setting it *permanently*, deserves to
be saved by not allowing him to do so. If somebody uses this we
should hope that he did out of not knowing better and is actually
thankful when he learns what this meant."
https://pve.proxmox.com/pipermail/pve-devel/2017-November/029527.html
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
we only executed a 'pvecm updatecerts --silent there', but we do this
already in the systemd service in ExecStartPost, so
this is unnecessary
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
This should prevent issues when generating certificates on
first boot of a node with the RTC wrongly set to the local
timezone instead of UTC. Since we cannot require the node to
be synchronized with an NTP server, we pretend it's
yesterday when calling openssl.