search for: maxage

I see this in syslog: Aug 12 03:57:22 orion upsd[18274]: Data for UPS [a102-apc-10] is stale - check driver (one for each UPS). Then I see a bunch of messages like this: Aug 12 03:58:02 orion upsd[18274]: write() failed for ::1: Broken pipe Aug 12 03:58:02 orion snmpd[2872]: Connection from UDP: [127.0.0.1]:50940 And then it returns to normal like this: Aug 12 03:58:04 orion upsd[18274]: UPS

[please keep the list CC'd, thanks] > On Aug 14, 2015, at 10:27 AM, Bob Brown <bbrown at harpercollege.edu> wrote: > > Would it put NA in the log files if maxage was too short? I think so. I haven't tried it, but if snmp-ups polls every 30 seconds, and MAXAGE is 15, then with a random polling interval, 50% of the time the data would be more than 15 seconds old. In practice, the driver and upsd were probably started around the same time, and due to diff...

Every hour I get a mail from logcheck with a line like Nov 6 12:08:34 wheat fetchnews[13617]: clamping maxage for comp.os.linux.admin to global expire 50 The strange thing is that syslog is filled with similar lines, but this is the only one I get in the report. It is the last such line in each group: # many similar lines deleted Nov 6 12:08:32 wheat fetchnews[13617]: comp.std.c++: considering articles 1...

Under AIX there are three security settings: expires = a fixed date at which an account is no longer valid maxage= weeks before a password expires maxexpires=max weeks during which a password can be changed by a user after expiration AFTER WHICH ACCESS IS NOT ALLOWED Beauty of maxage with expires is, that no manual intervention is required to block inactive users. With maxage=5 and expires=1 an inactive user...

...ng it is business as usual for the driver and it won't broadcast any state change (it doesn't need to). 2) In 'server/upsd.c' the routine 'sstate_dead()' is used to update the driver state. This is where the actual problem is located: > int sstate_dead(upstype *ups, int maxage) > { > time_t now; > double elapsed; > > /* an unconnected ups is always dead */ > if (ups->sock_fd == -1) > return 1; /* dead */ > > time(&now); > > /* ignore DATAOK/DATASTA...

Hi, I am trying to change a SAS macro to R. here is my code. I get an error at the last line. attach(fram) dset1<-cbind(AGE,BMI,DEATH) > BMIGRP<-cut(BMI,breaks=3,right=TRUE) > AGEGRP<-floor(AGE/10)-2 > dset<-cbind(AGEGRP,BMIGRP,DEATH) > maxage<-max(dset[,1]) > minage<-min(dset[,1]) > #maxcls<-dset[,2] > #mincls<-dset[,2] > nage<-maxage-minage+1 > nclass<-maxcls-mincls+1 > nsub<-nrow(dset) > weight <- matrix(,nage,1) > for ( i in minage:maxage ) + {weight[i-minage+1,1] = sum(std = i)} >...

I've compiled 3.7.1p2 on AIX 5.1 w/pam compiled in, but not enable in the sshd_config. Also applied Darrens 3.7.1p2 patch25. I am having issues w/password aging when maxage is set to anything >0. i dont believe this function was ever working (at least not in 3.5p1). Can anyone verify this? Thanks, Ryan __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree

...6662]: Data for UPS [ups1] is stale - check driver May 5 03:50:47 egbert upsd[96662]: UPS [ups1] data is no longer stale May 5 03:50:47 egbert upsd[96662]: Data for UPS [ups1] is stale - check driver May 5 03:50:50 egbert upsd[96662]: UPS [ups1] data is no longer stale ie 5 messages per second! MAXAGE is 15 seconds, IMO it should be at _least_ that time between complaints of staleness.. Am I misunderstanding what MAXAGE does? -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of the...

...some threads to a similar question posted to the R-Help list in October last year. Because I am a bit of a survival analysis and R newbie, I didn't really understand the discussion thread. I've been working with a Weibull distribution, thus: >leafsurv.weibull<-survreg(Surv(minage, maxage, censorcode, type = >"interval")~1, dist = "weib") And I guess I'd like to be able to do something that's the equivalent of >leafsurv.gamma<-survreg(Surv(minage, maxage, censorcode, type = >"interval")~1, dist = "gamma") At least one o...

...: NEW Severity: critical Priority: P2 Component: Miscellaneous AssignedTo: openssh-bugs at mindrot.org ReportedBy: gokoyev at us.ibm.com There appears to be a problem with SSH on AIX 5.1 on systems running secldap client (secldapclntd): ssh ignores the maxage attribute specified for the SYSTEM=LDAP users in the ldap directory. Instead ssh is looking for the maxage attribute in the /etc/security/user and the 'lastupdate' in the /etc/security/passwd. If the default stanza in the /etc/security/user does not contain maxage the LDAP user never gets...

...return 0; } + } + + /* + * Check AIX password expiry. Only check when running as root. + * Unpriv'ed users can't access /etc/security/passwd or + * /etc/security/user so passwdexpired will always fail. + */ + if (geteuid() == 0) { + char *msg, *user = pw->pw_name; + int result, maxage, result2, maxexpired; + struct userpw *upw; + + /* + * Check if password has been expired too long. In this case, + * passwdexpired still returns 1 but /bin/passwd will fail + * while still returning a successiful status, allowing the + * login. So, we deny these login attempts here. +...

...return 0; } + } + + /* + * Check AIX password expiry. Only check when running as root. + * Unpriv'ed users can't access /etc/security/passwd or + * /etc/security/user so passwdexpired will always fail. + */ + if (geteuid() == 0) { + char *msg, *user = pw->pw_name; + int result, maxage, result2, maxexpired; + struct userpw *upw; + + /* + * Check if password has been expired too long. In this case, + * passwdexpired still returns 1 but /bin/passwd will fail + * while still returning a successiful status, allowing the + * login. So, we deny these login attempts here. +...

...w do I change the polling time that nut uses to poll the device to match that of the serial port? The reason I'd like to is I am not going to see any power alerts for unless there is a power outage for longer than 15-30 seconds. I've checked the FAQ on this, do I have to change the 'MAXAGE' parameter to force more frequent updates? Justin.

...07]: Poll UPS [apc620 at localhost] failed - Data stale Jun 6 13:28:50 hell upsmon[607]: Executing automatic power-fail shutdown Jun 6 13:28:50 hell upsmon[607]: Auto logout and shutdown proceeding So it appears upsd lost communication with the UPS, but the real problem was that after the 15 sec MAXAGE period, upsmon decided it was necessary to shutdown. Why? Any ideas?

...status: active tap0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500 ether 00:bd:3e:24:00:00 bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 ether ea:8b:1f:65:2a:5c id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: tap0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP> ifmaxaddr 0 port 7 priority 128 path cost 2000000 member: em0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>...

Hi, I have the above UPS connected to a FreeBSD 6.2 box and it shows 'data stale' very frequently (every few minutes). I have tried the usual trick of setting maxage, poll interval, etc etc but to no avail. When I wind up logging I see (on mge-shut) entering shut_get_report(id: 0d, len: 1800) shut_wait_ack(): ACK received entering shut_get_report(id: 16, len: 1800) shut_wait_ack(): ACK received entering shut_get_report(id: 17, len: 1800) shut_wait_ack(): ACK...

Hello, I'm using driver newhidups with APC Back-UPS CS 500. Most things works fine except the following: After I disconnect the UPS the upsd write "Data for UPS [apc] is stale - check driver" in /var/log/messages. In the same second it tells "UPS [apc] data is no longer stale". This repeats all the time the ups is disconnected: Jan 25 14:45:03 degpn026w226 kernel: usb

...The testing below is done on the trunk version. My ups.conf: [mge-nova] driver=usbhid-ups port=auto desc="MGE Nova 600VA on Bozo" vendorid = 0463 pollinterval = 30 upsd.conf: ACL all 0.0.0.0/0 ACL localhost 127.0.0.1/32 ACCEPT localhost REJECT all MAXAGE 60 usbdevs -vd: Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 uhub0 port 1 addr 2: low speed, power 20 mA, config 1, NOVA AVR(0xffff), MGE UPS SYSTEMS(0x0463), rev 0.01 ugen0 When I start up the usbhid-ups driver manually it...

...The testing below is done on the trunk version. My ups.conf: [mge-nova] driver=usbhid-ups port=auto desc="MGE Nova 600VA on Bozo" vendorid = 0463 pollinterval = 30 upsd.conf: ACL all 0.0.0.0/0 ACL localhost 127.0.0.1/32 ACCEPT localhost REJECT all MAXAGE 60 usbdevs -vd: Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 uhub0 port 1 addr 2: low speed, power 20 mA, config 1, NOVA AVR(0xffff), MGE UPS SYSTEMS(0x0463), rev 0.01 ugen0 When I start up the usbhid-ups driver manually it...

...some threads to a similar question posted to the R-Help list in October last year. Because I am a bit of a survival analysis and R newbie, I didn't really understand the discussion thread. I've been working with a Weibull distribution, thus: >leafsurv.weibull<-survreg(Surv(minage, maxage, censorcode, type = "interval")~1, dist = "weib") And I guess I'd like to be able to do something that's the equivalent of >leafsurv.gamma<-survreg(Surv(minage, maxage, censorcode, type = "interval")~1, dist = "gamma") At least one of the R-h...