[Nagiosplug-devel] [OT] Nagios Plugins Used by Up.time
Voon, Ton
Ton.Voon at egg.com
Wed Mar 10 03:25:09 CET 2004
AJ,
Thanks for your post. I've been reading a lot up on the GPL recently, mainly
due to the SCO case, and this looks like a violation of the GPL. As you are
in possession of their code, can you take a look at
http://www.gnu.org/licenses/gpl-violation.html and I will chase up.
My understanding is that they would be allowed to redistribute the code if
they retained the GPL and the copyright of the original source.
Ton
-----Original Message-----
From: AJ McKee [mailto:aj.mckee at nmtbmedia.com]
Sent: Wednesday, March 10, 2004 4:20 AM
To: nagiosplug-devel at lists.sourceforge.net
Subject: [Nagiosplug-devel] [OT] Nagios Plugins Used by Up.time
Hi All,
Sorry about the OT post, but I thought it should be brought to your
attention if it already has not. I downloaded a demo monitoring app the
other day called up.time from Uptime Software (www.uptimesoftware.com),
to give it a try and see how it compares with Nagios. Well the admin
interface is beautiful. A lot of effort there. However when I dug into
the file system I found some strange results.
To cut to the chase there is a directory called libexec in
/opt/SPYNuptm/ and its contents are similar if not identical to that of
nagios. But all the plugins have been modified not to show the gpl
licence info that is there normally. So I was wondering if this was
known to nagios plugin developers, and if so sorry for going through
something which is already known. If not, bummer is this another example
of a company ripping off from the OSS community? I am in possession of a
document they publish (PDF if anyone wants it off list) which compares
their product to Nagios (Which I love BTW :), which to me seems
inaccurate to a great extent.
So basically I was wondering what was everyone's thoughts etc on this? I
have included a dir listing and the output from their check_mysql
command for reference.
Cheers in advance,
Yours
AJ
Have you see this elsewhere before :)
/opt/SPYNuptm/libexec
total 9340
-rwx--x--x 1 uptime 87399 Feb 26 02:45 check_by_ssh
-rwx--x--x 1 uptime 569 Feb 26 02:45 check_chk4
-rwx--x--x 1 uptime 1272 Feb 26 02:45 check_dhcp
-rwx--x--x 1 uptime 89113 Feb 26 02:45 check_dns
-rwxr-xr-x 1 uptime 2637 Feb 26 02:45 check_fscap
-rwx--x--x 1 uptime 90633 Feb 26 02:45 check_ftp
-rwx--x--x 1 uptime 159582 Feb 26 02:45 check_http
-rwx--x--x 1 uptime 90477 Feb 26 02:45 check_imap
-rwx--x--x 1 uptime 95427 Feb 26 02:45 check_ldap
-rwx--x--x 1 uptime 238700 Feb 26 02:45 check_mysql
-rwxr-xr-x 1 uptime 1033 Feb 26 02:45 check_nfs
-rwx--x--x 1 uptime 92464 Feb 26 02:45 check_nntp
-rwx--x--x 1 uptime 831 Feb 26 02:45 check_ntsvc
-rwx--x--x 1 uptime 459 Feb 26 02:45 check_oracle
-rwxr-xr-x 1 uptime 27423 Feb 26 02:45 check_ora_performance
-rwx--x--x 1 uptime 1715 Feb 26 02:45 check_ora_tablespace
-rwxr-xr-x 1 uptime 1094127 Feb 26 02:45 check_perf
-rwx--x--x 1 uptime 91168 Feb 26 02:45 check_ping
-rwx--x--x 1 uptime 90752 Feb 26 02:45 check_pop
-rwxr-xr-x 1 uptime 1852 Feb 26 02:45 check_processcount
-rwx--x--x 1 uptime 3082 Feb 26 02:45 check_smb
-rwx--x--x 1 uptime 91043 Feb 26 02:45 check_smtp
-rwx--x--x 1 uptime 102912 Feb 26 02:45 check_snmp
-rwx--x--x 1 uptime 89644 Feb 26 02:45 check_ssh
-rwx--x--x 1 uptime 96106 Feb 26 02:45 check_tcp
-rwx--x--x 1 uptime 90609 Feb 26 02:45 check_udp
-rwxr-xr-x 1 uptime 267 Feb 26 02:45 check_uptime
-rwx--x--x 1 uptime 1746 Feb 26 02:45 check_yp
-rws--x--x 1 uptime 1216515 Feb 26 02:45 dhclient
-rwx--x--x 1 uptime 4774504 Feb 26 02:45 dhclient_solaris
-rwx--x--x 1 uptime 576671 Feb 26 02:45 smbclient
-rwx--x--x 1 uptime 1292 Feb 26 02:45 solaris
-rwx--x--x 1 uptime 79910 Feb 26 02:45 urlize
Or better
./check_mysql --help
check_mysql (servmon-plugins 3.0.1) 1.4
Usage: check_mysql [-d database] [-H host] [-P port] [-u user] [-p
password]
check_mysql --help
check_mysql --version
There are no required arguments. By default, the local database with
a server listening on MySQL standard port 3306 will be checked
Options:
-d, --database=STRING
Check database with indicated name
-H, --hostname=STRING or IPADDRESS
Check server on the indicated host
-P, --port=INTEGER
Make connection on the indicated port
-u, --username=STRING
Connect using the indicated username
-p, --password=STRING
Use the indicated password to authenticate the connection
==> IMPORTANT: THIS FORM OF AUTHENTICATION IS NOT SECURE!!! <==
Your clear-text password will be visible as a process table entry
-h, --help
Print detailed help screen
-V, --version
Print version information
email support at uptimesoftware.com
This private and confidential e-mail has been sent to you by Egg.
The Egg group of companies includes Egg Banking plc
(registered no. 2999842), Egg Financial Products Ltd (registered
no. 3319027) and Egg Investments Ltd (registered no. 3403963) which
is authorised and regulated by the Financial Services Authority. Egg
Investments Ltd. is entered in the FSA register under number 190518.
Registered in England and Wales. Registered offices: 1 Waterhouse
Square, 138-142 Holborn, London EC1N 2NA.
If you are not the intended recipient of this e-mail and have received
it in error, please notify the sender by replying with 'received in
error' as the subject and then delete it from your mailbox.
More information about the Devel
mailing list