10 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
Ryan Loudfoot	8d420adfe3	Fix some comment spacing and update version number.	2014-02-21 20:48:01 -05:00
Ryan Loudfoot	7833c20aae	I need to test more. Re-added variable for whois command. It's a variable in case we want to do something with it later, such as options for whois host.	2014-02-21 20:27:50 -05:00
Ryan Loudfoot	02b3509b56	Remove godaddy.com check for .ca domains because it didn't work anymore.	2014-02-21 20:23:32 -05:00
Ryan Loudfoot	651d6b4fa7	Add .nu thanks to Jack-Benny	2013-12-16 21:15:09 -05:00
Ryan Loudfoot	4ff31eb1d9	Remove old attempts by Ryan	2013-12-16 21:14:46 -05:00
Ryan Loudfoot	c638dbc675	Increment version number	2013-11-28 17:58:04 -05:00
Ryan Loudfoot	f1b3dac6d9	Add Jack-Benny thanks for .net fix	2013-11-28 17:57:44 -05:00
Ryan Loudfoot	5f79f0f9f3	Updated as per Vidar from shellcheck.net. ... Email received from Vidar: Hi, On line 53 in the script, getopt is used with -u: -u, --unquoted Do not quote the output. Note that whitespace and special (shell-dependent) characters can cause havoc in this mode (like they do with other getopt(1) implementations). This havoc is basically what Shellcheck is warning about. Unfortunately it's not simply a matter of quoting the variable, since the underlying problem is the way getopt is used. Instead of -u, you can use -s bash, and then eval instead of word split: args=$(getopt -o hd:w:c:P: --long help,domain:,warning:,critical:,path: -s bash -n "$PROGRAM" -- "$@") ... eval "set -- $args" This way, no havoc is caused, and no shellcheck errors are reported. Regards, Vidar	2013-11-03 18:11:48 -05:00
Ryan Loudfoot	c6471330d6	Update my (Ryan) email address and fix utils.sh check (-a deprecated, using -e now)	2013-11-02 12:19:10 -04:00
Ryan Loudfoot	8358bd7f09	One pass through spellcheck.net. Hiccup on line: set --	2013-11-02 11:14:27 -04:00