You can always use the daemon-control-dist script (w/ a few minor mods 
documented at the top) in place of the FC rpm version.  Simply edit it and 
save it as /etc/init.d/denyhosts and you should be in business.  I've used 
this script for years with FC 5,6,7,8 and RHEL 4.

Regards,

Phil


On Tue, 1 Jul 2008, James Carman wrote:

> On Tue, Jul 1, 2008 at 11:49 AM, Phil Schwartz
> <[EMAIL PROTECTED]> wrote:
>>
>> Does "stop" then "start" work properly (rather than "condrestart")?
>
> No, that's the issue.  Using the "service" stuff doesn't work at all.
> The daemon doesn't start properly.  There is one difference in the log
> files between manual start and service start.  At the end of the log
> file when you start it manually, you'll see:
>
> 2008-07-01 13:24:55,080 - denyhosts   : INFO     launching DenyHosts
> daemon (version 2.6)...
> 2008-07-01 13:24:55,085 - denyhosts   : INFO     DenyHosts daemon is
> now running, pid: 31554
> 2008-07-01 13:24:55,086 - denyhosts   : INFO     send daemon process a
> TERM signal to terminate cleanly
> 2008-07-01 13:24:55,087 - denyhosts   : INFO       eg.  kill -TERM 31554
> 2008-07-01 13:24:55,097 - denyhosts   : INFO     monitoring log: 
> /var/log/secure
> 2008-07-01 13:24:55,098 - denyhosts   : INFO     sync_time: 3600
> 2008-07-01 13:24:55,098 - denyhosts   : INFO     daemon_purge:      3600
> 2008-07-01 13:24:55,098 - denyhosts   : INFO     daemon_sleep:      30
> 2008-07-01 13:24:55,099 - denyhosts   : INFO     purge_sleep_ratio: 120
> 2008-07-01 13:24:55,099 - denyhosts   : INFO     sync_time:      : 3600
> 2008-07-01 13:24:55,099 - denyhosts   : INFO     sync_sleep_ratio: 120
>
> However, if you use the service start method, you only see:
>
> 2008-07-01 13:26:42,847 - denyhosts   : INFO     launching DenyHosts
> daemon (version 2.6)...
> 2008-07-01 13:26:42,855 - denyhosts   : INFO     DenyHosts daemon is
> now running, pid: 31597
> 2008-07-01 13:26:42,857 - denyhosts   : INFO     send daemon process a
> TERM signal to terminate cleanly
> 2008-07-01 13:26:42,857 - denyhosts   : INFO       eg.  kill -TERM 31597
>
> So, you don't see the sync stuff.  Perhaps that's a clue about what is
> failing?  I don't know python or I'd manually edit the script to try
> to make it spit out more information.  If it were written in Java or
> Ruby, I'd be better suited to help. :)
>
>>
>> Also, what is the value of LOCK_FILE in denyhosts.cfg?  It should match the
>> one in /etc/init.d/denyhosts.
>
> In /etc/denyhosts.conf:
>
> LOCK_FILE=/var/lock/subsys/denyhosts
>
> In /etc/init.d/denyhosts:
>
> LOCKFILE=/var/lock/subsys/denyhosts
>
> -------------------------------------------------------------------------
> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
> Studies have shown that voting for your favorite open source project,
> along with a healthy diet, reduces your potential for chronic lameness
> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
> _______________________________________________
> Denyhosts-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/denyhosts-user
>

-- 
Regards,

Phil Schwartz
- http://www.phil-schwartz.com

Open Source Projects:
- DenyHosts: http://www.denyhosts.net
- Kodos: http://kodos.sourceforge.net
- ReleaseForge: http://releaseforge.sourceforge.net
- Scratchy: http://scratchy.sourceforge.net
- FAQtor: http://faqtor.sourceforge.net

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Denyhosts-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/denyhosts-user

Reply via email to