1. the beginning errors
2. in the code you should see if ($reason eq "mbps" ) {
but it still applie else part of if
3. why do we get numeric error :S
[root@sflow islemler]# perl deneme.plUnquoted string "paketlimiti" may clash with future reserved word at deneme.pl line 19.Unquoted string "trafiklimiti" may clash with future reserved word at deneme.pl line 23.Name "main::paketlimiti" used only once: possible typo at deneme.pl line 4.Name "main::trafiklimiti" used only once: possible typo at deneme.pl line 5.Argument "trafiklimiti" isn't numeric in numeric gt (>) at deneme.pl line 23, <$fh> line 1.paket limiti asildimbps178.20.230.51 35mbps1387666838 178.20.230.51 35 mbpspaket limiti asildipps178.20.230.51 3072pps1387666838 178.20.230.51 3072 ppspaket limiti asildimbps178.20.227.86 11mbps1387666838 178.20.227.86 11 mbpspaket limiti asildipps79.110.81.134 1536pps1387666838 79.110.81.134 1536 ppspaket limiti asildimbps178.20.230.51 32mbps1387666839 178.20.230.51 32 mbpspaket limiti asildipps178.20.230.51 3328pps1387666839 178.20.230.51 3328 pps
splain
/opt/local/bin/splain: Reading from STDIN
Unquoted string "paketlimiti" may clash with future reserved word at deneme.pl line 19.
Unquoted string "paketlimiti" may clash with future reserved word at deneme.pl
line 19 (#1)
(W reserved) You used a bareword that might someday be claimed as a
reserved word. It's best to put such a word in quotes, or capitalize it
somehow, or insert an underbar into it. You might also declare it as a
subroutine.
Name "main::paketlimiti" used only once: possible typo at deneme.pl line 4.
Name "main::paketlimiti" used only once: possible typo at deneme.pl line 4 (#2)
(W once) Typographical errors often show up as unique variable names.
If you had a good reason for having a unique name, then just mention it
again somehow to suppress the message. The our declaration is
provided for this purpose.
NOTE: This warning detects symbols that have been used only once so $c, @c,
%c, *c, &c, sub c{}, c(), and c (the filehandle or format) are considered
the same; if a program uses $c only once but also uses any of the others it
will not trigger this warning.
Argument "trafiklimiti" isn't numeric in numeric gt (>) at deneme.pl line 23, <$fh> line 1.
Argument "trafiklimiti" isn't numeric in numeric gt (>) at deneme.pl line 23,
<$fh> line 1 (#3)
(W numeric) The indicated string was fed as an argument to an operator
that expected a numeric value instead. If you're fortunate the message
will identify which operator was so unfortunate.
Did you mean to say
if ($size > $paketlimiti) {
3XLcom
ASKER
yes if ($size > $paketlimiti) { this part is not wroking correctly check the output
/opt/local/bin/splain: Reading from STDIN
Unquoted string "paketlimiti" may clash with future reserved word at deneme.pl line 19.
Unquoted string "paketlimiti" may clash with future reserved word at deneme.pl
line 19 (#1)
(W reserved) You used a bareword that might someday be claimed as a
reserved word. It's best to put such a word in quotes, or capitalize it
somehow, or insert an underbar into it. You might also declare it as a
subroutine.
Name "main::paketlimiti" used only once: possible typo at deneme.pl line 4.
Name "main::paketlimiti" used only once: possible typo at deneme.pl line 4 (#2)
(W once) Typographical errors often show up as unique variable names.
If you had a good reason for having a unique name, then just mention it
again somehow to suppress the message. The our declaration is
provided for this purpose.
NOTE: This warning detects symbols that have been used only once so $c, @c,
%c, *c, &c, sub c{}, c(), and c (the filehandle or format) are considered
the same; if a program uses $c only once but also uses any of the others it
will not trigger this warning.
Argument "trafiklimiti" isn't numeric in numeric gt (>) at deneme.pl line 23, <$fh> line 1.
Argument "trafiklimiti" isn't numeric in numeric gt (>) at deneme.pl line 23,
<$fh> line 1 (#3)
(W numeric) The indicated string was fed as an argument to an operator
that expected a numeric value instead. If you're fortunate the message
will identify which operator was so unfortunate.
Did you mean to say
if ($size > $paketlimiti) {