Bug 40086
| Summary: | Crontab for sysstat not exiting after backgrounding sadc | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Christopher Penney <penney> |
| Component: | crontabs | Assignee: | Crutcher Dunnavant <crutcher> |
| Status: | CLOSED RAWHIDE | QA Contact: | David Lawrence <dkl> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.1 | Keywords: | FutureFeature |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2001-05-10 15:15:58 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
this was truly a sysstat problem, and has been addressed in the rawhide sysstat package. |
From Bugzilla Helper: User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0smp i686) Description of problem: When run-parts runs /etc/cron.hourly/sysstat something isn't getting backgrounded properly and I end up with processes that are waiting on the exit of something (I have not explored it). How reproducible: Always Steps to Reproduce: 1. Do an install of RedHat 7.1 (sysstat & crontabs must be installed). Specifically, by kickstart install has the following backages: @ Base @ Network Server @ Development @ Utilities @ Emacs psacct wu-ftpd ntp tcpdump 2. Watch the process list on the hour (when cron.hourly runs next)W Actual Results: You will see the following in a 'ps' list: root 2107 0.0 0.0 1436 476 ? S 11:01 0:00 CROND root 2108 0.0 0.0 1920 908 ? S 11:01 0:00 /bin/bash /usr/bin/run-parts /etc/cron.hourly root 2110 0.0 0.0 1656 552 ? S 11:01 0:00 awk -v progname=/etc/cron.hourly/sysstat progname {????? print progname ":\n"????? progname="";???? }???? { print; } root 2111 0.0 0.0 1904 880 ? S 11:01 0:00 /bin/sh /usr/lib/sa/sa1 600 6 root 2113 0.0 0.0 1352 512 ? S 11:01 0:00 /usr/lib/sa/sadc 600 6 /var/log/sa/sa10 Expected Results: I expect to only see the sadc process, though the way /usr/lib/sa/sa1 is written I also expect to see the sa1 script waiting for sadc to exit (that should really be fixed as well as there isn't much need in the script waiting for sadc to exit). Additional info: Not a severe problem, but it would be nice to see this cleaned up.