Bug 27421 - Enhancement to innd initscript
Summary: Enhancement to innd initscript
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: inn
Version: 7.1
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Florian La Roche
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-02-13 17:38 UTC by Need Real Name
Modified: 2007-03-27 03:40 UTC (History)
0 users

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-02-13 17:38:43 UTC
Embargoed:


Attachments (Terms of Use)

Description Need Real Name 2001-02-13 17:38:34 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)


Here is an enhancement to the innd initscript that will allow it to 
continue to work if the user has relocated their INN history database 
and/or news spool from the RedHat default location.

Reproducible: Always
Steps to Reproduce:
1. Edit inn.conf to relocate PATHHISTORY.
2. Try to start INN via the initscript.
	

Actual Results:  Get an error "please run makehistory or makedbz before 
running INN."

Expected Results:  Should have started INN.

*** innd.orig Sat Feb 10 12:00:28 2001
--- innd Sat Feb 10 12:03:18 2001
***************
*** 19,26 ****
  # Check that networking is up.
  [ ${NETWORKING} = "no" ] && exit 0
  [ -d /etc/news ] || exit 0
! [ -d /var/spool/news ] || exit 0
! [ -f /var/lib/news/history -a -f /var/lib/news/history.hash ] || {
  echo $"Please run makehistory and/or makedbz before starting innd." >&2
  exit 1
  }
--- 19,28 ----
  # Check that networking is up.
  [ ${NETWORKING} = "no" ] && exit 0
  [ -d /etc/news ] || exit 0
! [ -f /etc/news/inn.conf ] || exit 0
! . /usr/lib/innshellvars
! [ -d $SPOOLBASE ] || exit 0
! [ -f $HISTORY -a -f $HISTORY.hash ] || {
  echo $"Please run makehistory and/or makedbz before starting innd." >&2
  exit 1
  }

Comment 1 Florian La Roche 2001-02-14 10:37:24 UTC
Good change, applied to the next rpm.



Note You need to log in before you can comment on or make changes to this bug.