similar to: Suspend-to-disk & NUT (solved!)

Hi, I've seen a few emails in the archives about problems polling MGE UPSs via USB under FreeBSD, but unfortunately I didn't find a solution in them that works for me. A few details about my setup.. The UPS is a MGE Nova AVR 600 connected via USB to a FreeBSD 6.2 box. I have tried both the nut port (2.0.5) and the svn trunk but have had no success yet. I am running nut as root to

Hi, I've seen a few emails in the archives about problems polling MGE UPSs via USB under FreeBSD, but unfortunately I didn't find a solution in them that works for me. A few details about my setup.. The UPS is a MGE Nova AVR 600 connected via USB to a FreeBSD 6.2 box. I have tried both the nut port (2.0.5) and the svn trunk but have had no success yet. I am running nut as root to

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():

[...] > I think this output doesn't help very much. This is very helpful. The problem is not in the connection to the driver, upd->data_ok switches between 0 and 1. Only the driver can change this value by repetitively switching between DATASTALE and DATAOK. There is nothing upsd can do about this, this is a driver problem. This is consistent with the observation that all people

I think I found a fix (workaround?) for the above mentioned problem. To summarize shortly, upsd lost communication with the (safenet) driver in case the system wakes up after suspending to disk. Restarting the driver or upsmon did not help, only a restart of upsd did. The attached patch will also solve this, although I'm still not really sure why or whether this will create too much load on

Dear all, I would like to know how can I retrieve a data.frame without the columns that have a partial match name. Let´s say that I have a data.frame with 200 columns and 100 of them have the name "StartX", with X being the unique part for each column name. I want to delete all columns that have the name starting with "Start". I´ve tried to do this but it doesn´t work: >

> Author: adkorte-guest > Date: Mon Jun 25 19:26:09 2007 > New Revision: 988 > > Log: > Update to reflect changes in the way we deal with dstate_dataok() and > dstate_datastale(). > > Historically it was needed to call dstate_dataok() regularly, to prevent > staleness warnings. This is no longer needed, now the server will PING > drivers it has not heard of

Hi, I have had a long standing problem with NUT talking to 110V MGE UPSs on FreeBSD, I was recently investigating again and noticed that upsd seems overly noisy, eg.. May 5 03:50:36 egbert upsd[96662]: UPS [ups1] data is no longer stale May 5 03:50:36 egbert upsd[96662]: Data for UPS [ups1] is stale - check driver May 5 03:50:36 egbert upsd[96662]: UPS [ups1] data is no longer stale May 5

I think I have found a way to deal with the issue of the spurious message on startup of NUT. Before implementing it, I would like to see what the other developers think of this idea. My proposal is not to wait for DUMPDONE in the startup of upsd for a duration of MAXINIT seconds, but rather to send the fake "INIT" status in response to a ups.status request. As soon as DUMPDONE hits, or

[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

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

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

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] >

Hi All. Attached is a patch which adds AIX native password expiry support to sshd. It will only apply to -current and is a subset of the patch I have been working on in the last few months (see bug #14 [1]). It contains code by Pablo Sor, Mark Pitt and Zdenek Tlusty and fixes for bugs reported by many others (see [2] for a full list). It adds a do_tty_change_password function that execs

Hi All. Attached is a patch introduces password expiry handling for AIX (other platforms to follow). It is more or less the same as the previous patch but has been updated to reflect recent changes to auth-passwd.c I'm wondering if the AIX parts of auth.c should be moved to port-aix.c and if the generic password change functions (currently at the end of auth-passwd.c) belong in a separate

http://bugzilla.mindrot.org/show_bug.cgi?id=869 Summary: Password expiration does not work for LDAP users Product: Portable OpenSSH Version: -current Platform: PPC OS/Version: AIX Status: NEW Severity: critical Priority: P2 Component: Miscellaneous AssignedTo: openssh-bugs at mindrot.org

[As posted as Ubuntu Question #184284 on Launchpad] Hi, I try to set up nut (2.4.3) on my Lucid (10.04.3 LTS) to make use of my old but very trusty UPS (Best Power Fortress 660 LI). Yes, this UPS is old (about 16 years), but with its third battery pack last week it is as good as new. It runs perfectly well with Windows XP, Vista and even Windows 7. But not so with Ubuntu and nut. After

Hi All, I've finally found solutions for my previous problems. But since this includes changes in the shared files, I'd like to discuss them here. 1. Driver restart problem. When I start the driver for the first time, everything is ok. But when I want to restart it, problems begin. The driver fails to read Report descriptor for the second time (libusb_open is used to open the device).

Arnaud Quette wrote: > Anyhow, I would more see this as a merge of all these drivers, with > some autodetection or flag/param to switch the mfr/model and maybe > capabilities... Whatever the driver name is, a good thing would be the > name of the protocol or something generic enough, though powermust is > fine. Ok, I made some minor changes to powermust, to make it less

Dear r-help subscribers, A couple of weeks ago I sent the following message to the r-help mail list. It hasn't generated any response, and I could really use some help on this. Anyone able to help? Thanks again, Roger Dungan >> I am working on some survival analysis of some interval censored failure time data in R. I have done similar analysis before using PROC LIFEREG in SAS. In