Author Topic: Avast4server - trial license limitations or bugs?  (Read 3695 times)

0 Members and 1 Guest are viewing this topic.

terahlop

  • Guest
Avast4server - trial license limitations or bugs?
« on: March 21, 2011, 01:57:09 PM »
Hello, we're evaluating avast4server edition with trial license. During evaluation process we noticed several things and we're not sure if those are actual bugs or just limitation of trial license:

1. Avast4server doesn't rotate logs. Avast doesn't rotate it's logs with following parameters set:
usesyslog = no
syslogfacility = LOG_DAEMON
logfile = /var/log/avast4/avastd.log
maxlogfile=5000000

ls -al
total 63356
drwxr-xr-x 2 root root 4096 Mar 17 20:01 .
drwxr-xr-x 16 root root 4096 Mar 18 04:05 ..
-rw-r--r-- 1 root root 63422137 Mar 18 13:11 avastd.log
-rw-r--r-- 1 root root 1361213 Mar 17 20:01 avastd.log.0
-rw-r--r-- 1 root root 1588 Mar 18 12:00 avastvpsreload.log
-rw-r--r-- 1 root root 490 Mar 18 12:00 avastvpsupdate.sh.log

NOTE: rotation worked after avastd restart

2. Avast flood logs with messages on establish/disconnect events:
Mar 18 13:14:46 avastd[15295]: info: new avast! inet connection with 127.0.0.1:8223
Mar 18 13:14:47 avastd[15295]: info: closing avast! connection
Mar 18 13:14:47 avastd[15295]: info: closing avast! connection
Mar 18 13:14:47 avastd[15295]: info: closing avast! connection
Mar 18 13:14:47 avastd[15295]: info: closing avast! connection
Mar 18 13:14:47 avastd[15295]: info: new avast! inet connection with 127.0.0.1:8223
Mar 18 13:14:47 avastd[15295]: info: new avast! inet connection with 127.0.0.1:8223

This happens nevertheless fact that
ignoreloginfo set to '1' in config.

Could you please clarify if those are bugs or demo license limitations? Thanks in advance!

Offline zilog

  • Avast team
  • Advanced Poster
  • *
  • Posts: 957
  • or #f0; daa; add a,#a0; adc a,#40
Re: Avast4server - trial license limitations or bugs?
« Reply #1 on: March 30, 2011, 02:36:21 PM »
Hello, we're evaluating avast4server edition with trial license. During evaluation process we noticed several things and we're not sure if those are actual bugs or just limitation of trial license:

1. Avast4server doesn't rotate logs. Avast doesn't rotate it's logs with following parameters set:
usesyslog = no
syslogfacility = LOG_DAEMON
logfile = /var/log/avast4/avastd.log
maxlogfile=5000000

ls -al
total 63356
drwxr-xr-x 2 root root 4096 Mar 17 20:01 .
drwxr-xr-x 16 root root 4096 Mar 18 04:05 ..
-rw-r--r-- 1 root root 63422137 Mar 18 13:11 avastd.log
-rw-r--r-- 1 root root 1361213 Mar 17 20:01 avastd.log.0
-rw-r--r-- 1 root root 1588 Mar 18 12:00 avastvpsreload.log
-rw-r--r-- 1 root root 490 Mar 18 12:00 avastvpsupdate.sh.log

NOTE: rotation worked after avastd restart

2. Avast flood logs with messages on establish/disconnect events:
Mar 18 13:14:46 avastd[15295]: info: new avast! inet connection with 127.0.0.1:8223
Mar 18 13:14:47 avastd[15295]: info: closing avast! connection
Mar 18 13:14:47 avastd[15295]: info: closing avast! connection
Mar 18 13:14:47 avastd[15295]: info: closing avast! connection
Mar 18 13:14:47 avastd[15295]: info: closing avast! connection
Mar 18 13:14:47 avastd[15295]: info: new avast! inet connection with 127.0.0.1:8223
Mar 18 13:14:47 avastd[15295]: info: new avast! inet connection with 127.0.0.1:8223

This happens nevertheless fact that
ignoreloginfo set to '1' in config.

Could you please clarify if those are bugs or demo license limitations? Thanks in advance!

Hallo,
avastd doesn't rotate logs (more specifically, isn't prepared to have its log rotated in background, AFAIK, w/o restart).
The second one loks like a flaw in the configuration file logic, so i'll forward this to my colleague for fix. Thanks for the report, i'll post a note here when we'll have fixed version re-built.

regards,
pc
May's Law: Software efficiency halves every 18 months, compensating Moore's Law. (David May, INMOS)