From owner-freebsd-questions@freebsd.org Tue Oct 31 05:08:00 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AC30EE4E0B9 for ; Tue, 31 Oct 2017 05:08:00 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from gate.utahime.jp (ipq210.utahime.jp [183.180.29.210]) by mx1.freebsd.org (Postfix) with ESMTP id 7F16C3EDE for ; Tue, 31 Oct 2017 05:07:59 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from eastasia.home.utahime.org (eastasia.home.utahime.org [192.168.174.1]) by gate.utahime.jp (Postfix) with ESMTP id 1F6A519F8C; Tue, 31 Oct 2017 14:07:58 +0900 (JST) Received: from eastasia.home.utahime.org (localhost [127.0.0.1]) by localhost-backdoor.home.utahime.org (Postfix) with ESMTP id BE2B42E042; Tue, 31 Oct 2017 14:07:57 +0900 (JST) Received: from localhost (rolling.home.utahime.org [192.168.174.11]) by eastasia.home.utahime.org (Postfix) with ESMTPSA id 7FFE02E041; Tue, 31 Oct 2017 14:07:57 +0900 (JST) Date: Tue, 31 Oct 2017 14:07:04 +0900 (JST) Message-Id: <20171031.140704.2161058700193756206.yasu@utahime.org> To: freebsd-questions@freebsd.org Subject: Re: Ways to help investigating behavior of periodic scripts From: Yasuhiro KIMURA In-Reply-To: <20171031010627.cda5cd42.freebsd@edvax.de> References: <20171031.080731.85349314815802482.yasu@utahime.org> <20171031010627.cda5cd42.freebsd@edvax.de> X-Mailer: Mew version 6.7 on Emacs 25.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Oct 2017 05:08:00 -0000 From: Polytropon Subject: Re: Ways to help investigating behavior of periodic scripts Date: Tue, 31 Oct 2017 01:06:27 +0100 >> So are there any ways to help investigating this delay? >> (Option to make periodic(8) write start and end time of each script to >> syslog, for example.) > > You could add this manually to /usr/sbin/periodic; I'm not > aware of a built-in mechanism to log the starting / finishing > time of the many scripts that are run (depending on daily, > weekly or monthly call). Oh, I checked /usr/sbin/periodic and understood. It's shell script. Then I can directly add any code for investigation. And I know logger(1) can be used to write to syslog from shell script. So I can achieve what I said as example. Thank you for information. --- Yasuhiro KIMURA