Date: Tue, 31 Oct 2017 14:07:04 +0900 (JST) From: Yasuhiro KIMURA <yasu@utahime.org> To: freebsd-questions@freebsd.org Subject: Re: Ways to help investigating behavior of periodic scripts Message-ID: <20171031.140704.2161058700193756206.yasu@utahime.org> In-Reply-To: <20171031010627.cda5cd42.freebsd@edvax.de> References: <20171031.080731.85349314815802482.yasu@utahime.org> <20171031010627.cda5cd42.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
From: Polytropon <freebsd@edvax.de> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20171031.140704.2161058700193756206.yasu>