> On Tue, 16 Aug 2005 09:30:36 +0100, Dave Shield <[EMAIL PROTECTED]> said:
Dave> It's slightly unfortunate that Yegor has been working with the old
Dave> 5.0.x line (where this fix wasn't applied), and even more unfortunate
Dave> that I didn't investigate the current code more fully before
Da
Hi,
I've checked the solution provided by 5.1.3.1 and it works. As I earlier
looked at this solution I misunderstood the real meaning of times()
function and searched for the function that returns absolute uptime.
Thanks for your help and sorry for misunderstandings.
Best Regards,
Yegor Yefremo
On Tue, 16 Aug 2005 09:30:36 +0100 Dave wrote:
DS> [...] even more unfortunate
DS> that I didn't investigate the current code more fully before
DS> responding. Sorry for the confusion.
We're supposed to investigate the code before responding? Aw man, now I'll
never get anything done! :-P
--
Rob
Robert Story wrote:
> TA> > I'm a little concerned that Thomas seems to think this is already fixed,
> TA> > but Dave has checked in a fix. I tend to avoid the v3 stuff when I can,
> TA> > so I just want to see if some double checking is called for?
> TA>
> TA> I'm referring to Wes' fixes discuss
On Mon, 15 Aug 2005 19:46:28 +0200 Thomas wrote:
TA> Robert Story wrote:
TA> > I'm a little concerned that Thomas seems to think this is already fixed,
TA> > but Dave has checked in a fix. I tend to avoid the v3 stuff when I can,
TA> > so I just want to see if some double checking is called for?
TA
Robert Story wrote:
On Fri, 05 Aug 2005 22:05:28 +0200 Thomas wrote:
TA> Yegor Yefremov wrote:
TA> > I have a problem with snmpset (net-snmp 5.0.9). In my system I have an
TA> > encrypted (md5) password. I have an option to change the system time via
TA> > snmp. The system starts with
TA> > initi
On Fri, 05 Aug 2005 22:05:28 +0200 Thomas wrote:
TA> Yegor Yefremov wrote:
TA> > I have a problem with snmpset (net-snmp 5.0.9). In my system I have an
TA> > encrypted (md5) password. I have an option to change the system time via
TA> > snmp. The system starts with
TA> > initial time 01-01-1970 00:
On Mon, 2005-08-15 at 06:52 -0700, David T. Perkins wrote:
> Guys,
>
> Why not...
>
> long get_uptime_in_sec(void)
> {
> struct sysinfo info;
>
> if (sysinfo(&info) < 0 ) {
> perror("getting uptime");
> return -1; /* TODO: maybe this should be 0 */
> }
> return
Guys,
Why not...
long get_uptime_in_sec(void)
{
struct sysinfo info;
if (sysinfo(&info) < 0 ) {
perror("getting uptime");
return -1; /* TODO: maybe this should be 0 */
}
return info.uptime;
}
On Mon, 15 Aug 2005, Dave Shield wrote:
> On Mon, 2005-08-15 at 14:1
On Mon, 2005-08-15 at 14:13 +0200, Yegor Yefremov wrote:
> Comment a accepted:
>
> long get_uptime_in_sec(void)
> {
> long ret;
> struct sysinfo *info =
> (struct sysinfo*)malloc(sizeof(struct sysinfo));
>
> if(sysinfo(info) < 0)
> {
>
On Mon, Aug 15, 2005 at 10:14:14AM +0100, Dave Shield wrote:
> On Mon, 2005-08-15 at 11:03 +0200, Yegor Yefremov wrote:
> > Snmpv3_local_snmpEngineTime() gives a difference between start time and
> > now in seconds. It means when you change the year you have too big
> > difference. But actually one
Hi,
attached all changes I made to snmpv3.c, lcd_time.c, system.h.
Used version: 5.0.9 (can be applied to 5.1.3.1 too)
System: Linux
Best regards,
Yegor Yefremov
>On Mon, 2005-08-15 at 11:03 +0200, Yegor Yefremov wrote:
Comment a accepted:
long get_uptime_in_sec(void)
{
long ret;
Comment a accepted:
long get_uptime_in_sec(void)
{
long ret;
struct sysinfo *info =
(struct sysinfo*)malloc(sizeof(struct sysinfo));
if(sysinfo(info) < 0)
{
perror("Getting uptime");
return -1;
On Mon, 2005-08-15 at 11:03 +0200, Yegor Yefremov wrote:
> Snmpv3_local_snmpEngineTime() gives a difference between start time and
> now in seconds. It means when you change the year you have too big
> difference. But actually one wants to know the time difference from
> system start (snmpv3 engine
Hi,
I've fixed the problem. The problem was in function
"usm_check_and_update_timeliness" (snmpusm.c)
myBoots = snmpv3_local_snmpEngineBoots();
myTime = snmpv3_local_snmpEngineTime();
if ((int) secEngineIDLen == myIDLength
&& memcmp(secEngineID, myID, myIDLength) == 0) {
u_in
Yegor Yefremov wrote:
I have changed to version 5.0.10(5.1.3.1 is not so easy to integrate in
my system) but the bug is still there. Do you know in which file or
filegroup it was fixed?
Too many to list, most of them in snmplib/. Check the CVS logs if you're
curious enough.
Are you sure you
Hi,
I have changed to version 5.0.10(5.1.3.1 is not so easy to integrate in
my system) but the bug is still there. Do you know in which file or
filegroup it was fixed?
>Yegor Yefremov wrote:
>> I have a problem with snmpset (net-snmp 5.0.9). In my system I have
an
>> encrypted (md5) password. I h
Do you know what the patch number is? Or which file(s) is this fix in?
Thanks,
FT
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Thomas
Anders
Sent: Friday, August 05, 2005 1:05 PM
To: net-snmp-coders@lists.sourceforge.net
Subject: Re: snmpset and
Yegor Yefremov wrote:
I have a problem with snmpset (net-snmp 5.0.9). In my system I have an
encrypted (md5) password. I have an option to change the system time via
snmp. The system starts with
initial time 01-01-1970 00:00:00 UTC+0. I can change the time manually
or via sntp. So if I don't set
Hi,
I have a problem with snmpset (net-snmp 5.0.9). In my system I have an
encrypted (md5) password. I have an option to change the system time via
snmp. The system starts with
initial time 01-01-1970 00:00:00 UTC+0. I can change the time manually
or via sntp. So if I don't set any password everyt
20 matches
Mail list logo
