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!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
proxmox-firewall does not require firewall bridges if the interface is
on a linux bridge. It still creates firewall bridges for OVS, since
otherwise the traffic of the interface is not visible in netfilter.
Document this behavior explicitly as it hasn't been mentioned in the
documentation before.
Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
Reviewed-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
While I opened an issue for asciidoc.py two years ago [0], describing
the underlying regression and a simple potential fix, there was no
reaction whatsoever. I now also opened a PR [1] but let's see what
happens in the next two years, ideally I do not have to care about
this one way or there other.
This is basically a semantic copy of commit 393cdae ("d/control:
ensure docs are build with compatible asciidoc").
[0]: https://github.com/asciidoc-py/asciidoc-py/issues/266
[1]: https://github.com/asciidoc-py/asciidoc-py/pull/277
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
Because 'apt-get upgrade' or 'apt upgrade' will not pull in potential
new dependencies and that could lead to a broken system.
'apt-get dist-ugprade' or 'apt full-upgrade' will install new
dependencies when needed.
Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
This section is meant to give a basic overview on how to use
custom templates for notifications. It will be expanded in the
future, providing a more detailed view on how templates are resolved,
existing fallback mechanisms, available templates, template
variables and helpers.
Signed-off-by: Lukas Wagner <l.wagner@proxmox.com>
Reviewed-by: Alexander Zeidler <a.zeidler@proxmox.com>
Link: https://lore.proxmox.com/20250409074713.55474-1-l.wagner@proxmox.com
VirtIO-fs using writeback cache seems very broken at the moment. If a
guest accesses a file (even just using 'touch'), that the host is
currently writing, the guest can permanently end up with a truncated
version of that file. Even subsequent operations like moving the file,
will not result in the correct file being visible, but just rename the
truncated one.
Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
As reported in the community forum [0], for tar, an exclusion pattern
with a trailing slash will not match a folder with that name. For
rsync and proxmox-backup-client however, such a pattern will exclude
a directory with that name, but not a file.
rsync is used for 'suspend' mode backup and tar is used for all
non-PBS backups to create the archive. So currently, in the presence
of an exclusion pattern with a trailing slash, there is inconsistency
between different backup modes (because for 'suspend' mode, rsync will
already do the exclusion too) as well as between PBS and non-PBS
backups.
There doesn't seem to be a straight-forward way to align the behavior
for tar with command-line options exactly. The trailing slash can't be
removed from the pattern, because that would also match files.
Matching with
> some/pattern/*
> some/pattern/.*
rather than
> some/pattern/
gets pretty close, which was suggested by Dominik. Just the empty
directory is still included.
In any case, modifying current behavior would be a breaking change, so
actually aligning the exclusion (more closely) is better done in the
next major release.
Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
Make the PVE machines a sub point of the overall machine version, as
they are not really different, but only extend the mechanism we
already used by something we can directly control. I tried to extend
the previously existing machine version to also describe that we use
that version for deciding what to enabled/change on the PVE side,
i.e., not just what QEMU exposes, and also reduce some verbosity with
regard to implementation details.
While at it, I replaced the first-person plural (we) use with third
person indicative mood as documented in our style guide [0].
[0]: https://pve.proxmox.com/wiki/Technical_Writing_Style_Guide#Person_and_Mood
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
Signed-off-by: Gabriel Goller <g.goller@proxmox.com>
[TL: prefix anchor with gui_ like all others in the chapter...]
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
/etc/pve/priv/realm has been the default path since commit
782b702db ("auth ldap/ad: make password a parameter for the api")
That commit was part of pve-access-control 6.0-7.
Replace /etc/pve/priv/ldap with /etc/pve/priv/realm, to avoid pointing
users to the deprecated path.
It's not used anywhere in our code too, except as (very) old fallback.
Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
