From owner-freebsd-questions@FreeBSD.ORG Wed May 29 11:38:38 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 063A010E; Wed, 29 May 2013 11:38:38 +0000 (UTC) (envelope-from yerenkow@gmail.com) Received: from mail-pb0-x233.google.com (mail-pb0-x233.google.com [IPv6:2607:f8b0:400e:c01::233]) by mx1.freebsd.org (Postfix) with ESMTP id D2CB518A; Wed, 29 May 2013 11:38:37 +0000 (UTC) Received: by mail-pb0-f51.google.com with SMTP id jt11so9067517pbb.38 for ; Wed, 29 May 2013 04:38:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=52+f6DkQGSiqjofDdzyCkrfq3wsdjttSO2HlyCXpHps=; b=oHU9cqQv5MtyETz9rvXcaRspurVarbY20+yA2DryJBQbsQtJjkupexdbve/P67B89d DcFP3hXoM8MbINwseoaFKNoIBIp1KOmJYPWdmTlhDNpaQb/SSlMniJbV+T9MvkU7xV1X dlbW1XuLK6R5NRsh6YooehBo5amfc8J0ZGizZHYPO7p0HY+7GMWL6RxEIFkn93Ks5x2o /xD2NgM6Bty82EdNeDnZ/y/aAZYSvsU9Kkl3bMj5uIczLd4Fl2X8HBiG4J/zxMdlS4vr fpt1P4ReJJ1ho48yVozcpaPjy9uJlGu8My8erCBJ5IVlOFyWiP0zUjOAQ8Hq5BM1Cgb0 DqTw== MIME-Version: 1.0 X-Received: by 10.68.176.133 with SMTP id ci5mr2483181pbc.21.1369827517605; Wed, 29 May 2013 04:38:37 -0700 (PDT) Received: by 10.68.239.103 with HTTP; Wed, 29 May 2013 04:38:37 -0700 (PDT) In-Reply-To: <1369801479.2670.YahooMailNeo@web190706.mail.sg3.yahoo.com> References: <20130528230140.A5B396F448@smtp.hushmail.com> <51A541B5.3010905@gmail.com> <1369801479.2670.YahooMailNeo@web190706.mail.sg3.yahoo.com> Date: Wed, 29 May 2013 14:38:37 +0300 Message-ID: Subject: Re: BSD sleep From: Alexander Yerenkow To: Quark Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Kenta Suzumoto , Joshua Isom , "freebsd-questions@freebsd.org" , "freebsd-current@freebsd.org" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 May 2013 11:38:38 -0000 >what is stopping from interpreting 1h in similar manner to 3600? i.e. from now No, this is user-friendly, and thus can't be done :) But if think a second, sleep is used rarely by average users, mostly by programmers and other scripts, and they should know better what they are doing. Seriously, that explanation about different hours is not enough to prevent at least useful option. like sleep -f 1h (-f means force convert, without it you can see good explanation why sleep for 1 hour will be not sleep for 1 hour, and etc, and not get sleep at all.). Exact units in which sleeps happens (seconds, ticks, minutes, years) can be described in manual page, even without accepting m,h - that info would be useful for one. P.S. There is already non-portable feature in sleep - non-integer, and I'm sure that no one thought about some financists from various countries, who used to specify long numbers with separator, e.g. 3.600, and this means for them one hour and not 3 point 6 seconds. -- Regards, Alexander Yerenkow