Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ossec-control exit status is nonzero when maild is disabled by config #960

Closed
packetizeme opened this issue Sep 29, 2016 · 1 comment
Closed

ossec-control exit status is nonzero when maild is disabled by config #960

packetizeme opened this issue Sep 29, 2016 · 1 comment
Labels
bug needs-volunteers

Comments

@packetizeme
Copy link

If <email_notification>no</email_notification> is specified in ossec.conf, ossec-maild will not be run when starting ossec. Checking service status via ossec-control status will report this as not running and then return 1.

It seems that the better behavior would be to validate that the service should be running (check ossec.conf) and compare current vs desired state when determining return value, rather than simply expecting all services to be running.
@marcRBD
Copy link

marcRBD commented Oct 13, 2016

hi
i confirm that on debian 8.6 ossec-maild is not running after <email_notification>no</email_notification>

ddpbsd added a commit to ddpbsd/ossec-hids that referenced this issue Oct 13, 2016
@ddpbsd
Hoepfully fixes issue ossec#960 by not trying to start ossec-maild when
89e7f5e 
it's been disabled.
@ddpbsd ddpbsd mentioned this issue Oct 13, 2016
Merged
@ddpbsd ddpbsd closed this as completed Oct 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug needs-volunteers
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@packetizeme @ddpbsd @marcRBD