[SOLVED] msec.log

[nigelc]

Hi,
I am getting several pages in msec.log :

Code: Select all

2013-05-28 09:01:02,134 INFO: Forbidding the X server to listen to tcp connection
2013-05-28 09:01:02,141 INFO: Enabling log on console
2013-05-28 09:01:02,153 INFO: Password history not supported with pam_tcb.
2013-05-28 09:01:02,166 INFO: No changes in system files
2013-05-28 10:01:01,426 INFO: Forbidding the X server to listen to tcp connection
2013-05-28 10:01:01,434 INFO: Enabling log on console
2013-05-28 10:01:01,445 INFO: Password history not supported with pam_tcb.
2013-05-28 10:01:01,459 INFO: No changes in system files
2013-05-28 11:01:01,742 INFO: Forbidding the X server to listen to tcp connection
2013-05-28 11:01:01,750 INFO: Enabling log on console
2013-05-28 11:01:01,762 INFO: Password history not supported with pam_tcb.
2013-05-28 11:01:01,779 INFO: No changes in system files
2013-05-28 12:01:03,019 INFO: Forbidding the X server to listen to tcp connection
2013-05-28 12:01:03,039 INFO: Enabling log on console
2013-05-28 12:01:03,051 INFO: Password history not supported with pam_tcb.
2013-05-28 12:01:03,068 INFO: No changes in system files
2013-05-28 13:01:02,429 INFO: Forbidding the X server to listen to tcp connection
2013-05-28 13:01:02,489 INFO: Enabling log on console
2013-05-28 13:01:02,514 INFO: Password history not supported with pam_tcb.
2013-05-28 13:01:02,530 INFO: No changes in system files


Is this god or bad?

[doktor5000]

Well, it's probably not about god

Which part are you interested in? Normally most Display Managers don't allow for tcp connections straight through, so e.g. ssh X-Forwarding needs to be explicitly enabled. And it's just an INFO ...

[nigelc]

Is an INFO not an error?

[doktor5000]

No, because then the tag would be ERROR or WARNING ...
Maybe you should also pay attention to a golden rule: Don't care for an error message, unless there's a real error related to it.

Anyways, what's your particular problem with those entries, as already asked?