You are not logged in.
Pages: 1
Topic closed
I love pacman but I would like to know a bit more about its inner workings with logs. Specifically which and how many logs does it create when you install something (or upgrade). Reason for this is obviously when you install something with a bucketload of dependancies messages about individual packages fly on the screen without managing to read them (or I might be out of the room...). So how do you make sure you read everything needed?
My solution has always been a directory under /var/log (eg. /var/log/pacman) and the say for example:
cd /var/log/pacman
pacman -Syuw
pacman -Su | tee Syu
The second line is to actually download the needed files, otherwise my Syu log created in the third line would be filled with scrolling ##### while downloading/installing the files!
Is this the best I can do? Or does pacman have a cunning way to deal with this?
Thanks
There is no spoon in Arch...
Offline
how about looking into /var/log/pacman.log ?
Offline
I have seen pacman.log but I wasn't sure if it also saved the messages reffering to packages. I thought it only saved the time a package was installed or updated. So does pacman.log keep track of EVERYTHING?
(ps. by messages I mean like the ones after the installation of openoffice saying "run oofice" or kde reffering to java bindings etc)
Also what doc or man page did you read that told you about pacman.log?
Thanks
There is no spoon in Arch...
Offline
why not just "pacman -Syu --noconfirm > /my/pacman/log.file"
Offline
I thought that when you use > it omits to show stuff on screen where it really matters? Thats why I use tee, as it does both screen and file.
Unless that mysterious --noconfirm does something???
There is no spoon in Arch...
Offline
--noconfirm simply omits user-input ... so yes/no questions get answered with yes automatically
and i wouldnt use > but &> to redirect std-out and error-out but ...
pacman -Syu | tee [some file]
has the advantage of that you can control the update AND have a log of what had happend..
so you just spend some secs at the screen making your desicions .. and than you can leave your box alone
Offline
It looks like like the power cut out here:
[2018-08-23 14:46] [ALPM] running 'systemd-udev-reload.hook'... [2018-08-23 14:46] [ALPM] running 'systemd-update.hook'... [2018-08-23 14:46] [ALPM] running 'update-ca-trust.hook'.
^a^a...
The only suspect part of pacman - Qkk are some backup file mismatch :
backup file: xorg-xinit: /etc/X11/xinit/xinitrc (Modification time mismatch) backup file: xorg-xinit: /etc/X11/xinit/xinitrc (Size mismatch)
Last edited by cooperrc (2018-08-26 13:47:44)
Offline
The only suspect part of pacman - Qkk are some backup file mismatch :
backup file: xorg-xinit: /etc/X11/xinit/xinitrc (Modification time mismatch) backup file: xorg-xinit: /etc/X11/xinit/xinitrc (Size mismatch)
Offline
Please don't necrobump 13 year old threads, https://wiki.archlinux.org/index.php/Co … bumping.22
If you make your own post about this include more details and post them in [ code ] tags.
Closing.
Online
Pages: 1
Topic closed