#7 Uninitialised Variable notifications when using admin CLI

[Damian Brasher]

Uninitialised Variable notifications when using admin CLI -diaser. All of these can be safely ignored.

- These occur because diaser expects diaser.conf on the working directory - the conf does not need to exist in the local directory.

[dbrasher@localhost diaser]$ ./diaser ../diaser-conf010412 --modify
Use of uninitialized value $opt in string eq at /usr/share/perl5/Getopt/Long.pm line 494.
Use of uninitialized value $opt in pattern match (m//) at /usr/share/perl5/Getopt/Long.pm line 902.

- After some Perl:Critic recommendation changes these occur:

Use of uninitialized value in <HANDLE> at ./diaser line 3841.
Can't open : No such file or directory at ./diaser line 3841.
Use of uninitialized value $response in scalar chomp at ./diaser line 3842.
Use of uninitialized value $response in pattern match (m//) at ./diaser line 3843.
Use of uninitialized value $response in pattern match (m//) at ./diaser line 3843

They need troubleshooting - the cause is probably due to improper lexical scoping. None of these are known to cause operation errors.