Displaying 20 results from an estimated 6000 matches similar to: "Update to the NUT Team members"
2010 Nov 25
3
Announce: new team member (to work on Mozilla NSS port)
Dear fellows,
As you have probably seen, NUT has had a recent boost through the help of
Eaton.
Frederic Bohe (contractor for Eaton France) has worked on Augeas, and is now
working the Windows port.
Chetan Agarwal, seconded by Prashi Gandi (both from Eaton India) are working
on XCP and quality / validation related projects.
I'm now pleased to announce that Emilien Kia (contractor for Eaton
2012 Oct 12
2
NSS support in trunk (was: NSS branch pull request)
2012/10/12 Emilien Kia <kiae.dev at gmail.com>
> Hi guys,
>
Hi Emilien and the list,
This is a pull request to finally merge NSS feature in nut trunk:
> https://github.com/clepple/nut/pull/3
>
I'd like to take a moment to shed some more light on this important
development, which lasted 3 years:
- the initial
2018 Jul 11
2
Adding drivers to NUT?
Dear Daniele,
thanks a lot for your support, i have some things that are not so clear for me:
- I can send you the whole sources for our UPSs, do you need only Headers and C files or also other files (i suppose Driver list)?
- Seen that we had some problems with the Blazer driver (the battery voltage calculation were not correct for our UPSs) we copied it and modified a bit while changing the
2018 Feb 28
2
Work around for power recycling after shutdown.return - TSSHARA UPS - nutdrv_qx driver - megatec protocol
Answers bellow.
2018-02-28 1:41 GMT-03:00 Daniele Pezzini <hyouko at gmail.com>:
> 2018-02-27 14:51 GMT+01:00 Jairo Rotava <jairo.rotava at gmail.com>:
> > Hi,
> >
> > I had an issue where after returning the power from a shutdown.return the
> > ups would do another shutdown.return during the boot, and kept this
> forever.
> > After some
2018 Jul 18
2
Adding drivers to NUT?
Dear Daniele,
I'm trying to create a subdriver for 'nutdrv_qx' instead of modifying the Blazer as you suggested, but i honestly don't understand how to integrate usb-serial devices (some of our UPSs have USB but serial protocol Q1). i understand the serial version but not the USB one.
i also checked the "Claim" function, but i can't see drivers that uses the VID
2018 Jul 24
2
Adding drivers to NUT?
Dear Daniele,
i understand perfectly, i'd like to explain you why we choosed to clone the blazer_usb driver:
some of our devices uses Voltronic Q1 protocol and we tried the Krauler Subdriver (it was the one with the right "commands", Q1, F, etc.), but the issues were 2:
- first: the Krauler Subdriver expects a different number of bytes in answer because in debug i see "Short
2010 Aug 30
0
[LLVMdev] job ad: QA contractor position in Apple's compiler team
This is an advertisement for a QA contractor position in Apple's Clang frontend team. Please forward to anyone who might be interested.
------------
Apple's LLVM compiler team is looking to fill a 6 month QA contractor position to help drive major improvements to our qualification and testing processes for Clang.
Currently we have a semi-automated process for tracking compiler
2010 Nov 28
1
[nut-commits] svn commit r2705 - branches/windows_port/drivers
Citeren Frederic BOHE <fbohe-guest op alioth.debian.org>:
> 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 value of
2011 Jan 18
1
[nut-commits] svn commit r2839 - branches/windows_port/scripts/Windows
Citeren Frederic BOHE <fbohe-guest op alioth.debian.org>:
> --- 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 @@
> char fn[SMALLBUF];
> FILE *nutf;
> char buf[SMALLBUF];
> + const char * conf_path;
>
> -
2011 Jan 26
1
[nut-commits] svn commit r2853 - in branches/windows_port: drivers include
Citeren Frederic BOHE <fbohe-guest op alioth.debian.org>:
> 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:16:09
> 2011 (r2853)
> @@
2011 Mar 17
1
[nut-commits] svn commit r2940 - in branches/windows_port/scripts/Windows/Installer
>
> ---------- Forwarded message ----------
> From: Frederic BOHE <fbohe-guest at alioth.debian.org>
> To: nut-commits at lists.alioth.debian.org
> Date: Wed, 16 Mar 2011 14:57:09 +0000
> Subject: svn commit r2940 - in
> branches/windows_port/scripts/Windows/Installer: . ImageFiles
> ImageFiles/Binary ImageFiles/Others ImageFiles/emptyDir
>
2011 Jan 21
1
End of NSS port
Hi all,
I am pleased to announce that NSS port of NUT is finished.
Port is fully functionnal (same functionnalities as openssl, and a
not-activated-by-default client certificate validation function) and
successfully tested by myself (external tests are pending, Frederic Bohe
is planned for) with a test matrix which will be uploaded to the web
site soon (by Arnaud), tested functionnality by
2012 May 03
1
[nut-commits] svn commit r3554 - branches/windows_port/common
c'est quoi cette chelouzerie ?
je parle de l'ajout du sizeof(DWORD)...
et ce que ce serait pas un str*n*cpy ou s*n*printf la vraie solution ?
Arno
2012/5/3 Frederic BOHE <fbohe-guest at alioth.debian.org>:
> Author: fbohe-guest
> Date: Thu May ?3 08:31:38 2012
> New Revision: 3554
> URL: http://trac.networkupstools.org/projects/nut/changeset/3554
>
> Log:
>
2011 Jun 28
1
[nut-commits] svn commit r3060 - branches/nut-scanner/tools/nut-scanner
2011/6/27 Frederic BOHE <fbohe-guest at alioth.debian.org>
> Author: fbohe-guest
> Date: Mon Jun 27 13:56:51 2011
> New Revision: 3060
> URL: http://trac.networkupstools.org/projects/nut/changeset/3060
>
> Log:
> Add NUT server scan.
>
> (...)
> device_t * scan_snmp(char * start_ip, char * stop_ip,long usec_timeout,
> snmp_security_t * sec);
>
>
2013 Oct 17
0
UPSC based Windows Client
[Please remember to copy the list.]
On Oct 15, 2013, at 8:45 AM, eric kreuwels wrote:
> Hi Charles
>
> Thanks for your answer. Good questions/suggestions. I copied both the WinUPSC and the installer project on my GDRIVE and shared it with you:
> https://docs.google.com/file/d/0B0mSjYYj84-6ZGM4MWZfMnFxbUU/edit?usp=sharing
>
> Archiving WinUPSC in the NUT GitHub would be my
2018 Aug 28
1
Fwd: Forward of moderated message
[forwarded without attachments, for real this time]
> Begin forwarded message:
>
> From: Gabriele TAORMINA <gabriele.taormina at legrand.com <mailto:gabriele.taormina at legrand.com>>
> Subject: Re: [Nut-upsdev] Adding drivers to NUT?
> Date: August 27, 2018 at 6:03:55 AM EDT
> To: Daniele Pezzini <hyouko at gmail.com <mailto:hyouko at gmail.com>>
>
2011 Jun 21
1
[nut-commits] svn commit r3048 - branches/nut-scanner/tools/nut-scanner
Citeren Frederic BOHE <fbohe-guest at alioth.debian.org>:
> 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/scan_snmp.c Tue Jun 21
>
2018 Dec 24
2
Freenas configuration Legrand Daker DK1kVA
Hi all,
I have an UPS by Legrand, model Daker DK 1 kVA, i have tried to use
"nutdrv_qx" driver with usb but have no success.
I will send you all the information you need to try to solve or write
the correct driver.
Hope to be useful.
regards
Andrea
2019 Mar 05
0
How to post a device dump to the DDL?
Daniele, thank you.See attached file.Yuri
-------- Исходное сообщение --------От: Daniele Pezzini <hyouko at gmail.com> Дата: 05.03.2019 3:09 (GMT+03:00) Кому: "Yuri V. Mednitski" <ranger at ranger.ru> Копия: nut-upsuser at alioth-lists.debian.net Тема: Re: [Nut-upsuser] How to post a device dump to the DDL? Either open a pull request on our GitHub
1999 Jul 27
2
NT User can't access share
Folks,
A remote admin is trying to add a contractor account to our NT
domain with limited rights. Unfortunately, everytime the contractor
account is removed from the DomainUsers group, the contractor
encounters the following:
\\nt-nfs-md\IPC$
and the infamous invalid password. Once the user is re-added to the
DomainUsers group, they can access the share fine.
My question is what permissions