Citeren Arnaud Quette :
I guess I see the scanning code as a stopgap way to contact "legacy"
servers (or what would be legacy after some discovery protocol like mDNS is
set up), and either timeouts or non-blocking is just a kludge to make that
work a little better. And isn't opening a non-blocki
Citeren "Stuart D. Gathman" :
That is a very good idea. Use some other port scanning code to narrow down
ports to try instead of corrupting upscli_connect with complications not
needed for normal operation.
This still leaves me with one question - being able to auto-detect the
upsd servers
Citeren Michal Soltys :
Those two commands happen only once before the actual loop is in
effect, during the initialization stage - in upsdrv_initinfo(). It's
the only place where such large delay is used. Note this is only the
max possible delay, the read will return as quickly as possible
Citeren Charles Lepple :
For the purpose of auto-detecting servers I'd propose to resurrect
the UDP code and broadcast the servers presence once every 10
seconds or so. Yes, this has its drawbacks too (to make sure the
broadcasts reach the potential clients), but this has the advantage
to
Citeren Charles Lepple :
I guess I see the scanning code as a stopgap way to contact "legacy"
servers (or what would be legacy after some discovery protocol like
mDNS is set up), and either timeouts or non-blocking is just a
kludge to make that work a little better. And isn't opening a
no
Citeren Stuart D Gathman :
Your test is with localhost - so any non-existent socket would get
immediately rejected. The nut scanner has to deal with hosts on the
network. If they send an ICMP reject, then there is no need for a
timeout. But it is very common for a host to simply "eat" at
Citeren Michal Soltys :
@@ -417,10 +414,12 @@
if (flags & SER_CC) {
iset = IGN_CCCHARS;
aset = "";
+ sec = 6; usec = 0;
}
if (flags & SER_CS) {
iset = IGN_CSCHARS;
aset = "";
+ sec
Citeren Michal Soltys :
@@ -251,14 +251,14 @@
if (do_lock_port) {
errno = 0;
ret = 0;
-#ifdef HAVE_UU_LOCK
+ #ifdef HAVE_UU_LOCK
ret = uu_lock(xbasename(device_path));
-#elif defined(HAVE_FLOCK)
+ #elif defined(H
Citeren Michal Soltys :
Log:
apcsmart: allow tearing down/setting up serial connection during
normal activity;
If this is needed at all (why?), I don't think this should be handled
at driver level, but this would need to be in the serial.c library.
Opening/closing a serial port is indepe
Citeren Frédéric Bohé :
I am currently working on the nut scanner. For detecting available upsd
on the network, I rely on upscli_connect. The problem with this function
is that it calls a blocking "connect" function.
This is a serious problem, not only for the nut-scanner but for
basically
Citeren Frederic BOHE :
Modified: branches/nut-scanner/tools/nut-scanner/scan_snmp.c
==
--- branches/nut-scanner/tools/nut-scanner/scan_snmp.c Fri Jun 17
08:12:00 2011 (r3047)
+++ branches/nut-scanner/tools/nut-scanner
Citeren "Christian \"Eddie\" Dost" :
The basic differences in protocol are:
There is no "I" command, but a "FW?" command to request firmware
version. "Q1" and "F" are there.
Is the reply format the same? If so, this is trivial to add in the
blazer.c global 'command' structure, by appendin
Citeren Charles Lepple :
This seems ambitious for a few months. Then again, there's the old
quote about the person saying it can't be done shouldn't get in the
way of the person who is making it happen :-)
Full ack. I'm not sure how much time I can spend on NUT, but
especially the Windows p
Citeren Arnaud Quette :
I have received documentation about the protocol of the Zinto A UPSs by
Online USV-Systeme and wrote a driver to monitor and configure my UPS. This
is based heavily on the blazer driver,
Arjen, the blazer* author, will probably jump on this thread when he has
some spare
Citeren "Keven L. Ates" :
Rewrite anyone?
Just a quick question, do you have a clue what PID files are used for?
Best regards, Arjen
--
Please keep list traffic on the list (off-list replies will be rejected)
___
Nut-upsdev mailing list
Nut-upsde
Citeren Arnaud Quette :
apart if I've missed something, I've not seen this 'upsilon' patch (well, a
reworked version) make its way in the trunk...
It's definitly not going to be named upsilon, since that's another
name for the underlying protocol (Q1, Megatec, whatever). The
subdrivers in
Citeren Aurélien Grenotton :
After some investigation, they almost use the krauler-type
communication already supported in the blazer_usb driver. However, the
UPS won't reply if the language ID is not 0x4095...
Therefore, I cloned the krauler_command, adding the language ID and
unicode to ASCII
Citeren Arnaud Quette :
Log:
Trim extraneous end-of-line, in buggy HID string tables, which
results in upsc breaking the communication pipe (Ubuntu bug #753661)
We have 'rtrim' to do this:
- return buf;
+ return rtrim(buf, '\n');
Best regards, Arjen
--
Please keep list traffic on the list
Citeren Arnaud Quette :
we (Eaton) have created a new data to expose efficiency of the UPS
(basically it is the ratio of the output current on the input current).
I know that at least APC should also provide it on some units, since I've
seen evidence in an EPA presentation [1].
So I'd like to c
Citeren Danilo Godec :
If the UPS really only uses the RX and TX pins, the setting of
'cablepower' is irrelevant.
Yes, the supplied RS232 cable only has three connected pins. Without
setting 'cablepower=none', the driver didn't detect the UPS.
Again, the driver itself doesn't care about this
Citeren Danilo Godec :
The UPS has both RS232 and USB connection. To use the RS232 connection,
I had to use the 'cablepower = none' as the UPS is using only RX, TX and
GND pins.
If the UPS really only uses the RX and TX pins, the setting of
'cablepower' is irrelevant.
So my 'usp.conf' was
Citeren Arnaud Quette :
just to revive the static code analysis thread...
It would be nice if you could expose your ideas and the results of your
tests.
Also, apart from Splint, have you tested any other systems?
From what I see, Splint and Frama-C are probably the most interesting.
Well, the
Citeren Arnaud Quette :
@Arjen: if you want to test some possible fixes, you can commit on the HPUX
branch, so that Chetan can test it without the need for buildbot slaves.
The problem has already been fixed in the trunk, by removal of the
AX_CREATE_STDINT_H macro and relying on either or
I doubt we still need to create our own fixed width integer types. We
already expect IEEE Std 1003.1-2001 compliance, so the availability of
either or is implied.
Best regards, Arjen
--
Please keep list traffic on the list (off-list replies will be rejected)
__
Citeren Frederic BOHE :
+REM copy DLL files from system
+copy /Y c:\mingw\msys\1.0\bin\msys-1.0.dll .\ImageFiles\Others
+copy /Y c:\mingw\msys\1.0\bin\msys-crypto-1.0.0.dll .\ImageFiles\Others
+copy /Y c:\mingw\msys\1.0\bin\msys-ssl-1.0.0.dll .\ImageFiles\Others
+copy /Y c:\mingw\bin\libgnurx-0.
Chetan,
Could you check the contents of the include/nut-stdint.h file, to see
why there are compilation warnings on the HP-UX buildbot?
Best regards, Arjen
--
Please keep list traffic on the list (off-list replies will be rejected)
___
Nut-upsdev
Citeren John Bayly :
I'll look into how that works, thanks. These look like they do
exactly the job for specifying the delays for the switched outlets
(outlet.1.delay.start).
I don't think so. Why don't you just use 'upsrw' to change these
values? These are supposed to be R/W values in th
Citeren John Bayly :
Are there any plans to allow us to specify UPS variables in ups.conf, eg:
We already support this (as a hidden feature) since nut-2.4.0, where
it is possible to set
default. = value (default to value if UPS doesn't report this)
override. = value (same, but over
Citeren Michal Soltys :
The only "problematic" case is #3, and the only way I see currently
is through checking the flag - as checking if the variable already
exists (which implies being present in .conf file) is not enough.
And if I poll such variable either way, user's override is lost -
Citeren Michal Soltys :
As we want the user to be able do issue all shutdown methods manually,
adjust sdcmd_*() to use STAT_INSTCMD_{HANDLED,FAILED}, so they can
be used directly.
The above is a good idea.
Also minor text corrections, and APC specific command renames.
This isn't. You reall
Citeren Michal Soltys :
This delay is meant for multicharacter commands, besides
we always guarantee delay by other means - so do the stuff properly.
[...]
upsdebugx(1, "On-line - forcing OB temporarily");
ser_send_char(upsfd, 'U');
- usleep(UPSD
Citeren Michal Soltys :
Signed-off-by: Michal Soltys
---
drivers/apcsmart.c | 93
+++-
1 files changed, 84 insertions(+), 9 deletions(-)
Committed with changes. Note that we prefer to have explanations of
variables in the manual pages, r
Citeren Chuck Anderson :
On Sat, Mar 05, 2011 at 11:38:18AM +0100, Michal Soltys wrote:
Signed-off-by: Michal Soltys
---
drivers/apcsmart.h | 28 +++-
1 files changed, 15 insertions(+), 13 deletions(-)
Could you please integrate my minor compat additions with your
Citeren Michal Soltys :
APC_USERCTRL - allows permanent overriding of the variable. Meaning
even if the ups supports reading and/or writing it, the driver will not
allow it (actually it will behave as if the variable wasn't supported at
all). This guarantees that the value set by the user in the
Citeren Michal Soltys :
In cases such as immutable flag over readable value, we have
to be able to acquire this info at driver level (to e.g. avoid
polling, if user defined a variable with 'override' prefix).
I'm not sure I like this. While it may seem a waste of effort to poll
for a variabl
Citeren Michal Soltys :
Follow up from previous thread:
http://www.mail-archive.com/nut-upsdev@lists.alioth.debian.org/msg02331.html
Main differences is that V3 is split into many small patches, so the
reviewing
changes should be much easier. There're also a few additional
changes in late
Please use the mailinglist to ask for support.
- Forwarded message from siwin...@ever.com.pl -
Date: Mon, 21 Feb 2011 13:21:28 +0100
From: Szymon Iwiński
Subject: "Ever" Company UPS drivers
To: nut-upsdev-ow...@lists.alioth.debian.org
Dear NUT Developers,
First o
Citeren Michal Soltys :
the likely options are:
- handle this at driver level - e.g. preserve the immutable flag if
already set without setting rw (if necessary, e.g. in apcsmart if
ignorelb is set), ignore polling, adjust the code so it works fine,
etc.
- go back to minbatt/mintime
- ad
Citeren Michal Soltys :
So, any +/- comments about this approach ?
The reason why it is taking me so long to adopt this, is the reason
that (although you separated this is three chunks) the changes to the
apcsmart driver require to change the LB processing at the same time.
I'd prefer to
Citeren Richard Gerth :
I'd be happy to do testing.
Just let me know when...
In order to get some useful feedback for the -pre versions may I
suggest to subscribe people that are willing to test upcoming releases
to 'nut-upsannounce'? Currently, there seems to be nothing but spam in
the
Citeren Richard Gerth :
Thank you for looking into this. And thank you (to you and the other
developers) for NUT -- it's fantastic to have such a great open source
UPS application.
Would you be willing/able to test future releases of NUT? One thing
that we're currently lacking is a group o
Citeren Richard Gerth :
I'm using openSUSE 11.2
My usblibs are thus:
bach:/usr/lib # ls -l libusb*
lrwxrwxrwx 1 root root19 Jan 11 2010 libusb-0.1.so.4 ->
libusb-0.1.so.4.4.4*
-rwxr-xr-x 1 root root 17940 Oct 23 2009 libusb-0.1.so.4.4.4*
lrwxrwxrwx 1 root root19 Jan 11 2010 libusb-1.
Citeren Philip Tait :
Would appreciate guidance on getting started generating a MIB-to-NUT
mapping (tools, etc):
OS: CentOS 5.5
NUT version 2.6.0
Assuming that you're able to successfully build NUT from sources,
you're all set. Unlike USB HID PDC subdrivers, we have no automated
tools av
Citeren Richard Gerth :
I have a Cyberpower 850AVRLCD ups, and I'm running NUT 2.6.0 (and
also tried 2.4.1 and 2.4.3). I suspect that the problem I was having
would affect anyone using the usbhid-ups driver, but since I have only
the one UPS, I don't know for sure.
It doesn't affect anyone.
Citeren Eric Wilde :
Fair enough. The germane portion of the config.log file is:
configure:7703: checking for init_snmp
configure:7703: gcc -o conftest -DINET6 -O2 -fmessage-length=0
-Wall -D_FORTIFY_SOURCE=2 -g -fno-strict-aliasing
-fstack-protector-all -Dlinux -I/usr/include/rpm -I/u
Citeren Eric Wilde :
Attempting to install the SNMP driver on Enterprise SuSE 10.0. The
version of NUT is 2.6.0.
[...]
The claim that the library doesn't exist is incorrect.
The script is not able to find the required libraries, it doesn't say
they don't exist. In order to find out what
Citeren Michal Soltys :
Then, the other options, that is if:
- additional LB checks are to remain in main.c
- new apcsmart's "ignorelb" option to have the desired effect
- the checks are to use well known battery.{runtime,charge}.low, and
be universal at the same time
the likely options are
Citeren Michal Soltys :
The point is about override.* values, as they are implemented
through immutable flag. If I added for example
[apctest]
override.battery.minutes.low = 0
or
override.battery.minutes.low = -1
How is this supposed to work? I can imagine shutting down earl
Citeren Frederic BOHE :
- res = w32_serial_read(fd,buf,buflen,timeout);
+ res = w32_serial_read((serial_handler_t *)fd,buf,buflen,timeout);
Rather than casting away the const (which may not be possible with
certain strict compiler flags), it is better to modify the prototype
an
Citeren Frederic BOHE :
Modified: branches/windows_port/include/wincompat.h
==
--- branches/windows_port/include/wincompat.h Wed Jan 26 15:05:16
2011 (r2852)
+++ branches/windows_port/include/wincompat.h Wed Jan 26 15:
Citeren Michal Soltys :
I think I found one bug with flag handling though:
dstate_setflags() uses = when setting new flags. This has a side
effect, that any later setflags() call will override earlier flags
(as expected), but that also includes the immutable flag (and that
we don't want,
Citeren rasengan rootish :
So basically what you have in mind is putting such checks in
main.c's loop somewhere after upsdrv_updateinfo() call, and then
updating ups.status ?
Yes.
That would also warrant adding options enabling such functionality
(separately for charge and runtime), as n
Citeren Michal Soltys :
Summary:
- new driver options: ignorelb, minbatt, mintime, wugrace, advorder
- expanded: sdtype
- few more types in compatibility table
- minor fixes and adjustments
First of all, thanks for the effort of working on this driver. The
lack of an active developer for AP
Citeren Frédéric Bohé :
Thanks for the clarification.
I just tried to compile and I have an error on this line, not sure how
to fix that.
common.c: In function 'confpath':
common.c:443:2: error: initializer element is not constant
common.c: In function 'dflt_statepath':
common.c:454:2: error: i
Citeren Frédéric Bohé :
+ static const char *path = getfullpath(PATH_ETC);
getfullpath is allocating memory with xstrdup. Doesn't this line produce
a memory leak ?
Nope.
Whenever you do an assignment to a static variable, this is only done
once. So the getfullpath() function will be
Citeren Michal Soltys :
- in upsdrv_shutdown(), there're loads of printfs - they kinda look
like a leftover from older debug times. Shouldn't they be changed
into upsdebugx() or upslogx() ?
This is pointless. The part of the code is typically run near the end
of the system halt script. By
Citeren Frederic BOHE :
--- branches/windows_port/scripts/Windows/wininit.c Tue Jan 18
08:57:03 2011 (r2838)
+++ branches/windows_port/scripts/Windows/wininit.c Tue Jan 18
10:05:01 2011 (r2839)
@@ -285,8 +285,11 @@
charfn[SMALLBUF];
FILE*nutf;
charbuf[SMAL
Citeren "Stuart D. Gathman" :
One advantage to client certs is that it avoids weak passwords - but
the client could protect their private key with a weak password.
In case of upsmon, this is a huge waste of effort. The upsmon client
has very little (master) or none at all (slave) influence o
Citeren emilien...@eaton.com:
Reverting commit r2819 seems fixing the problem.
Index: /trunk/clients/upsclient.c
===
--- /trunk/clients/upsclient.c (revision 2724)
+++ /trunk/clients/upsclient.c (revision 2819)
@@ -387,5 +387,5 @@
Citeren emilien...@eaton.com:
With a clean trunk checkout, compile and installation; and with the
following config :
upsmon.conf:
CERTPATH /usr/local/ups/etc/cert/
CERTVERIFY 1
FORCESSL 1
First off, you're not supposed to use both CERTVERIFY and FORCESSL.
FORCESSL is intended to be used in
Citeren emilien...@eaton.com:
If you think that login/password is enought to authenticate clients,
I can remove SSL client authentication parts. It is not a problem.
Well, I don't think it adds something, other than another option that
we'll get loads of questions about.
[...]
I'm still
Citeren emilien...@eaton.com:
I have added client certificate checking mainly to avoid
man-in-the-middle attacks or identity usurpation.
A man-in-the-middle attack is impossible if you verify the server
certificate (CERTVERIFY 1). If someone manages to stage a
man-in-the-middle attack by
While browsing the sources of the nss-ssl-port sources I noticed that
client certificates were added. What is the reason behind this? As far
as I can see, using a server certificate and validating it in the
upsmon client should provide us with a secure channel. Authorizations
for the server
Citeren emilien...@eaton.com:
What about CERTPATH in upsmon.conf ?
Don't touch that. This is indeed a path... :-)
This is where the upsmon client looks for the CA that signed the
certificate presented by the server. So unlike the server, this is
indeed a directory that holds the trusted C
Citeren Turronix :
If snmp-ups is started when the UPS is not reachable (e.g. we have a
slow switch that drops the first 30 seconds of communication at
computer boot or interface startup) the snmp-ups suicides (or
crashes?) and apparently there is nothing to re-launch it
automatically so
Citeren emilien...@eaton.com:
- netssl.c provides some configuration function, one per directive,
CERTREQUEST argument parsing is done in
conf.c:parse_upsd_conf_args() and the dedicated nss configuration
function is called with the corresponding value (IMHO best way
because best decoupli
Citeren Arnaud Quette :
I would also add that documentation will also be in that way:
UPGRADING will inform existing users to move to CERTPATH, and user
documentation will note CERTFILE as deprecated in favor of CERTPATH.
I couldn't disagree more. Using CERTPATH would hint users that they
ne
Citeren emilien...@eaton.com:
The main reason is to homogenize directive names between apps
(mainly upsmon which uses CERTPATH and upsd which uses CERTNAME) to
set the same property.
Why? The use of CERTFILE (OpenSSL only) and
CERTPATH/CERTIDENT/CERTREQUEST (NSS only) is completely differ
Citeren Emilien Kia :
Modified: branches/ssl-nss-port/server/conf.c
==
--- branches/ssl-nss-port/server/conf.c Wed Jan 5 21:12:03 2011(r2803)
+++ branches/ssl-nss-port/server/conf.c Thu Jan 6 10:27:55 2011
Citeren Emilien Kia :
Author: emilienkia-guest
Date: Fri Jan 7 14:44:25 2011
New Revision: 2809
URL: http://trac.networkupstools.org/projects/nut/changeset/2809
Log:
Deprecate CERTFILE conf var to the benefit of CERTPATH : homogenize
conf directive names.
Modified:
branches/ssl-nss-port
Citeren Arnaud Quette :
I would be grateful if another developer can pick this up.
I'll check that Arjen.
Never mind, I found the time today to make the necessary changes. I
just committed the updated driver.
Best regards, Arjen
--
Please keep list traffic on the list (off-list replies wi
I've just committed a rough version of the idowell-hid subdriver to
the trunk. It is already integrated in the usbhid-ups, but I lack the
time to complete the NUT to HID mapping in it. The following message
on the nut-upsuser mailinglist should provide enough clues to add most
of them:
Citeren Kjell Claesson :
Arjen can you enlighten me about the function of the blazer upsdrv_shutdown
function.
We first stop any pending shutdowns and then send it a shutdown with
delay command.
I think they are in the wrong order.
What makes you think so? This has been like this for qu
Citeren Rafael JesúsAlcántaraPérez :
Obviously, it is not supported (at least not today). Do you know if it is
"compatible" with yours?
See 'man 8 usbhid-ups' for a solution to use the usbhid-ups driver. If
the driver detects the UPS, post the output of 'upsc' here, so that we
can make thi
Citeren Arnaud Quette :
Author: aquette
Date: Fri Dec 17 23:32:20 2010
New Revision: 2748
URL: http://trac.networkupstools.org/projects/nut/changeset/2748
Log:
--with-doc=auto now behave depending on AsciiDoc presence
Instead of building whatever can be build (depending on the versions
foun
Citeren John Bayly :
I've discovered an issue (which may be unique to my UPS) with this commit.
init_communication now returns -1, instead of 0 if it failed to read
the manufacturer info, this makes sense after all.
Not entirely. Previously, the init_communication() function would try
to r
Citeren Arnaud Quette :
Author: aquette
Date: Sat Dec 11 12:31:21 2010
New Revision: 2731
URL: http://trac.networkupstools.org/projects/nut/changeset/2731
Log:
Complete the list of Subversion ignored files, with AsciiDoc
generated contents (no functional changes)
Is there a particular reaso
Citeren Arnaud Quette :
Date: Thu, 09 Dec 2010 14:01:14 +
Subject: svn commit r2726 - in branches/windows_port: common drivers include
Author: fbohe-guest
Date: Thu Dec 9 14:01:07 2010
New Revision: 2726
URL: http://trac.networkupstools.org/projects/nut/changeset/2726
Log:
More work on ser
Citeren Charles Lepple :
If you are trying to eliminate direct dependencies on the old
libusb-0.1 package, there is always the libusb-0.1-compat package. I
believe that FreeBSD 8+ has incorporated that into their libusb-1.0
API for the new USB stack, and aside from some changes in our
con
Citeren Michal Hlavinka :
I've been asked to find out some answers from libusb maintainer, so I'm
forwarding them:
- Why nut uses legacy libusb-0.1 api and not libusb 1.0 ?
Well, mostly because at the time we started adding USB support to NUT,
libusb-0.1 was all there is.
- Is there any
Citeren vasos :
i just want to share a quick n dirty patch to support nominal power
in APC ups's.
I was not sure about the name of the nut key and put it to ups.power.nominal
Thanks for your patch. The naming scheme of NUT can be found in
'docs/new-names.txt', where you'll find that the co
For everybody wondering about the following warning message in all
buildbots (except openSUSE):
../../server/ssl.c:134: warning: passing argument 1 of 'SSL_CTX_new'
discards qualifiers from pointer target type
This was changed between 0.9.8n and 1.0.0 [29 Mar 2010]:
*) Let the TLSv1_met
Citeren Stephen Beahm :
Parsing bug summary
---
working /etc/hosts.allow:
upsd127.0.0.1 [::1] : ALLOW
broken in /etc/hosts.allow:
upsdlocalhost : ALLOW
It looks like upsd originally intended to match nut username with system
username?
No. We want
Citeren Arnaud Quette :
It also seems, after an update round on my side, that the standardization on
nss pushed by Fedora and Suse has not yet made its way.
I can't speak for Fedora, but on the latest released version of
openSUSE, there is very little progress towards standardization on
NS
Citeren Arnaud Quette :
just to clearly disambiguate the situation: as from now, we'll be abandoning
the nss-compat work.
After playing with it for a couple of days, I fully agree.
Arjen: if you however want to continue testing this approach (which IMHO
would be a waste of time), could you p
Citeren Arnaud Quette :
dnl --
-dnl Check for --with-ssl
+dnl Check for with-ssl, and --with-nss or --with-openssl
+dnl Only one can be enabled at a time, with a preference for Mozilla NSS
+dnl if both are available
Having lo
Citeren Arjen de Korte :
I don't recall that we ever discussed the possibility of adding NSS
support by using the 'nss_compat_ossl' OpenSSL compatibility layer.
Just to be sure, I added this to see if this is a workable solution.
On my (openSUSE) system this seems to build w
Citeren Arjen de Korte :
Log:
Use the 'nss_compat_ossl' compatibility layer to use the Mozilla NSS
library instead of OpenSSL (we might want to include native support
in the future, but this will at least allow a quick migration for
testing purposes)
I don't reca
Citeren Frederic BOHE :
Author: fbohe-guest
Date: Fri Nov 26 14:01:35 2010
New Revision: 2705
URL: http://trac.networkupstools.org/projects/nut/changeset/2705
Log:
Add regex library for drivers (by Arnaud Quette)
Modified:
branches/windows_port/drivers/Makefile.am
Why is this needed? The
Citeren Charles Lepple :
The one thing I'm still not sure about is when the kernels changed
over - it seems like udev changed to ATTRS first.
I'm not sure that is really relevant if we know the udev version that
was used for building the kernel.
Also, I didn't know that udev had a pkg-con
Citeren Charles Lepple :
Looks like Ubuntu changed to the udev which supports ATTRS sometime
between 6.06 and 8.04 (2006 and 2008), but I haven't tracked down
when the kernels changed over.
If the system supports pkg-config, checking if the version is < 098
should be able to tell if we mu
Citeren Arnaud Quette :
FYI (mostly Charles and Arjen), a2x version has just been bumped to 8.6.3 in
their trunk.
So we will be able revert r2686
The released version is now also available, so I upped the required
versions for both asciidoc and a2x to 8.6.3. I installed the latest
version
Citeren Arnaud Quette :
Log:
Exclude -I. and extra developer warning flags with Net-SNMP support enabled
(using them is the responsibility of the NUT developers)
Modified:
branches/AsciiDoc/m4/nut_check_libnetsnmp.m4
Arjen,
was this really intended to target the AsciiDoc branch?
Yes.
Citeren Pawel Sikora :
(gdb) up
#1 blazer_status (cmd=) at blazer.c:214
(gdb) p val
$1 = 0x0
Excellent, I missed checking for a NULL pointer somewhere in the code.
Good catch!
199| for (i = 0, val = strtok_r(buf+1, " ", &last);
status[i].var; i++, val = strtok_r(NULL, " \r\n",
Citeren Arnaud Quette :
we could consider a slightly more complex approach where older asciidoc
detection would only enable the single page html, and pdf version (if
dblatex is also present).
I'll see what I can do. I already noticed that at least some of the
documentation will build with t
Citeren trantore :
With my system I don't have any problem. Please, ask for patch acceptance. I
belive that is better to fix any bug after several users begin to use NUT.
It might be included in future versions, but definitely not before we
have evaluated if this doesn't break existing syste
Citeren Arnaud Quette :
indeed, asciidoc / a2x return the version in the form " ",
which implies that we have to strip the part.
That indeed is the problem. As long as the appname doesn't contain
numerals, the AX_COMPARE_VERSION macro will strip it for us (so this
isn't a problem), but th
Citeren Arjen de Korte :
Most likely we'll need to strip the initial part of the return from
the 'a2x 8.6.1' version string, since that will probably be treated
as '2.8.6.1' now (it works when I lower the requirement to 1.0.0).
I'll see what I can do...
Wel
Citeren Charles Lepple :
Log:
Add checking minimum required version for AsciiDoc tools
I noticed that somewhere around this commit, the documentation
stopped being built by default in BuildBot.
Before I go digging too far, should I just add "--with-doc=auto" to
the configure parameters,
Citeren Frédéric Bohé :
I am trying to merge the windows_port branch with trunk and I have some
issues.
I'm not sure if that's a good idea at the moment. If I'm not mistaken,
we're about to release a new stable version soon.
First, getaddrinfo seems to be supported on Win32 platforms only
1 - 100 of 627 matches
Mail list logo
