Proxmox/pve-docs
5
0
Fork 0
mirror of git://git.proxmox.com/git/pve-docs.git synced 2025-03-19 18:50:06 +03:00
Code Releases Activity

simplify/cleanup previous commit

Browse Source
This commit is contained in:
Dietmar Maurer 2016-05-19 06:39:39 +02:00
parent 25535d343f
commit 37638f5933
1 changed files with 15 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
pct.adoc
View File

@ -207,26 +207,26 @@ randomize crontab:: so that cron does not start at the same time on all containe
Changes made by {PVE} are enclosed by comment markers:
# --- BEGIN PVE ---
<data>
# --- END PVE ---
----
# --- BEGIN PVE ---
<data>
# --- END PVE ---
----
If no such section is found it will be inserted at a reasonable location
in the file.
Those markers will be inserted at a reasonable location in the
file. If such a section already exists, it will be updated in place
and will not be moved.
If such a section already exists it will be updated in place and will not be
moved.
Modification of a file can be prevented by adding a `.pve-ignore.` file for it.
For instance, if the file `/etc/.pve-ignore.hosts` exists then the
`/etc/hosts` file will not be touched. (This can be a simple empty file creatd
via:
Modification of a file can be prevented by adding a `.pve-ignore.`
file for it. For instance, if the file `/etc/.pve-ignore.hosts`
exists then the `/etc/hosts` file will not be touched. This can be a
simple empty file creatd via:
# touch /etc/.pve-ignore.hosts
The above tasks are OS dependent and so they differ between different
distributions. You can also disable all modifications entirely by manually
setting the 'ostype' to 'unmanaged'.
Most modifications are OS dependent, so they differ between different
distributions and versions. You can completely disable modifications
by manually setting the 'ostype' to 'unmanaged'.
OS type detection is done by testing for certain files inside the
container: