| Summary: | small change in /etc/periodic/*/999.local | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Base System | Reporter: | Jan Srzednicki <winfried> | ||||
| Component: | conf | Assignee: | Crist J. Clark <cjc> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Only Me | ||||||
| Priority: | Normal | ||||||
| Version: | 4.4-STABLE | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
|
Description
Jan Srzednicki
2001-12-24 14:30:01 UTC
On Mon, Dec 24, 2001 at 02:26:11PM -0000, Jan Srzednicki wrote: [snip] > The /etc/periodic/*/999.local script will only allow to run a sh script. > Suerly you can put other scripts in cron, but I think it would be nice to > have such scripts run via periodic.conf (and receive daily reports from > in one mail). As stated in the comments for the 999.local script, it only really exists for back compatibilty with /etc/daily.local. For the functionality you desire, the recommended way to go is to use functionality built into periodic(8). Drop your "scripts" into /usr/local/etc/periodic/daily/. The "script" may be any executable file and not just a shell script. Since this is the preferred and supported way to do this and it has the functionality you desire, unless you have further argument why the support is also needed in 999.local, I'll close up the PR in a day or two. -- "It's always funny until someone gets hurt. Then it's hilarious." Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org Responsible Changed From-To: freebsd-bugs->cjc Crist will probably close this in a few days. State Changed From-To: open->closed The preferred way to do this is to use the /usr/local/periodic/daily directory. No feedback from submitter on why this is not an adequate solution. GNATS: Enter the reason for changing this PR's status here. |