diff --git a/.doctrees/configuration.doctree b/.doctrees/configuration.doctree new file mode 100644 index 0000000..4552006 Binary files /dev/null and b/.doctrees/configuration.doctree differ diff --git a/.doctrees/environment.pickle b/.doctrees/environment.pickle index 5806e7c..2a20d00 100644 Binary files a/.doctrees/environment.pickle and b/.doctrees/environment.pickle differ diff --git a/.doctrees/examples.doctree b/.doctrees/examples.doctree new file mode 100644 index 0000000..942c04a Binary files /dev/null and b/.doctrees/examples.doctree differ diff --git a/.doctrees/faq.doctree b/.doctrees/faq.doctree new file mode 100644 index 0000000..ebca619 Binary files /dev/null and b/.doctrees/faq.doctree differ diff --git a/.doctrees/index.doctree b/.doctrees/index.doctree index d6356ea..6bb10ef 100644 Binary files a/.doctrees/index.doctree and b/.doctrees/index.doctree differ diff --git a/.doctrees/installation.doctree b/.doctrees/installation.doctree new file mode 100644 index 0000000..d68121c Binary files /dev/null and b/.doctrees/installation.doctree differ diff --git a/.doctrees/troubleshooting.doctree b/.doctrees/troubleshooting.doctree new file mode 100644 index 0000000..98aad57 Binary files /dev/null and b/.doctrees/troubleshooting.doctree differ diff --git a/_sources/configuration.rst.txt b/_sources/configuration.rst.txt new file mode 100644 index 0000000..f177075 --- /dev/null +++ b/_sources/configuration.rst.txt @@ -0,0 +1,34 @@ +Configuration +============= + +.. toctree:: + :maxdepth: 2 + +Configuration is done via Python ini configuration files. The defaults +should be suitable for most users, so you may not need to do any configuration at all. +By default only the ``root`` snapper configuration is snapshotted. + +A commented example configuration files is located at ``/etc/snap-pac.ini.example``. + +To configure, copy the example configuration file: + +.. code-block:: bash + + cp /etc/snap-pac.ini{.example,} + +Then edit with your favorite editor. The file is commented and should be +self-explanatory. + +Each section corresponds with a snapper configuration. Add additional sections to add +other snapper configurations to be snapshotted. By default, only the root configuration +is snapshotted. + +Environment Variables +--------------------- + +To temporarily prevent snapshots from being performed for a single pacman +command, set the environment variable ``SNAP_PAC_SKIP``. For example: + +.. code-block:: bash + + sudo SNAP_PAC_SKIP=y pacman -Syu diff --git a/_sources/examples.rst.txt b/_sources/examples.rst.txt new file mode 100644 index 0000000..5877ed1 --- /dev/null +++ b/_sources/examples.rst.txt @@ -0,0 +1,92 @@ +Example +======= + +.. toctree:: + :maxdepth: 2 + +Here is an example of how the snapshots are created and how to rollback and pacman +transaction. Here the nano package is installed: + +.. code-block:: bash + + pacman -S nano + +.. code-block:: none + + resolving dependencies... + looking for conflicting packages... + + Packages (1) nano-2.5.3-1 + + Total Installed Size: 2.14 MiB + + :: Proceed with installation? [Y/n] Y + (1/1) checking keys in keyring [######################################] 100% + (1/1) checking package integrity [######################################] 100% + (1/1) loading package files [######################################] 100% + (1/1) checking for file conflicts [######################################] 100% + (1/1) checking available disk space [######################################] 100% + :: Running pre-transaction hooks... + (1/1) Performing snapper pre snapshots for the following configurations... + => root: 1033 + :: Processing package changes... + (1/1) installing nano [######################################] 100% + :: Running post-transaction hooks... + (1/1) Performing snapper post snapshots for the following configurations... + => root: 1034 + +The snapper snapshot number is given for each snapper configuration that is used. This +is also logged in pacman's log. + +Here are the snapshots created before and after the pacman transaction: + +.. code-block:: bash + + snapper -c root list -t pre-post | tail -n 1 + +.. code-block:: none + + 1033 | 1034 | Fri 22 Apr 2016 01:54:13 PM CDT | Fri 22 Apr 2016 01:54:14 PM CDT | pacman -S nano | + +Here is what changed during the transaction: + +.. code-block:: bash + + snapper -c root status 1033..1034 + +.. code-block:: none + + +..... /etc/nanorc + c..... /etc/snapper/.snap-pac-pre + +..... /usr/bin/nano + +..... /usr/bin/rnano + +..... /usr/share/doc/nano + +..... /usr/share/doc/nano/faq.html + +..... /usr/share/doc/nano/fr + +..... /usr/share/doc/nano/fr/nano.1.html + +..... /usr/share/doc/nano/fr/nanorc.5.html + +..... /usr/share/doc/nano/fr/rnano.1.html + +The above output is truncated, but it continues. See the `snapper(8) +`_ to for what each symbol means. You can also +do ``snapper diff`` in the same way. + +Then, to undo the pacman transaction: + +.. code-block:: bash + + snapper -c root undochange 1033..1034 + +.. code-block:: none + + create:0 modify:3 delete:100 + +Now nano is no longer installed, along with all the files it changed: + +.. code-block:: bash + + pacman -Qi nano + +.. code-block:: none + + error: package 'nano' was not found diff --git a/_sources/faq.rst.txt b/_sources/faq.rst.txt new file mode 100644 index 0000000..c6f17e4 --- /dev/null +++ b/_sources/faq.rst.txt @@ -0,0 +1,42 @@ +FAQ +=== + +.. toctree:: + :maxdepth: 2 + +**Does snap-pac backup non-btrfs /boot partitions?** + +No, but you can add a hook that does it for you. It would be something like the following: + +.. code-block:: none + + [Trigger] + Operation = Upgrade + Operation = Install + Operation = Remove + Type = Package + Target = linux + + [Action] + Description = Backing up /boot... + When = PreTransaction + Exec = /usr/bin/rsync -avzq --delete /boot /.bootbackup + + +**How do I link old kernel modules automatically when the kernel is upgraded?** + +This behavior is no longer a part of this package. Use a pacman hook like the following: + +.. code-block:: none + + [Trigger] + Operation = Upgrade + Operation = Install + Operation = Remove + Type = Package + Target = linux + + [Action] + Description = Symlinking old kernel modules... + When = PostTransaction + Exec = /usr/bin/bash -c "find /usr/lib/modules -xtype l -delete; ln -sv /.snapshots/$(snapper -c root list | awk 'END{print $1}')/snapshot/usr/lib/modules/$(uname -r) /usr/lib/modules/" diff --git a/_sources/index.rst.txt b/_sources/index.rst.txt index e679d6e..018ddb5 100644 --- a/_sources/index.rst.txt +++ b/_sources/index.rst.txt @@ -8,13 +8,34 @@ Welcome to snap-pac's documentation! .. toctree:: :maxdepth: 2 - :caption: Contents: + installation + configuration + examples + troubleshooting + faq +This is a set of `pacman `_ hooks and script that causes +`snapper `_ to automatically take a pre and post snapshot before and +after pacman transactions, similar to how `YaST `_ does with +OpenSuse. This provides a simple way to undo changes to a system after a pacman +transaction. -Indices and tables -================== +Because these are pacman hooks, it doesn't matter how you call pacman—whether +directly, through an AUR helper, or using an alias—snapper will create the snapshots +when pacman installs, upgrades, or removes a package. The pacman command used is +logged in the snapper description for the snapshots. Additionally the snapshot numbers +are output to the screen and to the pacman log for each snapper configuration during the +pacman transaction, so that the user can easily find which changes he or she may want to +revert. -* :ref:`genindex` -* :ref:`modindex` -* :ref:`search` +To undo changes from a pacman transaction, use ``snapper undochange``. See the `snapper +documentation `_ for more details as well as +examples. + +If you have severe breakage—like snapper is gone for some reason and you can't get it +back—you'll have to resort to more extreme methods, such as taking a snapshot of the pre +snapshot and making it the default subvolume or mounting it as /. Most likely you'll +need to use a live USB to get into a chroot environment to do any of these things. +Snapper has a ``snapper rollback`` feature, but your setup has to be properly configured to +use it. The exact procedure depends on your specific setup. Be careful. diff --git a/_sources/installation.rst.txt b/_sources/installation.rst.txt new file mode 100644 index 0000000..345ab0a --- /dev/null +++ b/_sources/installation.rst.txt @@ -0,0 +1,30 @@ +Installation +============ + +Install the ``snap-pac`` package using pacman: + +.. code-block:: bash + + pacman -S snap-pac + +Alternatively download the `latest release and signature +`_. Then, verify the download: + +.. code-block:: bash + + gpg --verify snap-pac-.tar.gz.sig + +where ```` is the version number you downloaded. + +Finally, run: + +.. code-block:: bash + + make install + +I have signed the release tarball and commits with my PGP key. Starting with release +2.2, the tarballs are signed with my key with fingerprint +``F7B28C61944FE30DABEEB0B01070BCC98C18BD66``. + +For previous releases, the key's fingerprint was +``8535CEF3F3C38EE69555BF67E4B5E45AA3B8C5C3``. diff --git a/_sources/troubleshooting.rst.txt b/_sources/troubleshooting.rst.txt new file mode 100644 index 0000000..be961c6 --- /dev/null +++ b/_sources/troubleshooting.rst.txt @@ -0,0 +1,23 @@ +Troubleshooting +=============== + +.. toctree:: + :maxdepth: 2 + +**snap-pac is only taking snapshots of the root configuration.** + +That's the default behavior. See :doc:`configuration`. + +**No snapshots are being taken when I run pacman.** + +No snapper configurations are set up for snap-pac's pacman hooks. By default snap-pac +will take snapshots for the root configuration and any other configuration which has +SNAPSHOT set to yes in its configuration file. See :doc:`configuration`. + +**After restoring snapshot from snap-pac, the pacman database is locked.** + +The pre/post snaphots are taken while pacman is running, so this is expected. Follow +the instructions pacman gives you (*e.g.*, removing the lock file). You can add the +database lock file to a snapper filter so that snapper won't consider it when +performing snapper diff, snapper status, snapper undochange, etc. See the Filters +section in `snapper(8) `_ for more information. diff --git a/configuration.html b/configuration.html new file mode 100644 index 0000000..a8589fc --- /dev/null +++ b/configuration.html @@ -0,0 +1,137 @@ + + + + + + + + Configuration — snap-pac documentation + + + + + + + + + + + + + + + + + + + +
+
+
+ + +
+ +
+

Configuration

+
+
+

Configuration is done via Python ini configuration files. The defaults +should be suitable for most users, so you may not need to do any configuration at all. +By default only the root snapper configuration is snapshotted.

+

A commented example configuration files is located at /etc/snap-pac.ini.example.

+

To configure, copy the example configuration file:

+
cp /etc/snap-pac.ini{.example,}
+
+
+

Then edit with your favorite editor. The file is commented and should be +self-explanatory.

+

Each section corresponds with a snapper configuration. Add additional sections to add +other snapper configurations to be snapshotted. By default, only the root configuration +is snapshotted.

+
+

Environment Variables

+

To temporarily prevent snapshots from being performed for a single pacman +command, set the environment variable SNAP_PAC_SKIP. For example:

+
sudo SNAP_PAC_SKIP=y pacman -Syu
+
+
+
+
+ + +
+ +
+
+ +
+
+
+ ©2021, Wes Barnett, PhD. + + | + Powered by Sphinx 3.5.2 + & Alabaster 0.7.12 + + | + Page source +
+ + + + + + \ No newline at end of file diff --git a/examples.html b/examples.html new file mode 100644 index 0000000..c84e738 --- /dev/null +++ b/examples.html @@ -0,0 +1,184 @@ + + + + + + + + Example — snap-pac documentation + + + + + + + + + + + + + + + + + + + +
+
+
+ + +
+ +
+

Example

+
+
+

Here is an example of how the snapshots are created and how to rollback and pacman +transaction. Here the nano package is installed:

+
pacman -S nano
+
+
+
resolving dependencies...
+looking for conflicting packages...
+
+Packages (1) nano-2.5.3-1
+
+Total Installed Size:  2.14 MiB
+
+:: Proceed with installation? [Y/n] Y
+(1/1) checking keys in keyring                               [######################################] 100%
+(1/1) checking package integrity                             [######################################] 100%
+(1/1) loading package files                                  [######################################] 100%
+(1/1) checking for file conflicts                            [######################################] 100%
+(1/1) checking available disk space                          [######################################] 100%
+:: Running pre-transaction hooks...
+(1/1) Performing snapper pre snapshots for the following configurations...
+=> root: 1033
+:: Processing package changes...
+(1/1) installing nano                                        [######################################] 100%
+:: Running post-transaction hooks...
+(1/1) Performing snapper post snapshots for the following configurations...
+=> root: 1034
+
+
+

The snapper snapshot number is given for each snapper configuration that is used. This +is also logged in pacman’s log.

+

Here are the snapshots created before and after the pacman transaction:

+
snapper -c root list -t pre-post | tail -n 1
+
+
+
1033  | 1034   | Fri 22 Apr 2016 01:54:13 PM CDT | Fri 22 Apr 2016 01:54:14 PM CDT | pacman -S nano      |
+
+
+

Here is what changed during the transaction:

+
snapper -c root status 1033..1034
+
+
+
+..... /etc/nanorc
+c..... /etc/snapper/.snap-pac-pre
++..... /usr/bin/nano
++..... /usr/bin/rnano
++..... /usr/share/doc/nano
++..... /usr/share/doc/nano/faq.html
++..... /usr/share/doc/nano/fr
++..... /usr/share/doc/nano/fr/nano.1.html
++..... /usr/share/doc/nano/fr/nanorc.5.html
++..... /usr/share/doc/nano/fr/rnano.1.html
+
+
+

The above output is truncated, but it continues. See the snapper(8) to for what each symbol means. You can also +do snapper diff in the same way.

+

Then, to undo the pacman transaction:

+
snapper -c root undochange 1033..1034
+
+
+
create:0 modify:3 delete:100
+
+
+

Now nano is no longer installed, along with all the files it changed:

+
pacman -Qi nano
+
+
+
error: package 'nano' was not found
+
+
+
+ + +
+ +
+
+ +
+
+
+ ©2021, Wes Barnett, PhD. + + | + Powered by Sphinx 3.5.2 + & Alabaster 0.7.12 + + | + Page source +
+ + + + + + \ No newline at end of file diff --git a/faq.html b/faq.html new file mode 100644 index 0000000..e09ef9a --- /dev/null +++ b/faq.html @@ -0,0 +1,143 @@ + + + + + + + + FAQ — snap-pac documentation + + + + + + + + + + + + + + + + + + +
+
+
+ + +
+ +
+

FAQ

+
+
+

Does snap-pac backup non-btrfs /boot partitions?

+

No, but you can add a hook that does it for you. It would be something like the following:

+
[Trigger]
+Operation = Upgrade
+Operation = Install
+Operation = Remove
+Type = Package
+Target = linux
+
+[Action]
+Description = Backing up /boot...
+When = PreTransaction
+Exec = /usr/bin/rsync -avzq --delete /boot /.bootbackup
+
+
+

How do I link old kernel modules automatically when the kernel is upgraded?

+

This behavior is no longer a part of this package. Use a pacman hook like the following:

+
[Trigger]
+Operation = Upgrade
+Operation = Install
+Operation = Remove
+Type = Package
+Target = linux
+
+[Action]
+Description = Symlinking old kernel modules...
+When = PostTransaction
+Exec = /usr/bin/bash -c "find /usr/lib/modules -xtype l -delete; ln -sv /.snapshots/$(snapper -c root list | awk 'END{print $1}')/snapshot/usr/lib/modules/$(uname -r) /usr/lib/modules/"
+
+
+
+ + +
+ +
+
+ +
+
+
+ ©2021, Wes Barnett, PhD. + + | + Powered by Sphinx 3.5.2 + & Alabaster 0.7.12 + + | + Page source +
+ + + + + + \ No newline at end of file diff --git a/genindex.html b/genindex.html index 63ba4de..0cc7e11 100644 --- a/genindex.html +++ b/genindex.html @@ -54,6 +54,13 @@

Navigation

+

Related Topics

diff --git a/index.html b/index.html index cb76e54..23326fa 100644 --- a/index.html +++ b/index.html @@ -14,6 +14,7 @@ + @@ -33,15 +34,44 @@

Welcome to snap-pac’s documentation!

-
-
- +

This is a set of pacman hooks and script that causes +snapper to automatically take a pre and post snapshot before and +after pacman transactions, similar to how YaST does with +OpenSuse. This provides a simple way to undo changes to a system after a pacman +transaction.

+

Because these are pacman hooks, it doesn’t matter how you call pacman—whether +directly, through an AUR helper, or using an alias—snapper will create the snapshots +when pacman installs, upgrades, or removes a package. The pacman command used is +logged in the snapper description for the snapshots. Additionally the snapshot numbers +are output to the screen and to the pacman log for each snapper configuration during the +pacman transaction, so that the user can easily find which changes he or she may want to +revert.

+

To undo changes from a pacman transaction, use snapper undochange. See the snapper +documentation for more details as well as +examples.

+

If you have severe breakage—like snapper is gone for some reason and you can’t get it +back—you’ll have to resort to more extreme methods, such as taking a snapshot of the pre +snapshot and making it the default subvolume or mounting it as /. Most likely you’ll +need to use a live USB to get into a chroot environment to do any of these things. +Snapper has a snapper rollback feature, but your setup has to be properly configured to +use it. The exact procedure depends on your specific setup. Be careful.

@@ -61,11 +91,19 @@

Navigation

+

Related Topics

diff --git a/installation.html b/installation.html new file mode 100644 index 0000000..c7a75ce --- /dev/null +++ b/installation.html @@ -0,0 +1,129 @@ + + + + + + + + Installation — snap-pac documentation + + + + + + + + + + + + + + + + + + + +
+
+
+ + +
+ +
+

Installation

+

Install the snap-pac package using pacman:

+
pacman -S snap-pac
+
+
+

Alternatively download the latest release and signature. Then, verify the download:

+
gpg --verify snap-pac-<version>.tar.gz.sig
+
+
+

where <version> is the version number you downloaded.

+

Finally, run:

+
make install
+
+
+

I have signed the release tarball and commits with my PGP key. Starting with release +2.2, the tarballs are signed with my key with fingerprint +F7B28C61944FE30DABEEB0B01070BCC98C18BD66.

+

For previous releases, the key’s fingerprint was +8535CEF3F3C38EE69555BF67E4B5E45AA3B8C5C3.

+
+ + +
+ +
+
+ +
+
+
+ ©2021, Wes Barnett, PhD. + + | + Powered by Sphinx 3.5.2 + & Alabaster 0.7.12 + + | + Page source +
+ + + + + + \ No newline at end of file diff --git a/objects.inv b/objects.inv index 5cbf0f3..5702a1a 100644 Binary files a/objects.inv and b/objects.inv differ diff --git a/search.html b/search.html index a9851c1..d47d33d 100644 --- a/search.html +++ b/search.html @@ -74,6 +74,13 @@

Navigation

+

Related Topics

diff --git a/searchindex.js b/searchindex.js index f335240..df7d00f 100644 --- a/searchindex.js +++ b/searchindex.js @@ -1 +1 @@ -Search.setIndex({docnames:["index"],envversion:{"sphinx.domains.c":2,"sphinx.domains.changeset":1,"sphinx.domains.citation":1,"sphinx.domains.cpp":3,"sphinx.domains.index":1,"sphinx.domains.javascript":2,"sphinx.domains.math":2,"sphinx.domains.python":2,"sphinx.domains.rst":2,"sphinx.domains.std":2,sphinx:56},filenames:["index.rst"],objects:{},objnames:{},objtypes:{},terms:{index:0,modul:0,page:0,search:0},titles:["Welcome to snap-pac\u2019s documentation!"],titleterms:{document:0,indic:0,pac:0,snap:0,tabl:0,welcom:0}}) \ No newline at end of file +Search.setIndex({docnames:["configuration","examples","faq","index","installation","troubleshooting"],envversion:{"sphinx.domains.c":2,"sphinx.domains.changeset":1,"sphinx.domains.citation":1,"sphinx.domains.cpp":3,"sphinx.domains.index":1,"sphinx.domains.javascript":2,"sphinx.domains.math":2,"sphinx.domains.python":2,"sphinx.domains.rst":2,"sphinx.domains.std":2,sphinx:56},filenames:["configuration.rst","examples.rst","faq.rst","index.rst","installation.rst","troubleshooting.rst"],objects:{},objnames:{},objtypes:{},terms:{"100":1,"1033":1,"1034":1,"2016":1,"8535cef3f3c38ee69555bf67e4b5e45aa3b8c5c3":4,"default":[0,3,5],"final":4,"while":5,For:[0,4],That:5,The:[0,1,3,5],Then:[0,1,4],Use:2,abov:1,action:2,add:[0,2,5],addit:0,addition:3,after:[1,3,5],alia:3,all:[0,1],along:1,also:1,altern:4,ani:[0,3,5],apr:1,aur:3,automat:[2,3],avail:1,avzq:2,awk:2,back:[2,3],backup:2,bash:2,becaus:3,befor:[1,3],behavior:[2,5],being:[0,5],bin:[1,2],boot:2,bootbackup:2,breakag:3,btrf:2,call:3,can:[1,2,3,5],care:3,caus:3,cdt:1,chang:[1,3],check:1,chroot:3,command:[0,3],comment:0,commit:4,configur:[1,3,5],conflict:1,consid:5,continu:1,copi:0,correspond:0,creat:[1,3],databas:5,delet:[1,2],depend:[1,3],descript:[2,3],detail:3,diff:[1,5],directli:3,disk:1,doc:1,doe:[2,3],doesn:3,done:0,download:4,dure:[1,3],each:[0,1,3],easili:3,edit:0,editor:0,end:2,environ:3,error:1,etc:[0,1,5],exact:3,exampl:[0,3],exec:2,expect:5,explanatori:0,extrem:3,f7b28c61944fe30dabeeb0b01070bcc98c18bd66:4,faq:[1,3],favorit:0,featur:3,file:[0,1,5],filter:5,find:[2,3],fingerprint:4,follow:[1,2,5],found:1,fri:1,from:[0,3,5],get:3,give:5,given:1,gone:3,gpg:4,has:[3,5],have:[3,4],helper:3,here:1,hook:[1,2,3,5],how:[1,2,3],html:1,inform:5,ini:0,instal:[1,2,3],instruct:5,integr:1,its:5,kei:[1,4],kernel:2,keyr:1,latest:4,lib:2,like:[2,3],link:2,linux:2,list:[1,2],live:3,load:1,locat:0,lock:5,log:[1,3],longer:[1,2],look:1,mai:[0,3],make:[3,4],matter:3,mean:1,method:3,mib:1,modifi:1,modul:2,more:[3,5],most:[0,3],mount:3,nano:1,nanorc:1,need:[0,3],non:2,now:1,number:[1,3,4],old:2,onli:[0,5],opensus:3,oper:2,other:[0,5],output:[1,3],pac:[0,1,2,4,5],packag:[1,2,3,4],pacman:[0,1,2,3,4,5],part:2,partit:2,perform:[0,1,5],pgp:4,post:[1,3,5],posttransact:2,pre:[1,3,5],pretransact:2,prevent:0,previou:4,print:2,proce:1,procedur:3,process:1,properli:3,provid:3,python:0,reason:3,releas:4,remov:[2,3,5],resolv:1,resort:3,restor:5,revert:3,rnano:1,rollback:[1,3],root:[0,1,2,5],rsync:2,run:[1,4,5],same:1,screen:3,script:3,section:[0,5],see:[1,3,5],self:0,set:[0,3,5],setup:3,sever:3,share:1,she:3,should:0,sig:4,sign:4,signatur:4,similar:3,simpl:3,singl:0,size:1,snap:[0,1,2,4,5],snap_pac_skip:0,snaphot:5,snapper:[0,1,2,3,5],snapshot:[0,1,2,3,5],some:3,someth:2,space:1,specif:3,start:4,statu:[1,5],subvolum:3,sudo:0,suitabl:0,symbol:1,symlink:2,system:3,syu:0,tail:1,take:[3,5],taken:5,tar:4,tarbal:4,target:2,temporarili:0,thi:[1,2,3,5],thing:3,through:3,total:1,transact:[1,3],trigger:2,troubleshoot:3,truncat:1,type:2,unam:2,undo:[1,3],undochang:[1,3,5],upgrad:[2,3],usb:3,use:3,used:[1,3],user:[0,3],using:[3,4],usr:[1,2],variabl:3,verifi:4,version:4,via:0,wai:[1,3],want:3,well:3,what:1,when:[2,3,5],where:4,whether:3,which:[3,5],won:5,would:2,xtype:2,yast:3,yes:5,you:[0,1,2,3,4,5],your:[0,3]},titles:["Configuration","Example","FAQ","Welcome to snap-pac\u2019s documentation!","Installation","Troubleshooting"],titleterms:{configur:0,document:3,environ:0,exampl:1,faq:2,instal:4,pac:3,snap:3,troubleshoot:5,variabl:0,welcom:3}}) \ No newline at end of file diff --git a/troubleshooting.html b/troubleshooting.html new file mode 100644 index 0000000..1c1bae5 --- /dev/null +++ b/troubleshooting.html @@ -0,0 +1,127 @@ + + + + + + + + Troubleshooting — snap-pac documentation + + + + + + + + + + + + + + + + + + + +
+
+
+ + +
+ +
+

Troubleshooting

+
+
+

snap-pac is only taking snapshots of the root configuration.

+

That’s the default behavior. See Configuration.

+

No snapshots are being taken when I run pacman.

+

No snapper configurations are set up for snap-pac’s pacman hooks. By default snap-pac +will take snapshots for the root configuration and any other configuration which has +SNAPSHOT set to yes in its configuration file. See Configuration.

+

After restoring snapshot from snap-pac, the pacman database is locked.

+

The pre/post snaphots are taken while pacman is running, so this is expected. Follow +the instructions pacman gives you (e.g., removing the lock file). You can add the +database lock file to a snapper filter so that snapper won’t consider it when +performing snapper diff, snapper status, snapper undochange, etc. See the Filters +section in snapper(8) for more information.

+
+ + +
+ +
+
+ +
+
+
+ ©2021, Wes Barnett, PhD. + + | + Powered by Sphinx 3.5.2 + & Alabaster 0.7.12 + + | + Page source +
+ + + + + + \ No newline at end of file