Difference between revisions of "Talk:Pacman"

From ArchWiki
Jump to navigation Jump to search
m (FAQ: reinstalling all packages: rm closed discussion)
(pacman.log: new section)
Line 2: Line 2:
  
 
IMO it should be added to this page. You can get text from [https://bbs.archlinux.org/viewtopic.php?pid=320958]. --[[User:Beroal|Beroal]] 13:13, 8 November 2010 (EST)
 
IMO it should be added to this page. You can get text from [https://bbs.archlinux.org/viewtopic.php?pid=320958]. --[[User:Beroal|Beroal]] 13:13, 8 November 2010 (EST)
 +
 +
== pacman.log ==
 +
 +
There are (as of this writing) two places on this page which say that <code>pacman</code>'s output is logged to <code>/var/log/pacman.log</code>. Obviously in the strictest sense this is false, as can easily be seen by anybody who's glanced at this file and at <code>pacman</code>'s on-screen output. Ordinarily, this wouldn't be a problem, as it's clear what is meant. But there's also some information which is ''not'' logged, and this fact is unclear.
 +
 +
I'd edit the page to make it clear what is and isn't logged, but I'm not sure myself. It seems like the following things are logged:
 +
 +
* Package installation complete
 +
* Most but not all of the per-package notices <code>pacman</code> prints.
 +
 +
It seems like the following things are not logged:
 +
 +
* Progress bars (of course)
 +
* Package download
 +
* Package integrity and signature checks
 +
* File conflicts
 +
* Disk space checks
 +
* Optional dependencies
 +
 +
Unless there's a problem (in which case they may be logged; I'm not sure), you really don't care about any of these except the optional dependencies, and those can be obtained with <code>pacman -Qi</code> or <code>expac</code>. However, I'm not sure if this list is exhaustive, and wouldn't want to find out the hard way that I'd missed important <code>pacman</code> output by assuming it'd be in the log.
 +
 +
Can somebody link to (or put here) a more comprehensive list of what is and isn't logged? I haven't been able to find one, and I think that it'd be much better to be clear than to simplify by saying "all the output is logged". [[User:DHouck|DHouck]] ([[User talk:DHouck|talk]]) 08:14, 22 February 2014 (UTC)

Revision as of 08:14, 22 February 2014

testdb

IMO it should be added to this page. You can get text from [1]. --Beroal 13:13, 8 November 2010 (EST)

pacman.log

There are (as of this writing) two places on this page which say that pacman's output is logged to /var/log/pacman.log. Obviously in the strictest sense this is false, as can easily be seen by anybody who's glanced at this file and at pacman's on-screen output. Ordinarily, this wouldn't be a problem, as it's clear what is meant. But there's also some information which is not logged, and this fact is unclear.

I'd edit the page to make it clear what is and isn't logged, but I'm not sure myself. It seems like the following things are logged:

  • Package installation complete
  • Most but not all of the per-package notices pacman prints.

It seems like the following things are not logged:

  • Progress bars (of course)
  • Package download
  • Package integrity and signature checks
  • File conflicts
  • Disk space checks
  • Optional dependencies

Unless there's a problem (in which case they may be logged; I'm not sure), you really don't care about any of these except the optional dependencies, and those can be obtained with pacman -Qi or expac. However, I'm not sure if this list is exhaustive, and wouldn't want to find out the hard way that I'd missed important pacman output by assuming it'd be in the log.

Can somebody link to (or put here) a more comprehensive list of what is and isn't logged? I haven't been able to find one, and I think that it'd be much better to be clear than to simplify by saying "all the output is logged". DHouck (talk) 08:14, 22 February 2014 (UTC)