From owner-freebsd-questions@FreeBSD.ORG Wed Aug 31 16:44:08 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 33B0816A420 for ; Wed, 31 Aug 2005 16:44:08 +0000 (GMT) (envelope-from rubenl@bloemgarten.demon.nl) Received: from post-24.mail.nl.demon.net (post-24.mail.nl.demon.net [194.159.73.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D81C43D5C for ; Wed, 31 Aug 2005 16:44:07 +0000 (GMT) (envelope-from rubenl@bloemgarten.demon.nl) Received: from axelds.demon.nl ([83.160.138.74]:49830 helo=abubbletprpdda) by post-24.mail.nl.demon.net with esmtp (Exim 4.51) id 1EAVh0-000KMM-FD; Wed, 31 Aug 2005 16:44:06 +0000 From: "Ruben Bloemgarten" To: "'martin hudec'" , Date: Wed, 31 Aug 2005 18:43:00 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1250" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 In-Reply-To: <20050831163022.GE39126@amber.aeternal.net> X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 thread-index: AcWuSV5tHJLbv/rWRw61UWAhJ0NmcgAAVfxg Message-Id: <20050831164407.9D81C43D5C@mx1.FreeBSD.org> Cc: Subject: RE: portsnap and updates using cron X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ruben@bloemgarten.demon.nl List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Aug 2005 16:44:08 -0000 Hi there, To run portsnap and/or freebsd update as a cron job use : #portsnap cron *NOT fetch Regards, Ruben -----Original Message----- From: owner-freebsd-questions@freebsd.org [mailto:owner-freebsd-questions@freebsd.org] On Behalf Of martin hudec Sent: August 31, 2005 6:30 PM To: freebsd-questions@freebsd.org Subject: Re: portsnap and updates using cron Hello, On Thu, Sep 01, 2005 at 02:07:57AM +1000 or thereabouts, Norberto Meijome wrote: > man ktrace > man kdump > > in a nutshell: ktrace shows the kernel calls that a process is > executing. It creates a dump file which you can view with kdump. similar > (better actually) than strace and whatever other ?trace found in linux. Hmmm, thanks for info, this kstuff is really much much better than strace :). Never heard of that, but now I am pretty impressed. Thanks. > then it seems it's a portsnap problem and not cron...get it working in > your normal shell first and then focus on automating it. (btw, what's > wrong with (cd /usr/ports/ ; make update) , or a cvsup cmd line?) Portsnap is working pretty well in normal shell. I was using cvsup before portsnap, but now, as portsnap is being part of base system I am considering to switch to it on all our production servers. I am also going to give a try to make update in /usr/ports. Thank you! -- martin hudec * 421 907 303 393 * corwin@aeternal.net * http://www.aeternal.net "Nothing travels faster than the speed of light with the possible exception of bad news, which obeys its own special laws." Douglas Adams, "The Hitchhiker's Guide to the Galaxy" -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.10.17/85 - Release Date: 08/30/2005 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.10.17/85 - Release Date: 08/30/2005