Problem with Check_DHCP

[Marc Powell]

You're absolutely correct of course =)

--
Marc

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Andreas Ericsson
> Sent: Monday, October 17, 2005 9:33 AM
> To: Nagios-users at lists.sourceforge.net
> Subject: Re: [Nagios-users] Problem with Check_DHCP
> 
> Marc Powell wrote:
> > Is check_dhcp owned by root? Just adding the sticky bit isn't
sufficient
> > if the owner (nagios presumably) doesn't have sufficient privileges.
> >
> 
> Umm... just to be anal. The sticky bit is t (octal 1000). It has no
real
> use for files anymore, but can be used to override write-permissions
on
> directories (only owner and root can delete files in directories with
> the sticky bit set). The suid bit (s, or octal 4000) is quite
different.
> 
> > --
> > Marc
> >
> >
> >>-----Original Message-----
> >>From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> >>admin at lists.sourceforge.net] On Behalf Of Fotios Magoufis
> >>Sent: Monday, October 17, 2005 9:07 AM
> >>To: Andreas Ericsson
> >>Cc: Nagios-users at lists.sourceforge.net
> >>Subject: RE: [Nagios-users] Problem with Check_DHCP
> >>
> >>Yes, I ran it as root and still no success.  If I execute the
command
> >
> > as
> >
> >>root, it works fine.
> >
> >
> >
> >>-----Original Message-----
> >>From: Andreas Ericsson [mailto:ae at op5.se]
> >>Sent: Monday, October 17, 2005 10:04 AM
> >>To: Fotios Magoufis
> >>Cc: Nagios-users at lists.sourceforge.net
> >>Subject: Re: [Nagios-users] Problem with Check_DHCP
> >>
> >>Fotios Magoufis wrote:
> >>
> >>>I've been having such a hard time getting the check_dhcp to work,
> >
> > but
> >
> >>>I still can't figure it out.  When the service runs as the nagios
> >>>user, I get the following error:
> >>>
> >>>Error: Could not bind socket to interface eth0. Check your
> >
> > privileges.
> >
> >>>I tried setting chmod +s check_dhcp, but it did not have any
> >
> > positive
> >
> >>>effect.
> >>>
> >>>Any ideas on how to fix?
> >>>
> >>
> >>I suppose you did chmod +s check_dhcp as root, right?
> >>
> >>Does it work when you run it as root from the console?
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by:
> > Power Architecture Resource Center: Free content, downloads,
> discussions,
> > and more. http://solutions.newsforge.com/ibmarch.tmpl
> > _______________________________________________
> > Nagios-users mailing list
> > Nagios-users at lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/nagios-users
> > ::: Please include Nagios version, plugin version (-v) and OS when
> reporting any issue.
> > ::: Messages without supporting info will risk being sent to
/dev/null
> >
> 
> --
> Andreas Ericsson                   andreas.ericsson at op5.se
> OP5 AB                             www.op5.se
> Tel: +46 8-230225                  Fax: +46 8-230231
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads,
discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
> ::: Please include Nagios version, plugin version (-v) and OS when
> reporting any issue.
> ::: Messages without supporting info will risk being sent to /dev/null


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null