Bug 630484

Summary:	inn cron jobs do not match binary installation locations
Product:	[Fedora] Fedora	Reporter:	Peter Greenwood <peterg>
Component:	inn	Assignee:	Nikola Pajkovsky <npajkovs>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	13	CC:	dhoward, jochen, npajkovs, ovasik
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-09-13 09:39:53 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:

Description Peter Greenwood 2010-09-05 21:45:35 UTC

Description of problem:

File /etc/cron.hourly/inn-cron-nntpsend contains the line:
runuser -m news -c "unset LANG; unset LC_COLLATE; /usr/lib/news/bin/nntpsend"

but nntpsend is installed at /usr/libexec/news/nntpsend

Similarly inn-cron-rnews contains:
runuser -m news -c 'unset LANG; unset LC_COLLATE; /usr/lib/news/bin/rnews -U'

but rnews is at /usr/libexec/news/rnews


Version-Release number of selected component (if applicable):
inn-2.5.1-3.fc13.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Install and run inn
2. Check email for root, observe emails from cron indicating "no such file or directory"

Actual results:
 Hourly emails from cron as follows:

"/etc/cron.hourly/inn-cron-nntpsend:

bash: /usr/lib/news/bin/nntpsend: No such file or directory
/etc/cron.hourly/inn-cron-rnews:

bash: /usr/lib/news/bin/rnews: No such file or directory"

Expected results:
No such emails

Additional info:

Comment 1 Peter Greenwood 2010-09-05 21:54:33 UTC

Also applies to /etc/cron.daily/inn-cron-expire where last line should read:
runuser -m news -c "unset LANG; unset LC_COLLATE; /usr/libexec/news/news.daily delayrm"

Comment 2 Nikola Pajkovsky 2010-09-06 09:09:19 UTC

Thanks for your report. Hmm, fix is still not in stable system. I fixed it in Wed Jun 2 2010. Update your inn from update-testing repo.

Comment 3 Nikola Pajkovsky 2010-09-13 09:39:53 UTC


*** This bug has been marked as a duplicate of bug 596580 ***