Pacman log cleaner

I've written a script to clean up the pacman log file. (It was 32 MB on my system, mostly because Sage was built in the post_install function and thus spammed the log file.)
I've posted it on my site along with an explanation of what it does. (I've added syntax highlighting to my toolchain and wanted an excuse to use it. )
Last edited by Xyne (2010-05-06 12:33:09)

Hehe I wrote something similar to this one for myself a few days ago. It cleans the pacman.log of spam as "Synchronizing package databases..." and "Starting full system upgrade..." lines.
If anyone wants it, here it is...(author of the thread, if you find my post appropriate, please contact me or write here, and I will remove this code. )
sudo pacman -Syu &&
sudo sed -i '/starting full system upgrade/ d' /var/log/pacman.log &&
sudo sed -i '/synchronizing package lists/ d' /var/log/pacman.log &&
echo "==> log file cleared of spam messages" &&
echo "==> exit" &&
date +'%A, %d.%m.%y., %k:%M' > /home/<YOUR_USER_HERE>/.scripts/synched # or whatever you like
The last line is to keep track of when pacman was last synched.
Cheers.

Similar Messages

  • [Solved] Pacman.log no longer logging maybe systemd

    Hi, I upgraded a couple of days ago on the 11th to systemd system, I am using 86_64 awesome DE, I ran Syu yesterday and this morning I found mplayer was acting poorly so I went to check pacman.log to see what was updated. Pacman.log hadn't logged since the 11th when I upgraded, although I would like to figure out mplayer, I am more interested in the log files. I also found that my boot log file is not recording boot information from the same time although the errors.log has information in it.
    thanks in advance for any help you may give.
    --jerry
    Last edited by jk121960 (2012-11-14 21:15:45)

    bernarcher wrote:
    To be more precise, did you follow this: Journald in conjunction with syslog
    pacman.log is working here.
    Yes and here is the status
    syslog-ng.service - System Logger Daemon
    Loaded: loaded (/usr/lib/systemd/system/syslog-ng.service; enabled)
    Active: active (running) since Wed, 2012-11-14 00:58:57 CST; 14h ago
    Docs: man:syslog-ng(8)
    Main PID: 591 (syslog-ng)
    CGroup: name=systemd:/system/syslog-ng.service
    └ 591 /usr/sbin/syslog-ng -F
    thanks for your help
    --jerry

  • Log cleaning takes a lot

    Hi,
    I've been reading the forum but could not find a hint for solving my problem. I apologize if I missed something and the answer is already there.
    My scenario for using BDB (je-4.0.103):
    - a read-only environment with about 4000 databases. The environment uses about 100GB disk space. Log file size is 10MB. Cache size is 100MB.
    - databases are opened only when needed and are closed after a few minutes of inactivity
    - when in read-only mode cleaner, checkpointer and IN compressor threads are disabled
    - once a day, the env is closed and re-opened in read/write mode for performing bulk data load, in deferred write mode, without transactions. About 0.5 - 1GB of data is imported daily (1 million key-value pairs).
    - during load, IN compressor is enabled but cleaner and checkpointer are not
    - log cleaning and checkpointing is invoked manually at the end of data import using the algorithm suggested in the docs
    After several months of working properly without any signs of degradation the whole thing broke down suddenly. The log cleaning takes now hours instead of minutes and it does not seem to do its job: the environment is now 250GB and keeps growing. Restart also takes several hours.
    Any help would be appreciated. If more details about my setup is needed, I can provide it.
    Thank you!
    Edited by: user9045772 on Sep 17, 2010 3:30 AM
    Mentioned the size of the cache.

    Hi Eric,
    Thank you very much for your help.
    I just tried increasing the cache from 100MB to 1GB and it made miracles. Log cleaning was finally completed after 2 hours. The db start time is now back to normal (less than 2 minutes).
    I'm still concerned with the fact that log cleaning takes a lot, but at least it finishes after several hours. Will have a look at db space utilization after completing a new run and will tell you the results.
    Until then, here are the env config and stats (after increasing the cache), maybe you spot something odd:
    ------------------ Env Config ------------------------------------
    allowCreate=true
    cacheSize=1048576000
    txnNoSync=false
    txnWriteNoSync=false
    {je.log.fileMax=10485760,
    je.env.runCheckpointer=false,
    je.env.runCleaner=false,
    je.log.totalBufferBytes=10485760,
    je.cleaner.minFileUtilization=50,
    je.env.isLocking=false,
    je.cleaner.minUtilization=80,
    je.sharedCache=true,
    je.env.runINCompressor=true,
    je.env.isTransactional=false,
    je.env.isReadOnly=false,
    je.log.faultReadSize=120960,
    je.log.bufferSize=5242880,
    je.maxMemory=10485760000,
    je.log.numBuffers=2,
    je.log.iteratorReadSize=120960}
    ------------------ Env Stats ------------------------------------
    I/O: Log file opens, fsyncs, reads, writes, cache misses.
         bufferBytes=10,485,760
         endOfLog=0x0/0x0
         nBytesReadFromWriteQueue=0
         nBytesWrittenFromWriteQueue=0
         nCacheMiss=24,646
         nFSyncRequests=1
         nFSyncTimeouts=0
         nFSyncs=1
         nFileOpens=5,319
         nLogBuffers=2
         nLogFSyncs=3
         nNotResident=24,646
         nOpenFiles=100
         nRandomReadBytes=1,664,658,816
         nRandomReads=13,751
         nRandomWriteBytes=2,961,648
         nRandomWrites=1
         nReadsFromWriteQueue=0
         nRepeatFaultReads=2
         nSequentialReadBytes=53,787,475,644
         nSequentialReads=274,985
         nSequentialWriteBytes=0
         nSequentialWrites=0
         nTempBufferWrites=0
         nWriteQueueOverflow=0
         nWriteQueueOverflowFailures=0
         nWritesFromWriteQueue=0
    Cache: Current size, allocations, and eviction activity.
         adminBytes=4,807,377
         cacheTotalBytes=21,728,916
         dataBytes=6,435,779
         lockBytes=0
         nBINsEvictedCACHEMODE=0
         nBINsEvictedCRITICAL=0
         nBINsEvictedEVICTORTHREAD=0
         nBINsEvictedMANUAL=0
         nBINsFetch=53,566
         nBINsFetchMiss=543
         nBINsStripped=0
         nEvictPasses=0
         nLNsFetch=90,991
         nLNsFetchMiss=24,096
         nNodesEvicted=0
         nNodesScanned=0
         nNodesSelected=0
         nRootNodesEvicted=0
         nSharedCacheEnvironments=1
         nUpperINsEvictedCACHEMODE=0
         nUpperINsEvictedCRITICAL=0
         nUpperINsEvictedEVICTORTHREAD=0
         nUpperINsEvictedMANUAL=0
         nUpperINsFetch=36,940
         nUpperINsFetchMiss=9
         requiredEvictBytes=0
         sharedCacheTotalBytes=21,728,916
    Cleaning: Frequency and extent of log file cleaning activity.
         cleanerBackLog=7,441
         fileDeletionBacklog=0
         nCleanerDeletions=0
         nCleanerEntriesRead=1,400,054
         nCleanerRuns=4,845
         nClusterLNsProcessed=0
         nINsCleaned=0
         nINsDead=0
         nINsMigrated=0
         nINsObsolete=86
         nLNQueueHits=0
         nLNsCleaned=0
         nLNsDead=0
         nLNsLocked=0
         nLNsMarked=0
         nLNsMigrated=0
         nLNsObsolete=1,390,901
         nMarkLNsProcessed=0
         nPendingLNsLocked=0
         nPendingLNsProcessed=0
         nRepeatIteratorReads=0
         nToBeCleanedLNsProcessed=0
         totalLogSize=0
    Node Compression: Removal and compression of internal btree nodes.
         cursorsBins=0
         dbClosedBins=0
         inCompQueueSize=0
         nonEmptyBins=0
         processedBins=15
         splitBins=0
    Checkpoints: Frequency and extent of checkpointing activity.
         lastCheckpointEnd=0xae0c/0x74f5c6
         lastCheckpointId=1,590
         lastCheckpointStart=0xae0c/0x4c6dea
         nCheckpoints=1
         nDeltaINFlush=15
         nFullBINFlush=47
         nFullINFlush=51
    Environment: General environment wide statistics.
         btreeRelatchesRequired=148
    Locks: Locks held by data operations, latching contention on lock table.
         nLatchAcquireNoWaitUnsuccessful=0
         nLatchAcquiresNoWaitSuccessful=0
         nLatchAcquiresNoWaiters=0
         nLatchAcquiresSelfOwned=0
         nLatchAcquiresWithContention=0
         nLatchReleases=0
         nRequests=0
         nWaits=0
    Edited by: user9045772 on Sep 17, 2010 4:12 AM
    added env config and stats

  • [SOLVED]pacman.log filled with "[PACMAN] starting full system upgrade"

    Today i just ran pacman -Suy, but now the log is filled with:
    Gozer ~ # tail /var/log/pacman.log -n 100
    [2013-04-08 12:26] [PACMAN] upgraded youtube-dl (2013.02.25-1 -> 2013.04.03-1)
    [2013-04-08 12:27] [PACMAN] starting full system upgrade
    [2013-04-08 12:27] [PACMAN] starting full system upgrade
    [2013-04-08 12:27] [PACMAN] starting full system upgrade
    [2013-04-08 12:27] [PACMAN] starting full system upgrade
    [2013-04-08 12:28] [PACMAN] starting full system upgrade
    [2013-04-08 12:28] [PACMAN] starting full system upgrade
    [2013-04-08 13:06] [PACMAN] starting full system upgrade
    Gozer ~ # grep '2013-04-08' /var/log/pacman.log |grep "starting full system upgrade" | wc -l
    637
    Is this a bug?
    Last edited by kokoko3k (2013-04-08 12:57:01)

    Edit: are you using some system update monitoring script?
    Ops... big "OPS".
    You are right, sorry!

  • Where does the recommendations of pacman log?

    When I upgrade the system, there is some recommendation to edit files in order the system work normally.
    Where these recommendation save?
    the log at /var/log/pacman.log only log the packages which installed, but It isn't include those recommendation.
    Last edited by nadavvin (2007-03-03 19:32:48)

    nadavvin wrote:
    Snowman wrote:It's not recommended to run pacman in a daemon script like that. Some updates are non-trivial and requires extra steps so you risk broking your system and you wouldn't know the reason.  If you want some automation, add the -w switch to the pacman line so pacman will just download the packages and won't install/upgrade anything. That way when you'll be at your computer, everything will be ready for the upgrade.
    Why not?
    It is work good from then.
    What could go wrong that can not prevent in the regular way?
    I guess that there will be no message like "this package could break the system", since if It like that, It will not added to the current repo.
    Because as I mentionned sometime extra steps are required. For example, when we switched from devfs to udev or from initrd to initcpio, you needed to change your fstab and lilo.conf/menu.lst.  If you would had done your updates in the background, you would have missed the warning messages as I don't think you would check the message log every day. So you would have ended up with an unbootable system. Other examples: if you use lilo, you need to run it each time the kernel/lilo is updated. Another one:  when we went to the modularized xorg 7, paths in xorg.conf needed to be changed.
    If it's the confirmation that you don't like, use the --noconfirm switch. Start pacman in a terminal then check it back later to see what packages it has installed and if there were important post-install messages.
    If you really want to run pacman as a daemon, I can't force you to not do it.  I'm just warning you that potential problems can happen with this method.

  • [SOLVED] pacman log optional dependencies

    Hi,
    Coming from ubuntu, just been trying Arch to get to know better the linux system and try a more KISS approach. I really like it, however I had a few troubles on the way which I am resolving slowly.. however concrenng pacman, maybe I am blind but I can't find a way to get all the messages displayed during some package installation in the pacman.log ; in particular all the optional dependencies are not listed there..
    Is there a way to get the full pacman log as shown during the installation in a log file ?
    Last edited by Alain2 (2009-11-08 02:05:52)

    Hi All,
    I saw this and had to take up the challenge.
    How's this? It's pure sed at work. It shows both required and optional dependencies.
    pacman -Qi | sed -n '/^Name/,/^Required By/{ /^Version/,/^Provides/d; /^Required By/d; /^Name/{x;p;x}; p }'
    This is a command line version of course so just make an alias for it in .bashrc. If you want to log it then create a cron script to update it. By the way this should alleviate the multi-line issue you were having as I did some reverse thinking on this. I just eliminated what we didn't need as opposed to just trying to find what we did need. Sometimes that works better. 
    Here's an example output: (The actual output is nice and tidy. Pasting into the forum here mucked the alignment up. ) lol!
    Name           : pcmciautils
    Depends On     : glibc  sysfsutils  module-init-tools>=3.2pre9 
    Optional Deps  : None
    Name           : pcre
    Depends On     : gcc-libs 
    Optional Deps  : None
    Name           : perl
                     perl-archive-tar=1.52  perl-autodie=2.06_01 
                     perl-attribute-handlers=0.85  perl-autoloader=5.68 
                     perl-b-debug=1.11  perl-b-lint=1.11  perl-base=2.14 
                     perl-bignum=0.23  perl-cgi=3.43  perl-class-isa=0.33 
                     perl-compress-raw-bzib2=2.020  perl-compress-raw-zlib=2.020 
                     perl-constant=1.17  perl-cpan=1.9402  perl-cpanplus=0.88 
                     perl-db_file=1.820  perl-dprof=20080331.00 
                     perl-data-dumper=2.124  perl-devel-ppport=3.19 
                     perl-devel-peek=1.04  perl-digest=1.16  perl-digest-md5=2.39 
                     perl-digest-sha=5.47  perl-encode=2.35 
                     perl-encoding-warnings=0.11  perl-exporter=5.63 
                     perl-extutils-cbuilder=0.2602  perl-extutils-command=1.16 
                     perl-extutils-constant=0.22  perl-extutils-embed=1.28 
                     perl-extutils-install=1.54  perl-extutils-makemaker=6.55_02 
                     perl-extutils-manifest=1.56  perl-extutils-parsexs=2.2002 
                     perl-file-fetch=0.20  perl-file-path=2.07_03 
                     perl-file-temp=0.22  perl-filter=1.37 
                     perl-filter-simple=0.84  perl-getopt-long=2.38  perl-if=0.05 
                     perl-io=1.25  perl-io-compress=2.020  perl-io-zlib=1.09 
                     perl-ipc-cmd=0.46  perl-ipc-sysv=2.01  perl-libnet=1.22 
                     perl-locale-codes=2.07  perl-locale-maketext=0.13 
                     perl-locale-maketext-simple=0.18  perl-log-message=0.02 
                     perl-log-message-simple=0.04  perl-mime-base64=3.08 
                     perl-math-bigint=1.89  perl-math-bigint-fastcalc=0.19 
                     perl-math-bigrat=0.22  perl-math-complex=1.56 
                     perl-memoize=1.01_03  perl-module-build=0.340201 
                     perl-module-corelist=2.18  perl-module-load=0.16 
                     perl-module-load-conditional=0.30  perl-module-loaded=0.02 
                     perl-module-pluggable=3.9  perl-next=0.64  perl-net-ping=2.36 
                     perl-object-accessor=0.34  perl-package-constants=0.02 
                     perl-params-check=0.26  perl-parent=0.221 
                     perl-parse-cpan-meta=1.39  perl-pathtools=3.30 
                     perl-pod-escapes=1.04  perl-pod-latex=0.58 
                     perl-pod-parser=1.37  perl-pod-perldoc=3.14_04 
                     perl-pod-simple=3.07  perl-podlators=2.2.2  perl-safe=2.18 
                     perl-scalar-list-utils=1.21  perl-selfloader=1.17 
                     perl-shell=0.72_01  perl-storable=2.20  perl-switch=2.14 
                     perl-sys-syslog=0.27  perl-term-cap=1.12  perl-term-ui=0.20 
                     perl-test=1.25_02  perl-test-harness=3.17 
                     perl-test-simple=0.92  perl-text-balanced=2.0.0 
                     perl-text-parsewords=3.27  perl-text-soundex=3.03 
                     perl-text-tabs+wraps=2009.0305  perl-thread-queue=2.11 
                     perl-thread-semaphore=2.09  perl-threads=1.72 
                     perl-threads-shared=1.29  perl-tie-file=0.97_02 
                     perl-tie-refhash=1.38  perl-time-hires=1.9719 
                     perl-time-local=1.1901  perl-time-piece=1.15 
                     perl-unicode-collate=0.52  perl-unicode-normalize=1.03 
                     perl-version=0.77  perl-win32=0.39  perl-win32api-file=0.1101 
                     perl-xsloader=0.10  perlio-via-quotedprint=0.06 
    Depends On     : gdbm  db>=4.8  coreutils  glibc  sh 
    Optional Deps  : None
    Name           : perl-crypt-ssleay
    Depends On     : perl>=5.10.0 
    Optional Deps  : None
    Have a nice day!!
    Hope this helps
    P.S. Here's another little tool I wrote you might find useful. Add to .bashrc
       wtd: (What They Do)
    alias wtd="pacman -Qi | sed -n '/Version/,/Install\ Script/!p' | grep -F -A2 "
    Just type:
    wtd program name
    This will output the description for the program(s) with program name in the title.
    Example:
    wtd grep
    Name : cgrep
    Description : Provides many of the features of grep, egrep, and fgrep with
    greatly enhanced performance
    Name : grep
    Description : A string search utility
    Edit: Well, I just showed above with Perl (duh!) I'm still having a multi-line issue with the Provides line. Where a program shows more than one Provides entry it's only deleting the first line.  I'll work on it and get back. Other than that this works (at least it should).
    Edit2: Here is a slightly hacked form of the above command that at least fixes the perl issue. This will still fail when encountering other multi-line Provides lines. I think those are fairly rare so I'm leaving it at that. Sed does have limits and I'm sure a more complex command could be written using sed but I think this will get you in the ballpark.
    pacman -Qi | sed -n '/^Name/,/^Required By/{ /^Version/,/^Provides/d; /^ *perl.*$/d; /^Required By/d; /^Name/{x;p;x}; p }'
    Last edited by harryNID (2009-11-08 19:12:03)

  • Log clean up ?

    is it safe to delete the old log files in these directories?
    C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\Logs
    thanks
    David Ulrich

    yes, though by default Exchange should be aging out old ones every 30 days.
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Log file cleaning problem

    Hi,
    I'm evaluating Berkeley DB Java Edition for my application, and I have the following code:
    public class JETest {
         private Environment env;
         private Database myDb;
         public JETest() throws DatabaseException {
              EnvironmentConfig envConfig = new EnvironmentConfig();
              envConfig.setAllowCreate(true);
              envConfig.setTransactional(false);
              envConfig.setCachePercent(1);
              env = new Environment(new File("/tmp/test2"),envConfig);
              DatabaseConfig dbConfig = new DatabaseConfig();
              dbConfig.setDeferredWrite(true);
              dbConfig.setAllowCreate(true);
              dbConfig.setTransactional(false);
              myDb = env.openDatabase(null, "testing", dbConfig);
         public void cleanup() throws Exception {
              myDb.close();
              env.close();
         private void insertDelete() throws DatabaseException {
              int keyGen = Integer.MIN_VALUE;
              byte[] key = new byte[4];
              byte[] data = new byte[1024];
              ByteBuffer buff = ByteBuffer.wrap(key);
              for (int i=0;i<20000;i++) {
                   buff.rewind();
                   buff.putInt(keyGen++);
                   myDb.put(null, new DatabaseEntry(key), new DatabaseEntry(data));
              int count = 0;
              System.out.println("done inserting");
              keyGen = Integer.MIN_VALUE;
    OperationStatus status;
              for (int i=0;i<20000; i++) {
                   buff.rewind();
                   buff.putInt(keyGen++);
                   count++;
                   status = myDb.delete(null, new DatabaseEntry(key));
    if (status != OperationStatus.SUCCESS) {
                        System.out.println("Delete failed.");
              System.out.println("called delete "+count+" times");
              env.sync();
         public static void main(String[] args) throws Exception {
              JETest test = new JETest();
              test.insertDelete();
              test.cleanup();
    After running the above, I expected that the log file utilization be 0%, because I delete each and every record in the database. The status returned by the delete() method was OperationStatus.SUCCESS for all the invocations.
    I ran the DbSpace utility, and this is what I found:
    $ java -cp je-3.2.13/lib/je-3.2.13.jar com.sleepycat.je.util.DbSpace -h /tmp/test2 -d
    File Size (KB) % Used
    00000000 9765 99
    00000001 3236 99
    TOTALS 13001 99
    Obviously, the cleaner thread won't clean log files that are 99% used.
    I did expect the logs to be completely empty, though. What is going on here?
    Thanks,
    Lior

    Lior,
    With the default heap size (64m) I was able to reproduce the problem you're seeing. I think I understand what's happening.
    First see this note in the javadoc for setDeferredWrite:
    http://www.oracle.com/technology/documentation/berkeley-db/je/java/com/sleepycat/je/DatabaseConfig.html#setDeferredWrite(boolean)
    Note that although deferred write databases can page to disk if the cache is not large enough to hold the databases, they are much more efficient if the database remains in memory. See the JE FAQ on the Oracle Technology Network site for information on how to estimate the cache size needed by a given database. In the current implementation, a deferred write database which is synced or pages to the disk may also add additional log cleaner overhead to the environment. See the je.deferredWrite.temp property in <JEHOME>/example.properties for tuning information on how to ameliorate this cost.
    The statement above about "additional log cleaner overhead" is not quite accurate. Specifically, we do not currently keep track of obsolete information about DW (Deferred Write) databases. We are considering improvements in this area.
    Your test has brought out this issue to an extreme degree because of the very small cache size, and the fact that you delete all records. Most usage of DW that we see involves a bulk data load (no deletes), or deletes performed in memory so the record never goes to disk at all. With the tiny cache in your test, the records do go to disk before they are deleted.
    You can avoid this situation in a couple of different ways:
    1) Use a larger cache. If you insert and delete before calling sync, the inserted records will never be written to disk.
    2) If this is a temporary database (no durability is required), then you can set the je.deferredWrite.temp configuration parameter mentioned above. Setting this to true enables accurate utilization tracking for a DW database, for the case where durability is not required.
    # If true, assume that deferred write database will never be
    # used after an environment is closed. This permits a more efficient
    # form of logging of deferred write objects that overflow to disk
    # through cache eviction or Database.sync() and reduces log cleaner
    # overhead.
    # je.deferredWrite.temp=false
    # (mutable at run time: false)
    Will either of these options work for your application?
    Mark

  • [SOLVED] Where to find pacman install log

    I was wondering whether there was any sort of install log for pacman.
    Also, if I wanted, how could I remove any packages installed between two specified dates (perhaps using the information provided in this log).
    Thanks!
    Last edited by tbgconno (2012-10-10 23:49:23)

    Default location: /var/log/pacman.log
    man pacman.conf:
    LogFile = /path/to/file
    Overrides the default location of the pacman log file. A typical
    default is /var/log/pacman.log. This is an absolute path and the
    root directory is not prepended.
    Also do check man pacman! And search the forums before posting!
    Documentation is there for a purpose.

  • Does cleaning sort records and impact on max log size

    I'm looking for confirmation that the act of cleaning logs produces sorted records, equivalent to having inserted them in sorted order to begin with. If that is the case is the memory overhead of cleaning proportional to the maximum log file size, or will it spill to disk to sort? I ask since the max log file size is 1G, and if there is a memory component then it may be relevant to take into consideration.
    On a similar note, is increasing the log file size from 10MB recommended if the database is large (say a TB)? Are there some linear operations (most likely in the admin/maintenance category) that have to iterate over each log file?
    Thanks.

    Hi,
    I'm looking for confirmation that the act of cleaning logs produces sorted records, equivalent to having inserted them in sorted order to begin with.No, that's not exactly true. When records are written (migrated to the end of the log) during the log cleaning process, any clustering (writing of adjacent records in key order) occurs on a per BIN (bottom internal node) basis. So at most 128 records (or DatabaseConfig.setNodeMaxEntries) with adjacent key values are sorted and written out together in this manner. But normally not all records in a BIN will be migrated and I'll describe more about this below.
    If that is the case is the memory overhead of cleaning proportional to the maximum log file size, or will it spill to disk to sort? I ask since the max log file size is 1G, and if there is a memory component then it may be relevant to take into consideration.No, the memory used for sorting in this case is the JE cache itself -- the memory that holds the Btree. The log cleaner thread moves records to be migrated into the Btree (in the cache), and flags them for migration. These records are written lazily the next time their parent Btree node (the BIN I mentioned) needs to be flushed. This can occur for two reasons: 1) when the BIN is evicted from the cache because the cache is full, or 2) during the next checkpoint, since a checkpoint will flush all dirty BINs. The most desirable situation is that the BIN is flushed during the checkpoint, not during eviction, to reduce the number of times that a single BIN is flushed to disk. If a BIN is evicted, it may have to be fetched again later in order to migrate more records as part of the log cleaning process, and this is counterproductive.
    So during this process, the number of records that are written to disk in key order in a cluster, such that they are physically adjacent on disk, is variable. It depends on how many records are processed by cleaner threads, and inserted in their parent BIN for migration, between checkpoint intervals, and whether the BINs are evicted during this period.
    A physical cluster of records includes the BIN itself as well as its child records that are migrated for log cleaning. The fact that the BIN is part of the cluster is beneficial to apps where not all BINs fit in the cache. If a record and its parent BIN are not in cache, and the app reads that record, the BIN and the record must both be fetched from disk. Since they will be in physical proximity to each other on disk, disk head movement is avoided or reduced.
    However, not all of the child records in a BIN will necessarily be part of a physical cluster. If only some of the records in a BIN were processed by the log cleaner before the BIN is flushed by the checkpointer or evictor, then only a subset of the child records will be written as part of the cluster. In other words, even for a single BIN, all the child records in that BIN are not normally written out together in a cluster.
    Clustering is a useful feature and something we would like to enhance in the future. What I've described above is as far as we've gotten with this feature in the currently released and supported product. However, there are two experimental configuration settings that cause additional clustering to occur. These cause additional records to be written to disk when their parent BIN is flushed. If you're interested in trying these, I will be happy to explain them and work with you. But you should be aware that they're not currently in the standard, supported set of features, and are not well tested.
    I'm not sure whether I've given you less information than you need or more than you wanted. :-) If you describe in detail what you're trying to do, and more about your app and performance requirements, I may be able to offer more concrete advice.
    On a similar note, is increasing the log file size from 10MB recommended if the database is large (say a TB)? Are there some linear operations (most likely in the admin/maintenance category) that have to iterate over each log file?Yes, there are such operations and per-log file overhead, and we recommend using using a 20M to 50M log file size for large data sets. Log files larger than 50MB could decrease log cleaner performance.
    --mark                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • How about a script to clean up /var/cache/pacman/pkg

    /var/cache/pacman/pkg can get filled up with packages that you intalled once, just to try out, but then uninstalled and never plan to install again. I am thinking of a script that removes pkg.tar.gz's that are not installed, which will clear up some truly "dead" space on your hard drive. What do you think?

    munkyeetr wrote:
    oh okay, so they aren't necessary to keep, and they're never used unless you want to reinstall a program.
    thank you.
    Sometimes a package will cause trouble, which is easily escaped by downgrading.  If you have trouble that brakes your internet connection it is so easy to fix by referring to your /var/log/pacman.log (if you have to) & downgrading, using the following method from the Arch Wiki:
    You may be able to downgrade the package trivially by visiting /var/cache/pacman/pkg/ on your system and seeing if the older version of the package is stored there. (If you haven't run pacman -Scc recently, it should be there). If the package is there, you can install that version using pacman -U pkgname-olderpkgver.pkg.tar.gz. If pacman complains about file conflicts, you could force it to do the installation anyway with pacman -Uf pkgname-olderpkgver.pkg.tar.gz.
    We had a kernel bug last October that caused many who did not have a copy of a previous kernel in their cache some extra trouble &  education. ;-)
    If you ever need a superseded kernel have a look here:
    http://ubuntuforums.org/showthread.php?t=954481
    Last edited by handy (2008-12-19 02:10:46)

  • Accidentally RM'd contents of /var/lib/pacman/local/

    I have been working on setting up a new workstation for myself, and getting it to be consistent with the old workstation that I had (with the exception of encrypting all of / this time rather than just encrypting /home).  Have been working on this for some time now and due to many frustrations (hardware related), lack of sleep and too many terminal sessions I ended up running an RM command inside /var/lib/pacman/local, removing all contents.
    I need to find a way to rebuild this if at all possible.  I'm thinking parsing out the package names from the pacman.log and then running reinstall for all things, however that is not really an ideal/clean solution.  Is there a better one that someone can point me to?  I found this: https://bbs.archlinux.org/viewtopic.php?pid=670876 however that seems to provide a list, without explaining further steps and I believe that I can get a list out of pacman.log which should be 100% accurate ... something like: yaourt -S `cat /var/log/pacman.log | grep "\[PACMAN\] installed" | awk '{print $5}' | sort | tr '\n' ' '`
    Open to suggestions on this.  I really do not want to have to start over ... again
    Thanks
    B

    ...or you can post the solution that worked for you so other users who may happen across it and can learn from it.
    https://wiki.archlinux.org/index.php/Fo … way_Street
    Last edited by graysky (2013-10-15 20:26:26)

  • Pacman 3 can't download pkg

    Hi, I just downloaded Arch Duke the LinuxTag edition. Did a clean install and so far so good.
    The problem is I can't install anything using the new pacman 3.
    I did a
    pacman -Sy
    I used the Xfer command to use wget to download the packages. Pacman actually managed to connect to the repository, but it can't download the db. I can see the progress bar but it is not moving. FYI, I used the ftp://ftp.archlinux.org/current/os/i686, so I don't think there is something wrong with the repo.
    I also tried
    pacman --debug -Sy
    but it shows nothing as pacman actually just stuck there when trying to download the file.
    This problem wasn't there when I was using pacman 2.9.8. I expect pacman 3 will do everything the previous version capable to do
    Oh yeah, and I am using proxy.
    Btw, in case anyone asking, this is my pacman.conf:
    # /etc/pacman.conf
    # See the pacman manpage for option directives
    # GENERAL OPTIONS
    [options]
    LogFile = /var/log/pacman.log
    HoldPkg = pacman glibc
    XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
    # REPOSITORIES
    # - can be defined here or included from another file
    # - pacman will search repositories in the order defined here
    # - local/custom mirrors can be added here or in separate files
    # - repositories listed first will take precedence when packages
    # have identical names, regardless of version number
    #[testing]
    #Include = /etc/pacman.d/testing
    [current]
    # Add your preferred servers here, they will be used first
    Include = /etc/pacman.d/current
    [extra]
    # Add your preferred servers here, they will be used first
    Include = /etc/pacman.d/extra
    [community]
    # Add your preferred servers here, they will be used first
    Include = /etc/pacman.d/community
    #[unstable]
    # Add your preferred servers here, they will be used first
    #Include = /etc/pacman.d/unstable
    # An example of a custom package repository. See the pacman manpage for
    # tips on creating your own repositories.
    #[current]
    #Server = file:///mnt/cdrom/arch/pkg
    Please help. Thanks!

    Hi, everyone
    Thanks for the reply.
    The problem might be with your proxy. Try using it without it?
    Unfortunately, I have no control over using proxy or direct connection as I'm using university's connection.
    I've experienced the same problem yesterday when I tried to install Arch within qemu. Everything else network-related worked: I was able to browse the web using links and pacman was even able to download the .db.tar.gz files from the mirror I've selected, but when it came to download the actual packages, pacman stalled.
    My case is a bit different. I also can not download the db file
    My guess is because of the new pacman. I didn't have these problems when I was using earlier version of pacman. So, I expect a workaround to make it work in my box.

  • "FILESYSTEM CHECK FAILED" after pacman -Syu

    Hi all,
    After a sucessfull 'pacman -Syu' (in which i didnt see any 'todo' messages but it did have a kernel upgrade) archlinux cannot start and i just get to a message similar talking about my root partition (ext3):
    The superblock could not be read or does not describe a correct ext2
    filesystem. If the device is valid and it really contains an ext2
    filesystem (and not swap or ufs or something else), then the superblock
    is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
    ******************* FILESYSTEM CHECK FAILED *************
    * Please repair manually and reboot. Note that the root *
    * filesystem is currently mounted read-only. To remount *
    * it read-write type: mount -n -o remount,rw / *
    * When you exit the mantenance shel the system will *
    * reboot automatically. *
    I restarted with a livecd and 'e2fscked' the partition (which btw found many errors that were corrected by it) but archlinux still gives me the same message. I have checked the partition again and again a thousand times but it always comes up clean, im even able to mount it from the different livecds i have tried and can read and create files on it so im pretty sure it is fine.
    And so my question is, does anyone know why this is happening? How comes archlinux keeps seeing a problem in this partition when others dont? What am i doing wrong?
    An y answer appreciated.
    Last edited by feralert (2009-06-03 20:15:23)

    Hi again,
    I have done some testing, maybe it will help.
    After the failure message i put roots password and i got dropped to a shell, if i try to find the root partition (eg. ls /dev/sda) gives an error cause it sda doesnt exists.
    If i edit rc.sysinit with a livecd and remove the fsck part i get a few diferent errors, some about partitions not being found and similar stuff. In my little knowledge of linux it ooks to me like it doesnt load the sata module or somethig...
    I copy here the pacman.log file, i remember that the update was a huge one, around 400 Mbytes if i remember correctly:
    [2009-05-30 22:20] synchronizing package lists
    [2009-05-30 22:21] starting full system upgrade
    [2009-05-30 22:23] synchronizing package lists
    [2009-05-30 22:23] starting full system upgrade
    [2009-05-30 23:29] upgraded alacarte (0.11.10-1 -> 0.12.1-1)
    [2009-05-30 23:29] upgraded kernel-headers (2.6.27.6-2 -> 2.6.29.3-1)
    [2009-05-30 23:29] upgraded tzdata (2009f-1 -> 2009g-1)
    [2009-05-30 23:29] warning: /etc/locale.gen installed as /etc/locale.gen.pacnew
    [2009-05-30 23:29] Generating locales...
    [2009-05-30 23:29] es_ES.UTF-8... done
    [2009-05-30 23:29] es_ES.ISO-8859-1... done
    [2009-05-30 23:29] es_ES.ISO-8859-15@euro... done
    [2009-05-30 23:29] Generation complete.
    [2009-05-30 23:29] upgraded glibc (2.9-4 -> 2.10.1-2)
    [2009-05-30 23:29] upgraded alsa-lib (1.0.19-1 -> 1.0.20-1)
    [2009-05-30 23:29] upgraded alsa-utils (1.0.19-1 -> 1.0.20-1)
    [2009-05-30 23:29] upgraded binutils (2.19.1-1 -> 2.19.1-3)
    [2009-05-30 23:29] upgraded geoip (1.4.5-1 -> 1.4.6-1)
    [2009-05-30 23:29] upgraded gcc-libs (4.3.3-1 -> 4.4.0-2)
    [2009-05-30 23:29] upgraded libdrm (2.4.9-1 -> 2.4.11-2)
    [2009-05-30 23:29] upgraded libgl (7.4.1-1 -> 7.4.2-2)
    [2009-05-30 23:29] upgraded mesa (7.4.1-1 -> 7.4.2-1)
    [2009-05-30 23:29] upgraded wxgtk (2.8.9.2-1 -> 2.8.10-1)
    [2009-05-30 23:29] upgraded amule (2.2.4-1 -> 2.2.5-2)
    [2009-05-30 23:29] upgraded x264 (20090216-1 -> 20090416-1)
    [2009-05-30 23:29] upgraded avidemux (2.4.4-2 -> 2.4.4-3)
    [2009-05-30 23:29] upgraded bin86 (0.16.17-3 -> 0.16.17-4)
    [2009-05-30 23:29] upgraded gmp (4.2.4-1.1 -> 4.3.1-2)
    [2009-05-30 23:29] upgraded coreutils (7.2-1 -> 7.4-1)
    [2009-05-30 23:29] upgraded dbus-core (1.2.4.4permissive-1 -> 1.2.14-1)
    [2009-05-30 23:29] upgraded glib2 (2.20.1-1 -> 2.20.2-1)
    [2009-05-30 23:29] upgraded bluez (4.37-1 -> 4.39-1)
    [2009-05-30 23:29] upgraded gstreamer0.10 (0.10.22-1 -> 0.10.23-1)
    [2009-05-30 23:29] upgraded gstreamer0.10-base (0.10.22-1 -> 0.10.23-1)
    [2009-05-30 23:29] upgraded gstreamer0.10-base-plugins (0.10.22-1 -> 0.10.23-1)
    [2009-05-30 23:29] upgraded brasero (2.26.1-2 -> 2.26.2-1)
    [2009-05-30 23:29] upgraded policykit (0.9-7 -> 0.9-9)
    [2009-05-30 23:29] upgraded consolekit (0.3.0-3 -> 0.3.0-5)
    [2009-05-30 23:29] upgraded cpio (2.9-3 -> 2.9-5)
    [2009-05-30 23:29] upgraded curl (7.19.4-1 -> 7.19.5-2)
    [2009-05-30 23:29] upgraded dbus (1.2.4.4permissive-1 -> 1.2.14-1)
    [2009-05-30 23:29] upgraded dcron (3.2-3 -> 3.2-4)
    [2009-05-30 23:29] upgraded dhcpcd (4.0.12-1 -> 5.0.4-1)
    [2009-05-30 23:29] upgraded dmapi (2.2.9-1 -> 2.2.10-1)
    [2009-05-30 23:29] upgraded docbook-xml (4.5-1 -> 4.5-2)
    [2009-05-30 23:29] upgraded gconf (2.26.0-3 -> 2.26.2-1)
    [2009-05-30 23:29] upgraded gnome-desktop (2.26.1-1 -> 2.26.2-1)
    [2009-05-30 23:29] upgraded gdbm (1.8.3-5 -> 1.8.3-6)
    [2009-05-30 23:29] upgraded sqlite3 (3.6.13-1 -> 3.6.14.1-1)
    [2009-05-30 23:29] upgraded python (2.6.1-1 -> 2.6.2-1)
    [2009-05-30 23:29] upgraded eog (2.26.1-1 -> 2.26.2-1)
    [2009-05-30 23:30] upgraded epiphany (2.26.1-1 -> 2.26.2-1)
    [2009-05-30 23:30] upgraded poppler (0.10.6-1 -> 0.10.7-1)
    [2009-05-30 23:30] upgraded poppler-glib (0.10.6-1 -> 0.10.7-1)
    [2009-05-30 23:30] upgraded evince (2.26.1-1 -> 2.26.2-1)
    [2009-05-30 23:30] upgraded libsoup (2.26.1-1 -> 2.26.2-1)
    [2009-05-30 23:30] upgraded evolution-data-server (2.26.1.1-1 -> 2.26.2-1)
    [2009-05-30 23:30] upgraded ffmpeg (20090217-1 -> 0.5-1)
    [2009-05-30 23:30] upgraded file (5.00-1 -> 5.03-2)
    [2009-05-30 23:30] upgraded file-roller (2.26.1-1 -> 2.26.2-1)
    [2009-05-30 23:30] upgraded findutils (4.4.0-1 -> 4.4.1-2)
    [2009-05-30 23:30] upgraded gcalctool (5.26.1-1 -> 5.26.2-1)
    [2009-05-30 23:30] installed ppl (0.10.2-2)
    [2009-05-30 23:30] installed cloog-ppl (0.15.3-1)
    [2009-05-30 23:30] upgraded gcc (4.3.3-1 -> 4.4.0-2)
    [2009-05-30 23:30] upgraded gtksourceview2 (2.6.1-1 -> 2.6.2-1)
    [2009-05-30 23:30] upgraded gedit (2.26.1-1 -> 2.26.2-1)
    [2009-05-30 23:30] upgraded glproto (1.4.9-1 -> 1.4.10-1)
    [2009-05-30 23:30] upgraded gnome-games (2.26.1-1 -> 2.26.2-1)
    [2009-05-30 23:30] upgraded whois (4.7.33-1 -> 4.7.33-2)
    [2009-05-30 23:30] upgraded gnome-nettool (2.26.1-1 -> 2.26.2-1)
    [2009-05-30 23:30] upgraded policykit-gnome (0.9.2-3 -> 0.9.2-4)
    [2009-05-30 23:30] upgraded gnome-panel (2.26.1-1 -> 2.26.2-1)
    [2009-05-30 23:31] upgraded gnome-power-manager (2.26.1-1 -> 2.26.1-2)
    [2009-05-30 23:31] upgraded vte (0.20.1-1 -> 0.20.2-1)
    [2009-05-30 23:31] upgraded gnome-terminal (2.26.1-1 -> 2.26.2-2)
    [2009-05-30 23:31] upgraded gtk-engines (2.18.1-1 -> 2.18.2-1)
    [2009-05-30 23:31] upgraded gnome-themes (2.26.1-1 -> 2.26.2-1)
    [2009-05-30 23:31] upgraded gnome2-user-docs (2.26.1-1 -> 2.26.2-1)
    [2009-05-30 23:31] upgraded gparted (0.4.4-2 -> 0.4.5-1)
    [2009-05-30 23:31] upgraded gstreamer0.10-bad (0.10.11-1 -> 0.10.12-1)
    [2009-05-30 23:31] upgraded libraw1394 (1.3.0-2 -> 2.0.2-1)
    [2009-05-30 23:31] installed libusb1 (1.0.0-1)
    [2009-05-30 23:31] upgraded libdc1394 (2.0.3-1 -> 2.1.0-1)
    [2009-05-30 23:31] upgraded libdvdread (0.9.7-2 -> 4.1.3-1)
    [2009-05-30 23:31] upgraded libdvdnav (0.1.10-3 -> 4.1.3-1)
    [2009-05-30 23:31] upgraded neon (0.28.3-2 -> 0.28.4-1)
    [2009-05-30 23:31] installed liblrdf (0.4.0-6)
    [2009-05-30 23:31] upgraded gstreamer0.10-bad-plugins (0.10.11-3 -> 0.10.12-1)
    [2009-05-30 23:31] upgraded gstreamer0.10-good (0.10.14-1 -> 0.10.15-1)
    [2009-05-30 23:31] upgraded libavc1394 (0.5.3-2 -> 0.5.3-3)
    [2009-05-30 23:31] upgraded libiec61883 (1.1.0-1 -> 1.2.0-1)
    [2009-05-30 23:31] installed libcaca (0.99.beta16-1)
    [2009-05-30 23:31] upgraded gstreamer0.10-good-plugins (0.10.14-1 -> 0.10.15-1)
    [2009-05-30 23:31] upgraded gstreamer0.10-ugly-plugins (0.10.11-1 -> 0.10.11-2)
    [2009-05-30 23:31] upgraded gtkhtml (3.26.1.1-1 -> 3.26.2-1)
    [2009-05-30 23:31] upgraded gucharmap (2.26.1-1 -> 2.26.2-1)
    [2009-05-30 23:31] upgraded libarchive (2.6.2-1 -> 2.7.0-1)
    [2009-05-30 23:31] NOTE
    [2009-05-30 23:31] ----
    [2009-05-30 23:31] Add your user to group 'camera' to use camera devices.
    [2009-05-30 23:31] upgraded libgphoto2 (2.4.4-1 -> 2.4.6-1)
    [2009-05-30 23:31] upgraded gvfs (1.2.2-1 -> 1.2.3-1)
    [2009-05-30 23:31] upgraded gzip (1.3.12-4 -> 1.3.12-6)
    [2009-05-30 23:31] upgraded jfsutils (1.1.13-1 -> 1.1.14-1)
    [2009-05-30 23:31] upgraded libsndfile (1.0.19-1 -> 1.0.20-1)
    [2009-05-30 23:31] upgraded sox (14.2.0-2 -> 14.2.0-3)
    [2009-05-30 23:31] installed ilmbase (1.0.1-1)
    [2009-05-30 23:31] installed openexr (1.6.1-1)
    [2009-05-30 23:31] upgraded libpng (1.2.35-1 -> 1.2.36-1)
    [2009-05-30 23:31] upgraded qt (4.5.0-5 -> 4.5.1-3)
    [2009-05-30 23:31] installed xine-lib (1.1.16.3-3)
    [2009-05-30 23:31] installed phonon (4.3.1-2)
    [2009-05-30 23:31] installed clucene (0.9.21b-1)
    [2009-05-30 23:31] installed exiv2 (0.18-1)
    [2009-05-30 23:31] installed strigi (0.6.4-2)
    [2009-05-30 23:31] installed soprano (2.2.3-1)
    [2009-05-30 23:31] installed xdg-utils (1.0.2-1)
    [2009-05-30 23:31] installed kdelibs (4.2.3-1)
    [2009-05-30 23:31] installed kdebase-runtime (4.2.3-1)
    [2009-05-30 23:31] installed fftw (3.2.1-1)
    [2009-05-30 23:31] installed libofa (0.9.3-2)
    [2009-05-30 23:31] installed tunepimp (0.5.3-6)
    [2009-05-30 23:31] installed kdemultimedia (4.2.3-1)
    [2009-05-30 23:31] installed polkit-qt (0.9.2-1)
    [2009-05-30 23:31] upgraded k3b (1.0.5-2 -> 1.66.0alpha2-1)
    [2009-05-30 23:32] upgraded qt3 (3.3.8-10 -> 3.3.8-11)
    [2009-05-30 23:32] upgraded kdelibs3 (3.5.10-2 -> 3.5.10-3)
    [2009-05-30 23:32] >>> Updating module dependencies. Please wait ...
    [2009-05-30 23:32] >>> MKINITCPIO SETUP
    [2009-05-30 23:32] >>> ----------------
    [2009-05-30 23:32] >>> If you use LVM2, Encrypted root or software RAID,
    [2009-05-30 23:32] >>> Ensure you enable support in /etc/mkinitcpio.conf .
    [2009-05-30 23:32] >>> More information about mkinitcpio setup can be found here:
    [2009-05-30 23:32] >>> http://wiki.archlinux.org/index.php/Mkinitcpio
    [2009-05-30 23:32]
    [2009-05-30 23:32] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
    [2009-05-30 23:32] ==> Building image "default"
    [2009-05-30 23:32] ==> Running command: /sbin/mkinitcpio -k 2.6.29-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
    [2009-05-30 23:32] :: Begin dry run
    [2009-05-30 23:32] :: Parsing hook [base]
    [2009-05-30 23:32] :: Parsing hook [udev]
    [2009-05-30 23:32] :: Parsing hook [autodetect]
    [2009-05-30 23:32] :: Parsing hook [sata]
    [2009-05-30 23:32] :: Parsing hook [keymap]
    [2009-05-30 23:32] :: Parsing hook [filesystems]
    [2009-05-30 23:32] :: Generating module dependencies
    [2009-05-30 23:32] :: Generating image '/boot/kernel26.img'...SUCCESS
    [2009-05-30 23:32] ==> SUCCESS
    [2009-05-30 23:32] ==> Building image "fallback"
    [2009-05-30 23:32] ==> Running command: /sbin/mkinitcpio -k 2.6.29-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
    [2009-05-30 23:32] :: Begin dry run
    [2009-05-30 23:32] :: Parsing hook [base]
    [2009-05-30 23:32] :: Parsing hook [udev]
    [2009-05-30 23:32] :: Parsing hook [sata]
    [2009-05-30 23:32] :: Parsing hook [keymap]
    [2009-05-30 23:32] :: Parsing hook [filesystems]
    [2009-05-30 23:33] :: Generating module dependencies
    [2009-05-30 23:33] :: Generating image '/boot/kernel26-fallback.img'...SUCCESS
    [2009-05-30 23:33] ==> SUCCESS
    [2009-05-30 23:33] upgraded kernel26 (2.6.29.2-1 -> 2.6.29.4-1)
    [2009-05-30 23:33] upgraded klibc (1.5.15-1 -> 1.5.15-2)
    [2009-05-30 23:33] upgraded klibc-extras (2.5-2 -> 2.5-3)
    [2009-05-30 23:33] upgraded klibc-kbd (1.15.20080312-8 -> 1.15.20080312-9)
    [2009-05-30 23:33] upgraded klibc-module-init-tools (3.5-1 -> 3.5-2)
    [2009-05-30 23:33] upgraded klibc-udev (141-1 -> 141-2)
    [2009-05-30 23:33] upgraded libdownload (1.3-1 -> 1.3-3)
    [2009-05-30 23:33] upgraded libgsf (1.14.12-1 -> 1.14.13-1)
    [2009-05-30 23:33] upgraded libsasl (2.1.22-7 -> 2.1.22-8)
    [2009-05-30 23:33] upgraded lsof (4.81-1 -> 4.82-1)
    [2009-05-30 23:33] upgraded lzo2 (2.02-3 -> 2.03-1)
    [2009-05-30 23:33] upgraded man-pages (3.20-2 -> 3.21-1)
    [2009-05-30 23:33] upgraded metacity (2.26.0-1 -> 2.26.0-2)
    [2009-05-30 23:33] upgraded mlocate (0.21.1-1 -> 0.22-1)
    [2009-05-30 23:33] upgraded mplayer (28347-4 -> 29318-1)
    [2009-05-30 23:33] upgraded mtools (4.0.10-1 -> 4.0.10-2)
    [2009-05-30 23:33] upgraded nautilus (2.26.2-1 -> 2.26.3-1)
    [2009-05-30 23:33] upgraded net-tools (1.60-13 -> 1.60-14)
    [2009-05-30 23:33] * relogin or source /etc/profile.d/openoffice.sh
    [2009-05-30 23:33] * see http://wiki.archlinux.org/index.php/Openoffice
    [2009-05-30 23:33] how to use extensions, e.g. for spell checking
    [2009-05-30 23:33] see /opt/openoffice/share/extension/install what
    [2009-05-30 23:33] is shipped with this package
    [2009-05-30 23:33] upgraded openoffice-base (3.0.1-1 -> 3.1.0-1)
    [2009-05-30 23:33] upgraded openoffice-es (3.0.1-1 -> 3.1.0-1)
    [2009-05-30 23:33] warning: /etc/pacman.d/mirrorlist installed as /etc/pacman.d/mirrorlist.pacnew
    [2009-05-30 23:33] upgraded pacman-mirrorlist (20090405-1 -> 20090509-1)
    [2009-05-30 23:33] upgraded pango (1.24.1-1 -> 1.24.2-1)
    [2009-05-30 23:33] upgraded pidgin (2.5.5-2 -> 2.5.6-1)
    [2009-05-30 23:33] upgraded tcp_wrappers (7.6-8 -> 7.6-9)
    [2009-05-30 23:33] upgraded portmap (6.0-2 -> 6.0-3)
    [2009-05-30 23:33] upgraded ppp (2.4.4-7 -> 2.4.4-8)
    [2009-05-30 23:33] upgraded procps (3.2.7-5 -> 3.2.8-1)
    [2009-05-30 23:33] upgraded psmisc (22.6-2 -> 22.7-1)
    [2009-05-30 23:33] upgraded pycairo (1.8.2-1 -> 1.8.4-1)
    [2009-05-30 23:33] upgraded pygobject (2.16.1-1 -> 2.18.0-1)
    [2009-05-30 23:33] upgraded python-gdata (1.3.0-1 -> 1.3.1-1)
    [2009-05-30 23:33] upgraded python-nose (0.10.4-3 -> 0.11.0-1)
    [2009-05-30 23:33] upgraded python-numpy (1.3.0-1 -> 1.3.0-2)
    [2009-05-30 23:33] upgraded rsync (3.0.5-1 -> 3.0.6-1)
    [2009-05-30 23:34] upgraded seahorse (2.26.1-1 -> 2.26.2-1)
    [2009-05-30 23:34] upgraded seahorse-plugins (2.26.1-1 -> 2.26.2-1)
    [2009-05-30 23:34] upgraded sysfsutils (2.1.0-4 -> 2.1.0-5)
    [2009-05-30 23:34] upgraded syslinux (3.75-4 -> 3.80-1)
    [2009-05-30 23:34] upgraded sysvinit (2.86-4 -> 2.86-5)
    [2009-05-30 23:34] upgraded tomboy (0.14.1-1 -> 0.14.2-1)
    [2009-05-30 23:34] upgraded transmission-gtk (1.42-1 -> 1.60-1)
    [2009-05-30 23:34] upgraded unrar (3.9.1-1 -> 3.9.3-1)
    [2009-05-30 23:34] upgraded usbutils (0.81-1 -> 0.82-1)
    [2009-05-30 23:35] upgraded vlc (0.9.9a-1 -> 0.9.9a-4)
    [2009-05-30 23:35] upgraded wireless_tools (29-2 -> 29-3)
    [2009-05-30 23:35] upgraded xfsprogs (3.0.0-1 -> 3.0.1-1)
    [2009-05-30 23:35] upgraded xkeyboard-config (1.5-1 -> 1.6-1)
    [2009-05-30 23:35] upgraded xorg-server-utils (7.4-5 -> 7.4-6)
    [2009-05-30 23:35] upgraded xorg-server (1.6.1-1 -> 1.6.1.901-1)

  • Pacman feature request "Package purge uninstall"

    hello
    I have been thinking about this issue for a long long time and have posted it in the forums many time in various ways, but maybe  I can explain the issue properly and experts can chime in.
    This is regarding keeping the file system extremely clean what i mean by that is having very high level of control over what files are installed in all the directories except /home.
    The purpose is to revert the file system to the way it was when the system was freshly installed.
    Case: Samba
    If I install samba in my fresh install machine, I will most probably change /etc/samba/smb.conf now what it does is when I decide remove samba even using pacman -Rscn samba I am left with /etc/samba directory which is pure junk, I do understand pacman not wanting to remove files which have been edited but I would like to have a purge option which takes away the files and directories installed by a package, I am not a developer but is there a place where I can ask for this feature?
    What will this feature mean?
    This will make reverting to fresh install really easy. If after the fresh install i have added lots of packages all I need to do is to remove those packages with the purge option and my install is back to fresh install state, ofcourse i wouldhave to replace all config files with their respective pacnew files.
    Is this a valid request? can any expert share their thoughts as to why it can/ cannot be implemented?
    Thanks for reading

    +1 to this suggestion: I too find myself trawling the system to clean-up any remaining files and directories after an uninstall of any package.
    Though I suppose it would be hard to determine what to remove (as mentioned in the bug tracker), we could look at an in between solution. Various uninstall programs on windows systems provide a list of folders and files that where not removed. We could provide a similar list.
    In the case of samba, the uninstall sequence could create a notion in the pacman logs along the lines of:
    Created during installation but not removed:
    *DIR: /etc/samba/
    *FILE: /etc/rc.d/samba
    Any subsequent action would then be up to the end user. Pacman should also output to terminal if any files / directories remain on the system after an uninstall, along the lines of:
    $ pacman -R samba
    # (1/1) samba removed
    # There are unremoved files / directories, check /var/log/pacman.log for more details!
    Last edited by stefanwilkens (2009-04-26 11:42:58)

Maybe you are looking for

  • JWS can't find dependent native library

    Hi, my JNLP file contains the following snippet <resources os="Windows"> <nativelib href="lib/windows/corelib.jar"/> </resources> where corelib.jar contains several DLL files. The first DLL depends on others contained in the same jar file. Lauching t

  • TIPS(18) : CREATING SCRIPTS TO RECREATE A TABLE STRUCTURE

    제품 : SQL*PLUS 작성날짜 : 1996-11-12 TIPS(18) : Creating Scripts to Recreate a Table Structure ========================================================= The script creates scripts that can be used to recreate a table structure. For example, this script ca

  • Original and transferred calls

    Hi All, In TCD what is the common field between an original inbound call and a transferred one by the agent. Agent ID is not displayed in transferred call field. Regards,

  • Cs 5.1 broken subpicture

    So I have an encore project for an old client we're updating and everything seems to be fine. The original project was in CS3, now we're working in CS 5.1 The problem is that the subpicture appears to be broken. When pressing the display subpicture b

  • Migrating clients from NT to XP testing

    Hi, I am migrating several applications including client to windows XP plus some of these apps will be patched to latest levels. What kind of tests would someone recommend to perform to check the client apps are working ok?