Hi all,
I am using Centos 5.8. And the problem is if any other (Win/ Linux) is giving the same static IP given to this system, they are not getting any conflict msg, and i found a package IPwatchD which does this same thing. But i am not able to install IPwatchD package on my Centos 5.8 system.

The problem is, though i completed the installation procedure without any problem, but when running the service i am getting the error as here

[oracle@orahostfzr ~]$ sudo /etc/init.d/ipwatchd start
/etc/init.d/ipwatchd: line 34: /lib/init/vars.sh: No such file or directory

So if any one has the solution for this error, or a any other package which can give notification on second PC who are trying to use IP assigned to this PC.
Thanks for the help

Find out where it resides by checking if it's part of the package:

Their is no o/p for the command, you mentioned.

[oracle@orahostfzr ~]$ rpm -ql $(rpm -qf /etc/init.d/ipwatchd)|grep vars.sh
[oracle@orahostfzr ~]$

Also, i have gone through the Quick start page http://ipwatchd.sourceforge.net/quick_start, and after giving command
/usr/sbin/ipwatchd -c /etc/ipwatchd.conf

the service has started, but i am still not getting any conflict msg on other PCs.

Then either my RPM/grep-fu sucks or the file was never included. Assert the latter as apparently /lib/init/vars.sh is a Debian thing. So just comment that line out in your init script and move on.


That's a whole different question and we don't know what /etc/ipwatchd.conf contains and if there actually were any conflicts in the time frame you ran ipwatchd.

first , /lib/init/vars.sh is not an IPwatchD file, and so it might have not been listed. second, i have tried commenting out this line, but then after, if i restart the application, i am getting other errors. so i gues from the docs of IPwatchD,
/usr/sbin/ipwatchd -c /etc/ipwatchd.conf
is the right way to start the application, only thing is why am i not getting the conflict messages, have any body used the packages, and can you pl comment how it works.

As I already said the file was never included because it only applies to Debian.


Saying "other errors" doesn't make sense, posting them does.


If you don't post your /etc/ipwatchd.conf we don't know how you run it and if you don't have anything on the side to verify (Arphound, Arpwatch) you don't know if there actually were any conflicts when you ran ipwatchd.