Menu
▾
▴
evlog-developers — For the discussion of Linux Event Logging and announcments.
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(31) |
Nov
(34) |
Dec
(20) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(9) |
Feb
(24) |
Mar
(17) |
Apr
(17) |
May
|
Jun
(3) |
Jul
(4) |
Aug
(5) |
Sep
(53) |
Oct
(5) |
Nov
(3) |
Dec
(14) |
| 2003 |
Jan
(58) |
Feb
(15) |
Mar
(18) |
Apr
(19) |
May
(7) |
Jun
(1) |
Jul
(4) |
Aug
(1) |
Sep
|
Oct
(5) |
Nov
(6) |
Dec
(7) |
| 2004 |
Jan
(1) |
Feb
|
Mar
(2) |
Apr
(14) |
May
(6) |
Jun
(8) |
Jul
(3) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
(5) |
| 2005 |
Jan
(7) |
Feb
(5) |
Mar
(4) |
Apr
|
May
(2) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
| 2006 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2007 |
Jan
(10) |
Feb
(1) |
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
|
From: James K. <ken...@us...> - 2007-10-25 22:34:36
|
nun...@er... wrote on 10/25/2007 02:23:08 AM: > Hi, > I would like to add evlog on Linux running on MPC8548E. Is there any > support for this processor? > Thanks, > Nunzio I'm not familiar with that chip. It looks like it might use the ppc64 instruction set. (What does "uname -a" on that system report?) Evlog supports both ppc32 and ppc64. Jim Keniston IBM Linux Technology Center |
|
From: Nunzio F. <nun...@er...> - 2007-10-25 09:24:01
|
Hi, I would like to add evlog on Linux running on MPC8548E. Is there any support for this processor? Thanks, Nunzio=20 |
|
From: Tong L. <ton...@gm...> - 2007-04-13 03:54:52
|
Many thanks! Jim. I will fix it. Regards Tong On 4/11/07, James Keniston <ken...@us...> wrote: > > evl...@li... wrote on 04/11/2007 > 09:07:51 AM: > > > Hello, > > > > Thanks for Jim's response in terms of evlog compiling issue. > > Now most functions of evlog work flawlessly. > > > > Here is an error I found after enabling udp/tcp log remote > > forwarding function. > > Uid value in all the forwarded log messages is overwritten by Severity > value: > > ON central log server Node1: > > > > recid=5, size=73, format=STRING, event_type=0x109, facility=LOCAL3, > > severity=CRIT, uid=CRIT, gid=root, pid=26035, pgrp=26035, > > time=Tue 10 Apr 2007 05:01:02 PM PDT, flags=0x0, thread=0xf7fc46c0, > > processor=0, host=node2 > > try log forwarding function > > > > > > I have tried, the same issue also exists on evlog rpms from evlog > website. > > > > Which module should I modify to correct this problem? > > The problem appears to be in the POSIX_LOG_ENTRY_UID case of > posix_log_memtostr() > in posix1.c. If the host is a remote host, it should encode the numeric > value of > the uid (as when getpwuid[_r] fails to find a match). Instead, it encodes > nothing, > and what was in the buffer before (i.e., "CRIT") remains. > > BTW, seems like POSIX_LOG_ENTRY_GID should be handled similarly. > > > After I fixed it, I can post the patch here. > > That'd be great. Thanks. > Jim > > > > > Thanks. > > > > ~ > > Tong > > > ------------------------------------------------------------------------- > ... > > _______________________________________________ > > evlog-developers mailing list > > evl...@li... > > https://lists.sourceforge.net/lists/listinfo/evlog-developers > > |
|
From: James K. <ken...@us...> - 2007-04-11 18:01:32
|
evl...@li... wrote on 04/11/2007 09:07:51 AM: > Hello, > > Thanks for Jim's response in terms of evlog compiling issue. > Now most functions of evlog work flawlessly. > > Here is an error I found after enabling udp/tcp log remote > forwarding function. > Uid value in all the forwarded log messages is overwritten by Severity value: > ON central log server Node1: > > recid=5, size=73, format=STRING, event_type=0x109, facility=LOCAL3, > severity=CRIT, uid=CRIT, gid=root, pid=26035, pgrp=26035, > time=Tue 10 Apr 2007 05:01:02 PM PDT, flags=0x0, thread=0xf7fc46c0, > processor=0, host=node2 > try log forwarding function > > > I have tried, the same issue also exists on evlog rpms from evlog website. > > Which module should I modify to correct this problem? The problem appears to be in the POSIX_LOG_ENTRY_UID case of posix_log_memtostr() in posix1.c. If the host is a remote host, it should encode the numeric value of the uid (as when getpwuid[_r] fails to find a match). Instead, it encodes nothing, and what was in the buffer before (i.e., "CRIT") remains. BTW, seems like POSIX_LOG_ENTRY_GID should be handled similarly. > After I fixed it, I can post the patch here. That'd be great. Thanks. Jim > > Thanks. > > ~ > Tong > ------------------------------------------------------------------------- ... > _______________________________________________ > evlog-developers mailing list > evl...@li... > https://lists.sourceforge.net/lists/listinfo/evlog-developers |
|
From: Tong L. <ton...@gm...> - 2007-04-11 16:07:54
|
Hello, Thanks for Jim's response in terms of evlog compiling issue. Now most functions of evlog work flawlessly. Here is an error I found after enabling udp/tcp log remote forwarding function. Uid value in all the forwarded log messages is overwritten by Severity value: ON central log server Node1: ** recid=5, size=73, format=STRING, event_type=0x109, facility=LOCAL3, severity=CRIT, uid=CRIT, gid=root, pid=26035, pgrp=26035, time=Tue 10 Apr 2007 05:01:02 PM PDT, flags=0x0, thread=0xf7fc46c0, processor=0, host=node2 try log forwarding function ** I have tried, the same issue also exists on evlog rpms from evlog website. Which module should I modify to correct this problem? After I fixed it, I can post the patch here. ** Thanks. ~ Tong |
|
From: James L. <jam...@gm...> - 2007-02-15 07:28:25
|
SSBoYXZlIHJlc29sb3ZlZCBpdA0KLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLSANCkZyb206 ICJKYW1lcyBLZW5pc3RvbiIgPGtlbmlzdG9qQHVzLmlibS5jb20+DQpUbzogIkphbWVzIExpIiA8 amFtZXNsLnlpbWxAZ21haWwuY29tPg0KQ2M6IDxldmxvZy1kZXZlbG9wZXJzQGxpc3RzLnNvdXJj ZWZvcmdlLm5ldD47IDxldmxvZy1kZXZlbG9wZXJzLWJvdW5jZXNAbGlzdHMuc291cmNlZm9yZ2Uu bmV0Pg0KU2VudDogVHVlc2RheSwgSmFudWFyeSAzMCwgMjAwNyA0OjUxIEFNDQpTdWJqZWN0OiBS ZTogW2V2bG9nLWRldl0gY2FuIG5vdCBjb21waWxlIGV2bG9nIG9uIGdjYyA0DQoNCg0KPiBldmxv Zy1kZXZlbG9wZXJzLWJvdW5jZXNAbGlzdHMuc291cmNlZm9yZ2UubmV0IHdyb3RlIG9uIDAxLzE5 LzIwMDcgMDE6MDc6NDUNCj4gQU06DQo+IA0KPj4gSGkgOg0KPj4gICAgIEkgY2FuIG5vdCBjb21w aWxlIGV2bG9nIDEuNi4xIGluIFNMRVMxMCBvciBSSEVMNCBVNC4NCj4gDQo+IFNvcnJ5IGZvciBu b3QgcmVzcG9uZGluZyBlYXJsaWVyLiAgU2VlIGJlbG93Lg0KPiANCj4+DQo+PiBIZXJlIGFyZSB0 aGUgZXJyb3I6DQo+Pg0KPj4gMS4NCj4+IHN5c2xvZ2F0VGVzdC5jOiBJbiBmdW5jdGlvbiChrmdh bWWhrzoNCj4+IHN5c2xvZ2F0VGVzdC5jOjE0OiB3YXJuaW5nOiBpbml0aWFsaXphdGlvbiBtYWtl cyBpbnRlZ2VyIGZyb20NCj4+IHBvaW50ZXIgd2l0aG91dCBhIGNhc3QNCj4+IHN5c2xvZ2F0VGVz dC5jOjE0OiBlcnJvcjogaW5pdGlhbGl6ZXIgZWxlbWVudCBpcyBub3QgY29tcHV0YWJsZSBhdCBs b2FkDQo+IHRpbWUNCj4+IHN5c2xvZ2F0VGVzdC5jOjE0OiBlcnJvcjogKG5lYXIgaW5pdGlhbGl6 YXRpb24gZm9yIKGuX19fLnBvcy5mdW5jdGlvblswXaGvKQ0KPj4gc3lzbG9nYXRUZXN0LmM6MTg6 IHdhcm5pbmc6IGluaXRpYWxpemF0aW9uIG1ha2VzIGludGVnZXIgZnJvbQ0KPj4gcG9pbnRlciB3 aXRob3V0IGEgY2FzdA0KPj4gc3lzbG9nYXRUZXN0LmM6MTg6IGVycm9yOiBpbml0aWFsaXplciBl bGVtZW50IGlzIG5vdCBjb21wdXRhYmxlIGF0IGxvYWQNCj4gdGltZQ0KPj4gc3lzbG9nYXRUZXN0 LmM6MTg6IGVycm9yOiAobmVhciBpbml0aWFsaXphdGlvbiBmb3Igoa5fX18ucG9zLmZ1bmN0aW9u WzBdoa8pDQo+IA0KPiBBcyBJIG1lbnRpb25lZCBpbiB0b2RheSdzIG1haWwgdG8gVG9uZyBMaXUs IEkgdGhpbmsgdGhpcyBoYXMgdG8gZG8gd2l0aCBhDQo+IGNoYW5nZSBpbiBnY2MgdGhhdCBtYWtl cyBzeXNsb2dhdCdzIHVzZSBvZiBfX0ZVTkNUSU9OX18gbm8gbG9uZ2VyDQo+IHN1cHBvcnRlZDsg YW5kIGEgY293b3JrZXIgd2lsbCBsb29rIGF0IHRoaXMgaW4gYSB3ZWVrIG9yIHNvLg0KPiANCnJl cGxhY2UgX19GVU5DVElPTl9fIGJ5ICIgIg0KPj4NCj4+DQo+PiAyLiBObyBQVEhSRUFEX1RIUkVB U19NQVggZGVmaW5lZCBpbiAvdXNyL2luY2x1ZGUvbGltaXRzLmgNCj4gDQo+IFlvdSBtZWFuIFBU SFJFQURfVEhSRUFEU19NQVggLS0gYnV0IGl0J3Mgc3RpbGwgdW5kZWZpbmVkIGluIGF0IGxlYXN0 IHNvbWUNCj4gcmVjZW50IGltcGxlbWVudGF0aW9ucyBvZiBsaW1pdHMuaC4gIERvZXMgX1BPU0lY X1RIUkVBRF9USFJFQURTX01BWCB3b3JrDQo+IGZvciB5b3U/DQo+IA0KX1BPU0lYX1RIUkVBRF9U SFJFQURTX01BWCBkb2VzIHdvcmsNCj4+DQo+PiAzLiBleHRlcm4gdG1wbF9hcmNoX3R5cGVfaW5m b190IF9ldmxUbXBsQXJjaFR5cGVJbmZvW11bXTsNCj4+IGlzIGludmFsaWQgaW4gZ2NjIDQuMS4w DQo+IA0KPiBUcnkgcmVwbGFjaW5nIFtdW10gd2l0aCBbOF1bMjRdIGluIHRoZSB2YXJpb3VzIHBs YWNlcyBfZXZsVG1wbEFyY2hUeXBlSW5mbw0KPiBpcyBkZWNsYXJlZCBleHRlcm4uDQoNCkl0IHNo b3VsZCBiZSANCmV4dGVybiB0bXBsX2FyY2hfdHlwZV9pbmZvX3QgX2V2bFRtcGxBcmNoVHlwZUlu Zm9bXVsyNF07DQoNCg0KDQoNCj4gDQo+IEppbSBLZW5pc3Rvbg0KPiBJQk0gTFRDLVJBUw== |
|
From: James K. <ken...@us...> - 2007-01-29 21:01:35
|
ZXZsb2ctZGV2ZWxvcGVycy1ib3VuY2VzQGxpc3RzLnNvdXJjZWZvcmdlLm5ldCB3cm90ZSBvbiAw MS8xOS8yMDA3IDAxOjA3OjQ1DQpBTToNCg0KPiBIaSA6DQo+ICAgICBJIGNhbiBub3QgY29tcGls ZSBldmxvZyAxLjYuMSBpbiBTTEVTMTAgb3IgUkhFTDQgVTQuDQoNClNvcnJ5IGZvciBub3QgcmVz cG9uZGluZyBlYXJsaWVyLiAgU2VlIGJlbG93Lg0KDQo+DQo+IEhlcmUgYXJlIHRoZSBlcnJvcjoN Cj4NCj4gMS4NCj4gc3lzbG9nYXRUZXN0LmM6IEluIGZ1bmN0aW9uIKGuZ2FtZaGvOg0KPiBzeXNs b2dhdFRlc3QuYzoxNDogd2FybmluZzogaW5pdGlhbGl6YXRpb24gbWFrZXMgaW50ZWdlciBmcm9t DQo+IHBvaW50ZXIgd2l0aG91dCBhIGNhc3QNCj4gc3lzbG9nYXRUZXN0LmM6MTQ6IGVycm9yOiBp bml0aWFsaXplciBlbGVtZW50IGlzIG5vdCBjb21wdXRhYmxlIGF0IGxvYWQNCnRpbWUNCj4gc3lz bG9nYXRUZXN0LmM6MTQ6IGVycm9yOiAobmVhciBpbml0aWFsaXphdGlvbiBmb3Igoa5fX18ucG9z LmZ1bmN0aW9uWzBdoa8pDQo+IHN5c2xvZ2F0VGVzdC5jOjE4OiB3YXJuaW5nOiBpbml0aWFsaXph dGlvbiBtYWtlcyBpbnRlZ2VyIGZyb20NCj4gcG9pbnRlciB3aXRob3V0IGEgY2FzdA0KPiBzeXNs b2dhdFRlc3QuYzoxODogZXJyb3I6IGluaXRpYWxpemVyIGVsZW1lbnQgaXMgbm90IGNvbXB1dGFi bGUgYXQgbG9hZA0KdGltZQ0KPiBzeXNsb2dhdFRlc3QuYzoxODogZXJyb3I6IChuZWFyIGluaXRp YWxpemF0aW9uIGZvciChrl9fXy5wb3MuZnVuY3Rpb25bMF2hrykNCg0KQXMgSSBtZW50aW9uZWQg aW4gdG9kYXkncyBtYWlsIHRvIFRvbmcgTGl1LCBJIHRoaW5rIHRoaXMgaGFzIHRvIGRvIHdpdGgg YQ0KY2hhbmdlIGluIGdjYyB0aGF0IG1ha2VzIHN5c2xvZ2F0J3MgdXNlIG9mIF9fRlVOQ1RJT05f XyBubyBsb25nZXINCnN1cHBvcnRlZDsgYW5kIGEgY293b3JrZXIgd2lsbCBsb29rIGF0IHRoaXMg aW4gYSB3ZWVrIG9yIHNvLg0KDQo+DQo+DQo+IDIuIE5vIFBUSFJFQURfVEhSRUFTX01BWCBkZWZp bmVkIGluIC91c3IvaW5jbHVkZS9saW1pdHMuaA0KDQpZb3UgbWVhbiBQVEhSRUFEX1RIUkVBRFNf TUFYIC0tIGJ1dCBpdCdzIHN0aWxsIHVuZGVmaW5lZCBpbiBhdCBsZWFzdCBzb21lDQpyZWNlbnQg aW1wbGVtZW50YXRpb25zIG9mIGxpbWl0cy5oLiAgRG9lcyBfUE9TSVhfVEhSRUFEX1RIUkVBRFNf TUFYIHdvcmsNCmZvciB5b3U/DQoNCj4NCj4gMy4gZXh0ZXJuIHRtcGxfYXJjaF90eXBlX2luZm9f dCBfZXZsVG1wbEFyY2hUeXBlSW5mb1tdW107DQo+IGlzIGludmFsaWQgaW4gZ2NjIDQuMS4wDQoN ClRyeSByZXBsYWNpbmcgW11bXSB3aXRoIFs4XVsyNF0gaW4gdGhlIHZhcmlvdXMgcGxhY2VzIF9l dmxUbXBsQXJjaFR5cGVJbmZvDQppcyBkZWNsYXJlZCBleHRlcm4uDQoNCkppbSBLZW5pc3Rvbg0K SUJNIExUQy1SQVM= |
|
From: James K. <ken...@us...> - 2007-01-29 20:31:25
|
evl...@li... wrote on 01/28/2007 11:3= 9:36 AM: > Hello, > > I am trying to compile evlog-1.6.1 from source code tar ball on > Rehhat enterprise linux 4 (64bit) on intel x86_64 server. > However I got many errors: > > > syslogatArray.c: In function `main': > syslogatArray.c:73: warning: initialization makes integer from > pointer without a cast > syslogatArray.c:73: error: initializer element is not computable at l= oad time > syslogatArray.c :73: error: (near initialization for `___.pos.function[0]') > syslogatArray.c:87: warning: initialization makes integer from > pointer without a cast > syslogatArray.c:87: error: initializer element is not computable at l= oad time > syslogatArray.c:87: error: (near initialization for `___.pos.function[0]') > syslogatArray.c:101: warning: initialization makes integer from > pointer without a cast > syslogatArray.c:101: error: initializer element is not computable atl= oad time > syslogatArray.c:101: error: (near initialization for `___.pos.function[0]') > syslogatArray.c:108: warning: initialization makes integer from > pointer without a cast > syslogatArray.c:108: error: initializer element is not computable atl= oad time > syslogatArray.c:108: error: (near initialization for `___.pos.function[0]') > .... > > I am wondering does that mean I can't compile evlog on 64bit Linux OS= ? evlog is definitely intended to work on both 32-bit and 64-bit Linux, including x86_64. I think the problem here might be that the syslogat macro uses __FUNCTI= ON__ as an initializer value. This worked when gcc implemented __FUNCTION__= as a string literal. But a while ago, I think, new versions of gcc starte= d treating __FUNCTION__ as a variable, which can't serve as an initialize= r value. > What should change to enable it? If you want to use syslogat(), I think you may be out of luck. One of = my coworkers has agreed to look into this in a week or so, and he should b= e able to give you a clearer answer. If all you want to do is make the test suite pass, then you can deconfi= gure the syslogat tests by commenting out the "$TESTDIR/syslogatTest.sh" lin= e in runtests.sh. > > If I just go ahead to use existing i386 rpm for 64bit OS, syslog > forward function won't work. > Any suggestion from the experts will be appreicated! > > Thanks. > > EF---------------------------------------------------------------------= ---- Jim Keniston IBM LTC-RAS= |
|
From: Tong L. <ton...@gm...> - 2007-01-28 19:39:39
|
Hello, I am trying to compile evlog-1.6.1 from source code tar ball on Rehhat enterprise linux 4 (64bit) on intel x86_64 server. However I got many errors: syslogatArray.c: In function `main': syslogatArray.c:73: warning: initialization makes integer from pointer without a cast syslogatArray.c:73: error: initializer element is not computable at load time syslogatArray.c:73: error: (near initialization for `___.pos.function[0]') syslogatArray.c:87: warning: initialization makes integer from pointer without a cast syslogatArray.c:87: error: initializer element is not computable at load time syslogatArray.c:87: error: (near initialization for `___.pos.function[0]') syslogatArray.c:101: warning: initialization makes integer from pointer without a cast syslogatArray.c:101: error: initializer element is not computable at load time syslogatArray.c:101: error: (near initialization for `___.pos.function[0]') syslogatArray.c:108: warning: initialization makes integer from pointer without a cast syslogatArray.c:108: error: initializer element is not computable at load time syslogatArray.c:108: error: (near initialization for `___.pos.function[0]') .... I am wondering does that mean I can't compile evlog on 64bit Linux OS? What should change to enable it? If I just go ahead to use existing i386 rpm for 64bit OS, syslog forward function won't work. Any suggestion from the experts will be appreicated! Thanks. EF |
|
From: James L. <jam...@gm...> - 2007-01-19 09:08:01
|
SGkgOg0KICAgIEkgY2FuIG5vdCBjb21waWxlIGV2bG9nIDEuNi4xIGluIFNMRVMxMCBvciBSSEVM NCBVNC4NCg0KSGVyZSBhcmUgdGhlIGVycm9yOg0KDQoxLiANCnN5c2xvZ2F0VGVzdC5jOiBJbiBm dW5jdGlvbiChrmdhbWWhrzoNCnN5c2xvZ2F0VGVzdC5jOjE0OiB3YXJuaW5nOiBpbml0aWFsaXph dGlvbiBtYWtlcyBpbnRlZ2VyIGZyb20gcG9pbnRlciB3aXRob3V0IGEgY2FzdA0Kc3lzbG9nYXRU ZXN0LmM6MTQ6IGVycm9yOiBpbml0aWFsaXplciBlbGVtZW50IGlzIG5vdCBjb21wdXRhYmxlIGF0 IGxvYWQgdGltZQ0Kc3lzbG9nYXRUZXN0LmM6MTQ6IGVycm9yOiAobmVhciBpbml0aWFsaXphdGlv biBmb3Igoa5fX18ucG9zLmZ1bmN0aW9uWzBdoa8pDQpzeXNsb2dhdFRlc3QuYzoxODogd2Fybmlu ZzogaW5pdGlhbGl6YXRpb24gbWFrZXMgaW50ZWdlciBmcm9tIHBvaW50ZXIgd2l0aG91dCBhIGNh c3QNCnN5c2xvZ2F0VGVzdC5jOjE4OiBlcnJvcjogaW5pdGlhbGl6ZXIgZWxlbWVudCBpcyBub3Qg Y29tcHV0YWJsZSBhdCBsb2FkIHRpbWUNCnN5c2xvZ2F0VGVzdC5jOjE4OiBlcnJvcjogKG5lYXIg aW5pdGlhbGl6YXRpb24gZm9yIKGuX19fLnBvcy5mdW5jdGlvblswXaGvKQ0KDQoNCjIuIE5vIFBU SFJFQURfVEhSRUFTX01BWCBkZWZpbmVkIGluIC91c3IvaW5jbHVkZS9saW1pdHMuaA0KDQozLiBl eHRlcm4gdG1wbF9hcmNoX3R5cGVfaW5mb190IF9ldmxUbXBsQXJjaFR5cGVJbmZvW11bXTsNCmlz IGludmFsaWQgaW4gZ2NjIDQuMS4wDQoNCg0K |
|
From: Lanam, J. <jef...@hp...> - 2007-01-15 21:55:05
|
I have installed the evlog 1.6.1 RPM on Red Hat Linux. I cannot get syslog forwarding to work. I tried running /sbin/slog_fwd, but libevlsyslog.so.1 does not appear to be in the RPM. I tried copying libevlsys.log.so.0.0.0 to libevlsyslog.so.1, so that slog_fwd can find it. When I do that, every command from then on gets at least one of the following errors: ERROR: ld.so: object '/lib/libevlsyslog.so.1' from /etc/ld.so.preload cannot be preloaded: ignored. Please help, the rest of evlog seems to work fine. I am not a Linux expert; I have no idea why it cannot be preloaded. Regards, Jeff |
|
From: Nick R. <ni...@sc...> - 2006-12-10 16:26:39
|
Hi, We are looking at using evlog on our systems. It looks like the last release was in 2004, is evlog still being developed and used in new installations ? Thanks Nick Rathke Sr. Systems Administrator Scientific Computing and Imaging Institute University of Utah |
|
From: Hien Q N. <ngu...@us...> - 2006-03-20 17:22:11
|
Hi Saurabh,
Would you give me some more information regarding your setup? Anyway,
evlog checks if the hardware clock is set to UTC or LOCAL by examine the
/etc/adjtime (line 3 of this file should indicate UTC or LOCAL), or if the
file does not exist the hwclock is LOCAL.
If the hwclock is local then evlog will add the timezone different to the
timestamp. Please check your /etc/adjtime.
Thanks, Hien.
Saurabh Moghe <sau...@jo...>
Sent by: evl...@li...
03/19/2006 11:18 PM
To
evl...@li...
cc
Subject
[evlog-dev] Problem about time zone
Hi,
I have got a problem setting the time zone for the event log server.
The records in the log display the time by adding +5.30 to the time.
This +5.30 is the difference of Indian standard time(IST) from GMT. All
the log records sent have the time stamp of +5.30 from the actual time.
The time for the log record in my router is correct. But the same record
in the server shows a increment of +5.30.
Can anyone help me on this.
Thanks,
Saurabh.
DISCLAIMER------------------------------------------
This communication and any files transmitted with it contain information
which is
confidential and which may also be privileged. It is for the exclusive use
of
the intended recipient(s). If you are not the intended recipient(s),
please
note that any disclosure, copying, printing or use what-so-ever of this
communication or the information contained in it is strictly prohibited.
If you
have received this communication in error, please notify the author or
pos...@jo... and then delete the e-mail together with any
copies of
it. Although this communication is believed to be free of any virus(s)
which
might affect any computer or IT system into which they are opened, it is
the
responsibility of the recipient to ensure that they are virus free.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting
language
that extends applications into web and mobile media. Attend the live
webcast
and join the prime developer group breaking into this new coding
territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
evlog-developers mailing list
evl...@li...
https://lists.sourceforge.net/lists/listinfo/evlog-developers
|
|
From: Saurabh M. <sau...@jo...> - 2006-03-20 07:22:09
|
Hi,
I have got a problem setting the time zone for the event log server.
The records in the log display the time by adding +5.30 to the time.
This +5.30 is the difference of Indian standard time(IST) from GMT. All
the log records sent have the time stamp of +5.30 from the actual time.
The time for the log record in my router is correct. But the same record
in the server shows a increment of +5.30.
Can anyone help me on this.
Thanks,
Saurabh.
DISCLAIMER------------------------------------------
This communication and any files transmitted with it contain information which is
confidential and which may also be privileged. It is for the exclusive use of
the intended recipient(s). If you are not the intended recipient(s), please
note that any disclosure, copying, printing or use what-so-ever of this
communication or the information contained in it is strictly prohibited. If you
have received this communication in error, please notify the author or
pos...@jo... and then delete the e-mail together with any copies of
it. Although this communication is believed to be free of any virus(s) which
might affect any computer or IT system into which they are opened, it is the
responsibility of the recipient to ensure that they are virus free.
|
|
From: James K. <ken...@us...> - 2005-12-02 22:01:57
|
DQoNCg0KDQpldmxvZy1kZXZlbG9wZXJzLWFkbWluQGxpc3RzLnNvdXJjZWZvcmdlLm5ldCB3cm90 ZSBvbiAxMi8wMS8yMDA1IDAzOjMyOjUyDQpQTToNCg0KPiBXaHkgdGhlIEVWTE9HIHByb2dyYW1z IGFyZSBhbGwgbGlua2VkIHdpdGggdGhlIHN0YXRpYyBsaWJldmwuYQ0KPiBsaWJyYXJ5IGluc3Rl YWQgb2YgdGhlIHNoYXJlZCBvbmU/DQoNCk9uZSBwb3NzaWJsZSBleHBsYW5hdGlvbiBpcyB0aGF0 IHdlIHN0YXJ0ZWQgb3V0IGRvaW5nIGl0IHRoYXQgd2F5IGFuZCBuZXZlcg0KdGhvdWdodCBhYm91 dCBjaGFuZ2luZyBpdC4gOi19ICBIaWVuJ3MgdGhlIGV2bG9nIGJ1aWxkIGV4cGVydCwgYnV0IEkg a25vdw0Kb2Ygbm8gcmVhc29uIHdoeSBidWlsZGluZyB3aXRoIHRoZSBzaGFyZWQgbGlicmFyaWVz IHdvdWxkIGNyZWF0ZSBwcm9ibGVtcy4NCg0KV2UnbGwgbG9vayBpbnRvIGl0LiAgUGF0Y2hlcyB3 ZWxjb21lLg0KDQo+IExpbmtpbmcgaXQgd2l0aCB0aGUgc3RhdGljIGxpYg0KPiBtYWtlcyBFVkxP RyBodWdl4oCmLiBlc3BlY2lhbGx5IGNvbXBhcmluZyBpdCB3aXRoIHRoZSBzeXNsb2cuIEnigJl2 ZQ0KPiBkb3dubG9hZGVkIHRoZSBsYXRlc3QgdmVyc2lvbiBvZiBldmxvZyBsaWJyYXJ5ICgxLjYu MSkgYW5kIGJ1aWxkIGl0DQo+IHVzaW5nIHRoZSBkZWZhdWx0IHNldHRpbmdzLg0KPg0KPiBSZWdh cmRzDQo+IFIuDQoNCkppbSBLZW5pc3Rvbg0KSUJNIExpbnV4IFRlY2hub2xvZ3kgQ2VudGVy |
|
From: Radoslaw B. <zfi...@po...> - 2005-12-01 23:33:25
|
Why the EVLOG programs are all linked with the static libevl.a library instead of the shared one? Linking it with the static lib makes EVLOG huge.. especially comparing it with the syslog. I've downloaded the latest version of evlog library (1.6.1) and build it using the default settings. Regards R. |
|
From: Bryan S. <Bry...@hp...> - 2005-06-10 21:46:29
|
In trying to use evlog, the documentation is incomplete. Apparently, some of the information would be in the Posix draft standard 1003.25, especially for the posix_log_* calls. I'm trying to locate a source for this draft standard. The IEEE website currently lists this standard as: > Status: Withdrawn PAR. Standards project no longer endorsed by the IEEE. Is this still under development? Since the IEEE isn't involved anymore, can a copy be posted to the evlog website again? Other suggestions on how to get a copy? -- Bryan Sutula <Bry...@hp...> |
|
From: Hien Q N. <ngu...@us...> - 2005-05-17 22:02:30
|
Hi Chris, I am not the maintainer for snmp patch, but I believe those patches on evlog site should still apply to v1.6.1 Give it a shot. Patch in this order: evlog-subagent-1.5.2-part1.patch evlog-subagent-1.5.2-part2.patch evlog-lookback-refine.patch Thanks, Hien. Hien Nguyen ngu...@us... (503) 578-4347 Chris Kottaridis <chr...@wi...> Sent by: evl...@li... 05/17/05 02:27 PM Please respond to chris.kottaridis To evl...@li... cc Subject [evlog-dev] SNMP subagent for 1.6.1 I have the 1.6.1 tarball for evlog. I also need to get evlog-snmp. While I have been able to locate some snmp patches for earlier releases I have not been able to locate snmp subagents for 1.6.1 of evlog. Where can I find the snmp subagent for evlog version 1.6.1 ? -- Chris Kottaridis <chr...@wi...> Wind River Systems ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ evlog-developers mailing list evl...@li... https://lists.sourceforge.net/lists/listinfo/evlog-developers |
|
From: Chris K. <chr...@wi...> - 2005-05-17 21:27:10
|
I have the 1.6.1 tarball for evlog. I also need to get evlog-snmp. While I have been able to locate some snmp patches for earlier releases I have not been able to locate snmp subagents for 1.6.1 of evlog. Where can I find the snmp subagent for evlog version 1.6.1 ? -- Chris Kottaridis <chr...@wi...> Wind River Systems |
|
From: LeJacq, J. P. <Jea...@ON...> - 2005-03-23 19:25:16
|
> -----Original Message----- > From: Hien Nguyen [mailto:hi...@us...]=20 > Sent: Wednesday, March 23, 2005 2:09 PM > To: LeJacq, Jean Pierre > Cc: evl...@li... > Subject: Re: [evlog-dev] Support for kernel 2.6.x >=20 > Yes, evlog does support the kernel 2.6.x, but we do not have=20 > patch for the latest kernel. There's currently a patch to=20 > kernel v2.6.0 on sf.net.=20 > What version of 2.6.x kernel you are looking at? 2.6.10 and specifically the debian kernel source package. I see the patch now. Sorry about that, I only saw mention of 2.4.x in the documentation and assumed 2.6.x was not supported. > However, if you don't plan to log event via evlog api in the=20 > kernel then you do not need evlog kernel patch, only user=20 > package would be enough. I was hoping to. I'll give the 2.6.0 patch a go and report back. --=20 JP |
|
From: Hien N. <hi...@us...> - 2005-03-23 19:09:10
|
Hi, Yes, evlog does support the kernel 2.6.x, but we do not have patch for the latest kernel. There's currently a patch to kernel v2.6.0 on sf.net. What version of 2.6.x kernel you are looking at? However, if you don't plan to log event via evlog api in the kernel then you do not need evlog kernel patch, only user package would be enough. Thanks, Hien. LeJacq, Jean Pierre wrote: >Hi evlog, > >Does evlog support the 2.6.x kernel series? If so, are >any patches required? > >Thanks in advance. > > > |
|
From: LeJacq, J. P. <Jea...@ON...> - 2005-03-23 13:04:08
|
Hi evlog, Does evlog support the 2.6.x kernel series? If so, are any patches required? Thanks in advance. --=20 JP =20 |
|
From: dmitry p. <dpe...@ru...> - 2005-03-09 15:32:14
|
Hi evlog-developers,
I propose the patch (attached below) to achieve the following goals
1. allow evlog to be compiled with gcc version 3.xx ( I have 3.4.3 )
2. allow evlog to be built in separate directory
diff -uNr evlog-1.6.1/user/cmd/ela/Makefile.am
evlog-1.6.1-mvista/user/cmd/ela/Makefile.am
--- evlog-1.6.1/user/cmd/ela/Makefile.am 2004-12-29 01:19:17.000000000
+0300
+++ evlog-1.6.1-mvista/user/cmd/ela/Makefile.am 2005-02-25
18:14:42.000000000 +0300
@@ -5,7 +5,7 @@
DISTCLEANFILES +=
MAINTAINERCLEANFILES +=
-INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/user/include/linux
+INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/user/include/linux -I../../include
EXTRA_DIST += ela ela_crt_rpt ela_sig ela_funcs ela_console
ela_hw_alert\
ela_show ela_show_all ela_vpd_funcs\
diff -uNr evlog-1.6.1/user/cmd/evlactiond/Makefile.am
evlog-1.6.1-mvista/user/cmd/evlactiond/Makefile.am
--- evlog-1.6.1/user/cmd/evlactiond/Makefile.am 2004-02-21
06:59:09.000000000 +0300
+++ evlog-1.6.1-mvista/user/cmd/evlactiond/Makefile.am 2005-02-25
18:14:52.000000000 +0300
@@ -13,7 +13,7 @@
MOSTLYCLEANFILES +=
# General compilation flags
-INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/user/include/linux
+INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/user/include/linux -I../../include
sbin_PROGRAMS := evlactiond
evlactiond_SOURCES := evlactiond.h evlactiond.c
diff -uNr evlog-1.6.1/user/cmd/evlconfig/Makefile.am
evlog-1.6.1-mvista/user/cmd/evlconfig/Makefile.am
--- evlog-1.6.1/user/cmd/evlconfig/Makefile.am 2004-04-28
21:44:22.000000000 +0400
+++ evlog-1.6.1-mvista/user/cmd/evlconfig/Makefile.am 2005-02-25
18:15:06.000000000 +0300
@@ -11,7 +11,7 @@
MOSTLYCLEANFILES +=
# General compilation flags
-INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/user/include/linux
+INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/user/include/linux -I../../include
AM_CFLAGS = @CFLAGS@
sbin_PROGRAMS := evlconfig
diff -uNr evlog-1.6.1/user/cmd/evlfacility/Makefile.am
evlog-1.6.1-mvista/user/cmd/evlfacility/Makefile.am
--- evlog-1.6.1/user/cmd/evlfacility/Makefile.am 2004-02-21
07:00:15.000000000 +0300
+++ evlog-1.6.1-mvista/user/cmd/evlfacility/Makefile.am 2005-02-25
18:15:15.000000000 +0300
@@ -11,7 +11,7 @@
MOSTLYCLEANFILES +=
# General compilation flags
-INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/user/include/linux
+INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/user/include/linux -I../../include
sbin_PROGRAMS := evlfacility
evlfacility_SOURCES := evlfacility.c
diff -uNr evlog-1.6.1/user/cmd/evlgentmpls/Makefile.am
evlog-1.6.1-mvista/user/cmd/evlgentmpls/Makefile.am
--- evlog-1.6.1/user/cmd/evlgentmpls/Makefile.am 2004-02-21
07:00:59.000000000 +0300
+++ evlog-1.6.1-mvista/user/cmd/evlgentmpls/Makefile.am 2005-02-25
18:15:24.000000000 +0300
@@ -11,7 +11,7 @@
MOSTLYCLEANFILES +=
# General compilation flags
-INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/user/include/linux
+INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/user/include/linux -I../../include
sbin_PROGRAMS := evlgentmpls
evlgentmpls_SOURCES := evlgentmpls.c
diff -uNr evlog-1.6.1/user/cmd/evlnotify/Makefile.am
evlog-1.6.1-mvista/user/cmd/evlnotify/Makefile.am
--- evlog-1.6.1/user/cmd/evlnotify/Makefile.am 2004-02-21
07:01:28.000000000 +0300
+++ evlog-1.6.1-mvista/user/cmd/evlnotify/Makefile.am 2005-02-25
18:15:31.000000000 +0300
@@ -11,7 +11,7 @@
MOSTLYCLEANFILES +=
# General compilation flags
-INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/user/include/linux
+INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/user/include/linux -I../../include
sbin_PROGRAMS := evlnotify
evlnotify_SOURCES := evlnotify.c
diff -uNr evlog-1.6.1/user/cmd/evlnotifyd/evlnotifyd.c
evlog-1.6.1-mvista/user/cmd/evlnotifyd/evlnotifyd.c
--- evlog-1.6.1/user/cmd/evlnotifyd/evlnotifyd.c 2004-03-24
01:18:23.000000000 +0300
+++ evlog-1.6.1-mvista/user/cmd/evlnotifyd/evlnotifyd.c 2005-02-25
20:40:29.517168273 +0300
@@ -113,7 +113,10 @@
/* Init clients info array */
initClients();
-
+
+ /* unlink notify server address */
+ (void) unlink(EVLNOTIFYD_SERVER_SOCKET);
+
/*
* Create the list with the first node is empty (NULL).
* This first node will always exist from now on.
diff -uNr evlog-1.6.1/user/cmd/evlnotifyd/Makefile.am
evlog-1.6.1-mvista/user/cmd/evlnotifyd/Makefile.am
--- evlog-1.6.1/user/cmd/evlnotifyd/Makefile.am 2004-03-24
01:18:23.000000000 +0300
+++ evlog-1.6.1-mvista/user/cmd/evlnotifyd/Makefile.am 2005-02-25
18:15:39.000000000 +0300
@@ -11,7 +11,7 @@
MOSTLYCLEANFILES +=
# General compilation flags
-INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/user/include/linux
+INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/user/include/linux -I../../include
AM_CFLAGS = @CFLAGS@ -D_EVL_WRITE_DIRECT
sbin_PROGRAMS := evlnotifyd
diff -uNr evlog-1.6.1/user/cmd/evlnotifyd/test/Makefile.am
evlog-1.6.1-mvista/user/cmd/evlnotifyd/test/Makefile.am
--- evlog-1.6.1/user/cmd/evlnotifyd/test/Makefile.am 2003-12-19
20:14:03.000000000 +0300
+++ evlog-1.6.1-mvista/user/cmd/evlnotifyd/test/Makefile.am 2005-02-25
18:18:11.000000000 +0300
@@ -11,7 +11,7 @@
MOSTLYCLEANFILES +=
# General compilation flags
-INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/kernel/@KERN_VERSION@/include
+INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/kernel/@KERN_VERSION@/include -I../../../include
noinst_PROGRAMS := testclient test testnull
LDADD := ../../../lib/.libs/libevl.a
diff -uNr evlog-1.6.1/user/cmd/evlogd/Makefile.am
evlog-1.6.1-mvista/user/cmd/evlogd/Makefile.am
--- evlog-1.6.1/user/cmd/evlogd/Makefile.am 2004-02-21
07:05:25.000000000 +0300
+++ evlog-1.6.1-mvista/user/cmd/evlogd/Makefile.am 2005-02-25
18:15:48.000000000 +0300
@@ -26,7 +26,7 @@
MOSTLYCLEANFILES +=
# General compilation flags
-INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/user/include/linux
+INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/user/include/linux -I../../include
sbin_PROGRAMS := evlogd evlogrmtd
diff -uNr evlog-1.6.1/user/cmd/evlogmgr/Makefile.am
evlog-1.6.1-mvista/user/cmd/evlogmgr/Makefile.am
--- evlog-1.6.1/user/cmd/evlogmgr/Makefile.am 2004-02-21
07:06:00.000000000 +0300
+++ evlog-1.6.1-mvista/user/cmd/evlogmgr/Makefile.am 2005-02-25
18:15:56.000000000 +0300
@@ -11,7 +11,7 @@
MOSTLYCLEANFILES +=
# General compilation flags
-INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/user/include/linux
+INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/user/include/linux -I../../include
sbin_PROGRAMS := evlogmgr
evlogmgr_SOURCES := evl_logmgmt.h evlogmgr.c evl_logmgmt.c
diff -uNr evlog-1.6.1/user/cmd/evlsend/Makefile.am
evlog-1.6.1-mvista/user/cmd/evlsend/Makefile.am
--- evlog-1.6.1/user/cmd/evlsend/Makefile.am 2004-02-21
07:06:26.000000000 +0300
+++ evlog-1.6.1-mvista/user/cmd/evlsend/Makefile.am 2005-02-25
18:16:04.000000000 +0300
@@ -11,7 +11,7 @@
MOSTLYCLEANFILES +=
# General compilation flags
-INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/user/include/linux
+INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/user/include/linux -I../../include
sbin_PROGRAMS := evlsend
evlsend_SOURCES := evlsend.c
diff -uNr evlog-1.6.1/user/cmd/evltc/Makefile.am
evlog-1.6.1-mvista/user/cmd/evltc/Makefile.am
--- evlog-1.6.1/user/cmd/evltc/Makefile.am 2004-02-21 07:06:51.000000000
+0300
+++ evlog-1.6.1-mvista/user/cmd/evltc/Makefile.am 2005-02-25
18:16:11.000000000 +0300
@@ -11,7 +11,7 @@
MOSTLYCLEANFILES +=
# General compilation flags
-INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/user/include/linux
+INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/user/include/linux -I../../include
sbin_PROGRAMS := evltc
evltc_SOURCES := evltc.c funcs.c
diff -uNr evlog-1.6.1/user/cmd/evlview/Makefile.am
evlog-1.6.1-mvista/user/cmd/evlview/Makefile.am
--- evlog-1.6.1/user/cmd/evlview/Makefile.am 2004-02-21
07:07:24.000000000 +0300
+++ evlog-1.6.1-mvista/user/cmd/evlview/Makefile.am 2005-02-25
18:16:22.000000000 +0300
@@ -11,7 +11,7 @@
MOSTLYCLEANFILES +=
# General compilation flags
-INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/user/include/linux
+INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/user/include/linux -I../../include
sbin_PROGRAMS := evlview
evlview_SOURCES := evlview.c specfmt.c
diff -uNr evlog-1.6.1/user/include/evlog.h.in
evlog-1.6.1-mvista/user/include/evlog.h.in
--- evlog-1.6.1/user/include/evlog.h.in 2004-09-24 22:27:12.000000000
+0400
+++ evlog-1.6.1-mvista/user/include/evlog.h.in 2005-02-23
20:09:41.000000000 +0300
@@ -202,8 +202,11 @@
#define syslogat(priority, fmt, ...) \
do { \
static struct evlog_info __attribute__((section(".log"),unused)) ___ \
- = { fmt, __stringify(EVL_FACILITY_NAME), _EVLOG_POS }; \
+ = { fmt, __stringify(EVL_FACILITY_NAME) }; \
+ ___.pos.line = __LINE__; \
char *unbraced_fmt = _evl_unbrace(fmt); \
+ strncpy( ___.pos.function, __FUNCTION__,
sizeof( ___.pos.function ) ); \
+ strncpy(___.pos.file,__FILE__, sizeof( ___.pos.file )) ; \
if (_evl_syslogat(priority, __stringify(EVL_FACILITY_NAME), \
evl_gen_event_type(__FILE__, __FUNCTION__, fmt), \
fmt, unbraced_fmt, ##__VA_ARGS__) != 1) \
diff -uNr evlog-1.6.1/user/lib/Makefile.am
evlog-1.6.1-mvista/user/lib/Makefile.am
--- evlog-1.6.1/user/lib/Makefile.am 2004-04-28 21:43:09.000000000 +0400
+++ evlog-1.6.1-mvista/user/lib/Makefile.am 2005-02-25
18:06:19.000000000 +0300
@@ -13,7 +13,7 @@
EXTRA_DIST += $(LIBEVLEXTRAFILES) Makefile.mk
# General compilation flags
-INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/user/include/linux
+INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/user/include/linux -I../include
AM_CFLAGS = @CFLAGS@
# Libraries
diff -uNr evlog-1.6.1/user/lib/template/convert.c
evlog-1.6.1-mvista/user/lib/template/convert.c
--- evlog-1.6.1/user/lib/template/convert.c 2004-12-15
20:05:46.000000000 +0300
+++ evlog-1.6.1-mvista/user/lib/template/convert.c 2005-02-23
19:50:45.000000000 +0300
@@ -245,6 +245,7 @@
}
break;
default:
+ break;
}
}
diff -uNr evlog-1.6.1/user/lib/template/Makefile.am
evlog-1.6.1-mvista/user/lib/template/Makefile.am
--- evlog-1.6.1/user/lib/template/Makefile.am 2004-02-21
07:09:00.000000000 +0300
+++ evlog-1.6.1-mvista/user/lib/template/Makefile.am 2005-02-25
18:03:51.000000000 +0300
@@ -11,7 +11,7 @@
MOSTLYCLEANFILES += lex.tt.c tt.tab.h tt.tab.c
# General compilation flags
-INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/user/include/linux
+INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/user/include/linux -I../../include
lex.tt.c: tmpllex.l
flex -Ptt $(top_srcdir)/user/lib/template/tmpllex.l
diff -uNr evlog-1.6.1/user/lib/test/bitfields/Makefile.am
evlog-1.6.1-mvista/user/lib/test/bitfields/Makefile.am
--- evlog-1.6.1/user/lib/test/bitfields/Makefile.am 2004-03-24
00:57:19.000000000 +0300
+++ evlog-1.6.1-mvista/user/lib/test/bitfields/Makefile.am 2005-02-25
18:09:19.000000000 +0300
@@ -13,7 +13,7 @@
MOSTLYCLEANFILES += bftest.c bftestN.c bftestU.c bftestUN.c bftestS.c
bftestSN.c
# General compilation flags
-INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/user/include/linux
+INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/user/include/linux -I../../../include
bitfields_testdir := $(localstatedir)/test
bitfields_test_PROGRAMS := bftest bftestSN
@@ -34,23 +34,27 @@
LDADD := ../../libevl.la
-# FIXME: This should be done at configure time.
-# These rules also create the corresponding .t files (bftest.t or
bftestU.t).
-bftest.c: mktest.sh bftest.cpre bftest.cpost bftest.tpre bftest.tpost
mkc.awk mkt.awk
- ./mktest.sh
+bftest.c:mktest.sh bftest.cpre bftest.cpost bftest.tpre bftest.tpost
mkc.awk mkt.awk
+ pushd $(top_srcdir)/user/lib/test/bitfields/; ./mktest.sh; popd
+ cp $(top_srcdir)/user/lib/test/bitfields/bftest.c .
bftestN.c: mktest.sh bftest.cpre bftest.cpost bftest.tpre bftest.tpost
mkc.awk mkt.awk
- ./mktest.sh -n
+ pushd $(top_srcdir)/user/lib/test/bitfields/; ./mktest.sh -n; popd
+ cp $(top_srcdir)/user/lib/test/bitfields/bftestN.c .
bftestU.c: mktest.sh bftest.cpre bftest.cpost bftest.tpre bftest.tpost
mkc.awk mkt.awk
- ./mktest.sh -u
+ pushd $(top_srcdir)/user/lib/test/bitfields/; ./mktest.sh -u; popd
+ cp $(top_srcdir)/user/lib/test/bitfields/bftestU.c .
bftestUN.c: mktest.sh bftest.cpre bftest.cpost bftest.tpre bftest.tpost
mkc.awk mkt.awk
- ./mktest.sh -u -n
+ pushd $(top_srcdir)/user/lib/test/bitfields/; ./mktest.sh -u -n; popd
+ cp $(top_srcdir)/user/lib/test/bitfields/bftestUN.c .
bftestS.c: mktest.sh bftest.cpre bftest.cpost bftest.tpre bftest.tpost
mkc.awk mkt.awk
- ./mktest.sh -s
+ pushd $(top_srcdir)/user/lib/test/bitfields/; ./mktest.sh -s; popd
+ cp $(top_srcdir)/user/lib/test/bitfields/bftestS.c .
bftestSN.c: mktest.sh bftest.cpre bftest.cpost bftest.tpre bftest.tpost
mkc.awk mkt.awk
- ./mktest.sh -s -n
+ pushd $(top_srcdir)/user/lib/test/bitfields/; ./mktest.sh -s -n ; popd
+ cp $(top_srcdir)/user/lib/test/bitfields/bftestSN.c .
diff -uNr evlog-1.6.1/user/lib/test/Makefile.am
evlog-1.6.1-mvista/user/lib/test/Makefile.am
--- evlog-1.6.1/user/lib/test/Makefile.am 2004-03-24 00:56:04.000000000
+0300
+++ evlog-1.6.1-mvista/user/lib/test/Makefile.am 2005-02-25
18:12:15.000000000 +0300
@@ -62,7 +62,7 @@
# General compilation flags
-INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/user/include/linux
+INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/user/include/linux -I../../include
testsdir = $(localstatedir)/test
diff -uNr evlog-1.6.1/user/lib/test/threadTest2.c
evlog-1.6.1-mvista/user/lib/test/threadTest2.c
--- evlog-1.6.1/user/lib/test/threadTest2.c 2003-03-18
00:47:17.000000000 +0300
+++ evlog-1.6.1-mvista/user/lib/test/threadTest2.c 2005-02-25
20:44:07.864582010 +0300
@@ -24,7 +24,7 @@
* (which in turn calls posix_log_vprintf).
*/
-#define MAX_THREADS (PTHREAD_THREADS_MAX-2)
+#define MAX_THREADS (_POSIX_THREAD_THREADS_MAX - 2)
struct workerStats {
pthread_t tid;
diff -uNr evlog-1.6.1/user/lib/test/threadTest.c
evlog-1.6.1-mvista/user/lib/test/threadTest.c
--- evlog-1.6.1/user/lib/test/threadTest.c 2002-03-26 00:19:05.000000000
+0300
+++ evlog-1.6.1-mvista/user/lib/test/threadTest.c 2005-02-25
20:43:58.066493019 +0300
@@ -33,7 +33,7 @@
*
*/
-#define MAX_THREADS (PTHREAD_THREADS_MAX-2)
+#define MAX_THREADS (_POSIX_THREAD_THREADS_MAX - 2)
struct workerStats {
pthread_t tid;
diff -uNr evlog-1.6.1/user/lib/util/format.c
evlog-1.6.1-mvista/user/lib/util/format.c
--- evlog-1.6.1/user/lib/util/format.c 2004-04-30 04:27:56.000000000
+0400
+++ evlog-1.6.1-mvista/user/lib/util/format.c 2005-02-23
19:51:45.000000000 +0300
@@ -286,7 +286,8 @@
seg->u.fs_attname = nsaName;
seg->u2.fs_attribute = NULL;
break;
- default:
+ default:
+ break;
}
seg->fs_userfmt = attrFmt;
if (attrFmt
@@ -475,7 +476,8 @@
*/
size += _evlGetMaxDumpLen();
break;
- default:
+ default:
+ break;
}
p = p->li_next;
} while (p != head);
@@ -667,7 +669,7 @@
case TY_INT: return TY_UINT;
case TY_LONG: return TY_ULONG;
case TY_LONGLONG: return TY_ULONGLONG;
- default:
+ default: break;
}
return ty;
}
diff -uNr evlog-1.6.1/user/lib/util/Makefile.am
evlog-1.6.1-mvista/user/lib/util/Makefile.am
--- evlog-1.6.1/user/lib/util/Makefile.am 2004-02-21 07:11:10.000000000
+0300
+++ evlog-1.6.1-mvista/user/lib/util/Makefile.am 2005-02-25
18:05:04.000000000 +0300
@@ -11,7 +11,7 @@
MOSTLYCLEANFILES +=
# General compilation flags
-INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/user/include/linux
+INCLUDES = -I$(top_srcdir)/user/include -I
$(top_srcdir)/user/include/linux -I../../include
evlutil_sources := scanner.c evl_list.c format.c fmtbuf.c evl_common.c
|
|
From: Darien K. <kin...@mi...> - 2005-02-14 19:01:38
|
Hein: Yes, printk forwarding was enabled in the kernel configuration as well as syslog forwarding (through the libevlsyslog.so.0.0.0 reference in /etc/ld.so.preload). I'm not quite sure if it's an SELinux kernel issue or something else. Brian: Thanks for the patch idea. Part of the odd setup, is that the target system has to maintain two completely separate syslog daemons, both simultaneously running; I figured evlog would help with that goal. At this stage, I've decided to move evlog's kernel-level functionality into manageable user-space components for now (e.g., pipes, sockets, sysklogd, syslog-ng, socat, cat, emlog). I'll let you know if I uncover any more detail regarding these anomalies when I revisit evlog later on. FYI, since reads from /proc/kmsg are destructive, I've found that transferring the contents to an emlog-based pipe allow for non-destructive, simultaneous reads. URL: http://www.circlemud.org/~jelson/software/emlog/ Thanks again, -- Darien Kindlund The MITRE Corporation InfoSec Engr / Scientist Hien Q Nguyen wrote: > How do you forward printk? DO you enable "forwarding printk" in the > kernel? Or you just using syslog forwarding (slog_fwd)? > If you are using slog_fwd to forward printk then try to restart evlogd > from a console (not an ssh session). Bryan Sutula wrote: > On Fri, 2005-02-11 at 00:20 -0500, Darien Kindlund wrote: >>After installing evlog-1.6.1, user-space syslog messages appear to show >>up fine, but kernel-level messages appear to not get written out to >>/var/evlog/eventlog and /var/evlog/privatelog automatically... Only >>restarting the evlog daemon seems to cause the kernel buffer to flush >>out to disk. >>. >>Any suggestions would be appreciated on how to fix this; let me know if >>you need any additional information. > > If you just want to get something working, you could try the syslog > patch in the previous thread. I'd appreciate any feedback if you try > it. |
|
From: Hien Q N. <ngu...@us...> - 2005-02-14 18:27:37
|
How do you forward printk? DO you enable "forwarding printk" in the kernel? Or you just using syslog forwarding (slog_fwd)? If you are using slog_fwd to forward printk then try to restart evlogd from a console (not an ssh session). Thanks, Hien Hien Nguyen ngu...@us... (503) 578-4347 Darien Kindlund <kin...@mi...> 02/10/05 09:20 PM Please respond to Darien Kindlund To evl...@li... cc ngu...@us... Subject [evlog-1.6.1] Kernel messages seem to be buffered forever... Hi Developers, After installing evlog-1.6.1, user-space syslog messages appear to show up fine, but kernel-level messages appear to not get written out to /var/evlog/eventlog and /var/evlog/privatelog automatically... Only restarting the evlog daemon seems to cause the kernel buffer to flush out to disk. Background Info: OS: Gentoo SELinux Kernel: selinux-sources-2.4.25-r2 The evlog-1.4.2_kernel2.4.20.patch patches cleanly to the kernel source, and kernel messages do appear to be received by evlogd, but only upon startup. Here's a typical data flow example of how evlogd appears to operate: 1) kernel calls printk() - writes text out to buffer 2) evlactiond starts up 3) evlnotifyd starts up 4) evlogd starts up 5) evlogd flushes kernel buffer text in (#1) out to disk 6) rest of system starts up 7) kernel calls printk() - writes text out to buffer 8) user logs in 9) user calls evlview -m, user sees kernel text from (#1) but NOT from (#7) 10) user restarts syslogd 11) evlogd flushes kernel buffer text in (#7) out to disk 12) user now sees kernel text from both (#1) and (#7) So, basically, kernel printk() messages don't get written to disk until evlog service restarts, while user-level syslog messages get written to disk in real-time. Any suggestions would be appreciated on how to fix this; let me know if you need any additional information. Thanks, -- Darien Kindlund The MITRE Corporation InfoSec Engr / Scientist |
12 messages has been excluded from this view by a project administrator.
