From owner-freebsd-questions@FreeBSD.ORG Sat Jun 27 16:17:17 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 438A41065670 for ; Sat, 27 Jun 2009 16:17:17 +0000 (UTC) (envelope-from zhangweiwu@realss.com) Received: from bossdog.realss.com (bossdog.realss.com [211.157.114.130]) by mx1.freebsd.org (Postfix) with ESMTP id E95E18FC13 for ; Sat, 27 Jun 2009 16:17:16 +0000 (UTC) (envelope-from zhangweiwu@realss.com) Received: from localhost (unknown [127.0.0.1]) by bossdog.realss.com (Postfix) with ESMTP id 1BB001C00CE; Sun, 28 Jun 2009 00:17:14 +0800 (CST) Received: from bossdog.realss.com ([127.0.0.1]) by localhost (bossdog.realss.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09575-02; Sun, 28 Jun 2009 00:17:14 +0800 (CST) Received: from [192.168.1.118] (unknown [123.116.112.112]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by bossdog.realss.com (Postfix) with ESMTP id B45141C002F; Sun, 28 Jun 2009 00:17:13 +0800 (CST) Message-ID: <4A4645FE.4040606@realss.com> Date: Sun, 28 Jun 2009 00:17:02 +0800 From: Zhang Weiwu User-Agent: Mozilla-Thunderbird 2.0.0.19 (X11/20090103) MIME-Version: 1.0 To: Modulok References: <4A461551.7090702@realss.com> <64c038660906270721v6908c058l53cc574ce43f40a1@mail.gmail.com> In-Reply-To: <64c038660906270721v6908c058l53cc574ce43f40a1@mail.gmail.com> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at bossdog.realss.com Cc: FreeBSD Questions mailing list Subject: Re: scripting suggestion: how to make this command shorter X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jun 2009 16:17:17 -0000 Modulok wrote: > Zhang, > > Perhaps you could put it into a text file and have cron simply execute > the text file. By doing so, you are free to break it up into a more > digestible format and start using programming constructs to make your > life easier. (Such as storing values in variables, or processing > standard input so the script can be called with various URL's and so > forth.) Your cron job could then simply execute "/home/you/bin/foo", > where 'foo' is whatever you decide to name the script. > > Is there any specific reason why this has to be all on one line? > -Modulok- Nothing more than curiosity and small benefit of not having to take care one more file. I know what you mean:)