Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 3 subscribers
  • Views 1856 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

To much memory for a single process

Tmor
To much memory for a single process:
37092 kb for /usr/local/bin/fwlogwatch -D -f /var/log/kernel-20020627.gz -P n -b -m 5 -t -e -n -N -p
root      6162 15.3 28.6 37092 36156 ?       S    00:01   2:02 /usr/local/bin/fwlogwatch -D -f /var/log/kernel-20020627.gz -P n -b -m 5 -t -e -n -N -p

and now? what should i do? and why?
 
 [size="1"][ 28 June 2002, 02:33: Message edited by: Tmor ][/size]


This thread was automatically locked due to age.
Parents
  • 0
    Tmor,

    our log analyzers are using too much CPU/RAM.
    This issue will be fixed with the next up2date.

    It is a none critical issue!

    read you
    o|iver
     
     [size="1"][ 28 June 2002, 03:24: Message edited by: oliver.desch ][/size]
  • 0 in reply to oliver.desch
    err.. however the network is a critical issue or?

    To much memory for a single process:
    33960 kb for ./mdw_deamon.pl
    root       227  0.0  7.1 33960 9048 ?        S    Jun19   7:22 ./mdw_deamon.pl
  • 0 in reply to Tmor
    Tmor,

    of course if the network doesn't work anymore...

    But this error messages tells you that a process
    uses more than 30MB of RAM which is none critical!
    Our selfmonitoring is a bit too strict, since
    most of the firewalls have at least 128MB of RAM.
    It was designed too run on machines with only
    64MB, in this case it would be critically if
    a process allocates that much RAM over a longer period.

    Related conf file /etc/wfe/conf/selfmonitoring

    read you
    o|iver
Reply
  • 0 in reply to Tmor
    Tmor,

    of course if the network doesn't work anymore...

    But this error messages tells you that a process
    uses more than 30MB of RAM which is none critical!
    Our selfmonitoring is a bit too strict, since
    most of the firewalls have at least 128MB of RAM.
    It was designed too run on machines with only
    64MB, in this case it would be critically if
    a process allocates that much RAM over a longer period.

    Related conf file /etc/wfe/conf/selfmonitoring

    read you
    o|iver
Children