Date: Wed, 21 Apr 2010 19:56:51 -0400 (EDT) From: vogelke+unix@pobox.com (Karl Vogel) To: freebsd-questions@freebsd.org Subject: Re: Kill via Cron... Message-ID: <20100421235651.E4F35BDF4@bsd118.wpafb.af.mil> In-Reply-To: <4BCEC689.4030300@infracaninophile.co.uk> (message from Matthew Seaman on Wed, 21 Apr 2010 10:34:01 %2B0100) References: <002c01cae05e$7eab3ea0$7c01bbe0$@wakefield.sch.uk> <20100420183859.C52D9BE09@bsd118.wpafb.af.mil> <86r5m9yk0q.fsf@red.stonehenge.com> <003e01cae12d$b9f2b770$2dd82650$@wakefield.sch.uk> <4BCEC689.4030300@infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
>> On 21/04/2010 09:36:24, mcoyles wrote:
M> I'm actually trying to kill the following in one swep if they've taken
M> more than 8 hours to complete... :
M> 62221 ?? S 0:27.11 gzip -q
M> 62223 ?? DL 0:01.80 /sbin/dump -0 -auf - /usr (dump)
M> 62224 ?? DL 0:01.79 /sbin/dump -0 -auf - /usr (dump)
M> 62225 ?? DL 0:01.81 /sbin/dump -0 -auf - /usr (dump)
If they're running under the same process groupid, then sending it a
signal via killpg(2) would kill them all. Two things that might help:
* The default blocksize (Kb/output block) in dump used to be 10, but you
could go as high as 64. Check the -b option.
* Use "gzip -1q" for speed at the cost of slightly less compression.
"compress -c" also works very well on dump images, and it's fast.
--
Karl Vogel I don't speak for the USAF or my company
phrasemonger, noun: a person who uses phrases or quotes that
were coined by other people. --http://www.wordspy.com/TechWordSpy/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100421235651.E4F35BDF4>