Amanda-Users

Unexpected 'gzip --best' processes

2004-10-21 12:28:23
Subject: Unexpected 'gzip --best' processes
From: Toralf Lund <toralf AT procaptura DOT com>
To: Amanda Mailing List <amanda-users AT amanda DOT org>
Date: Thu, 21 Oct 2004 18:19:12 +0200
This may be related to our backup problems described earlier:

I just noticed that during a dump running just now, I have

# ps -f -C gzip
UID        PID  PPID  C STIME TTY          TIME CMD
amanda    3064   769  0 17:18 pts/5    00:00:00 /bin/gzip --best
amanda    3129   773  0 17:44 pts/5    00:00:00 /bin/gzip --best

on the Amanda server. Parents are
# ps -f -p 769 -p 773
UID        PID  PPID  C STIME TTY          TIME CMD
amanda     769   743  0 12:44 pts/5    00:00:00 dumper0 ks/incr
amanda     773   743  0 12:44 pts/5    00:00:00 dumper2 ks/incr

what's strange about this, is that I'm neither using server compression, nor the 
"best" compress options.

My dumptype setup is (this is for my incremental-only backup to harddisk):

define dumptype global {
   comment "Global definitions"
   index yes
   compress client fast
   strategy incronly
   skip-full
}

define dumptype full-tar {
   global
   program "GNUTAR"   
   comment "Dump of files via tar"
   priority high
   exclude list optional ".amanda.excludes"   
}

Any ideas why I get these processes?

- Toralf



<Prev in Thread] Current Thread [Next in Thread>