similar to: release notes for CentOS 5.7

Hello I've created the first version of the ReleaseNotes page for CentOS 6.0 in the wiki. As usual, corrections / additions / translations are welcome. Manuel

On Tue, Mar 22, 2016 at 10:12 AM, Manuel Wolfshant <wolfy at nobugconsulting.ro> wrote: > On 03/22/2016 09:30 AM, Fabian Arrotin wrote: >> >> Hi, >> >> I was having a look at that page, and was wondering what we can do for >> point #3 (Manuals and other documentation) >> As we have no real content for CentOS 6 and 7 , my idea was just to >>

Hi Manuel et.al, Going thru the documentation -- it seems this configuration specific to blazer_ups. https://networkupstools.org/docs/man/blazer_usb.html Kind Regards, Yogesh On Fri, May 15, 2020 at 12:53 PM Manuel Wolfshant <wolfy at nobugconsulting.ro> wrote: > > On 5/15/20 12:13 PM, Yogesh Bhanu wrote: > > [...] > > # Is it possible to calculate /estimate how much

On 9 June 2015 at 07:55, Manuel Wolfshant <wolfy at nobugconsulting.ro> wrote: > <significant snippage> > > Call me picky but I'd rephrase > The CentOS Project ONLY provides updates or other changes for the > latest version of each major branch. > to > The CentOS Project provides updates or other changes ONLY for the > latest version of each major

Hello I've just been hit by one of the chipsets described at http://wiki.centos.org/HardwareList/RealTekRTL8111b. Because a) it does not work with the stock driver included in Centos 5.1 and b) I am very lazy and I do not like manually compiling modules each time a new kernel is installed (not to mention that I never forget anything, except for the important things which always go

Hi Manuel 2017-06-07 14:40 GMT+02:00 Charles Lepple <clepple at gmail.com>: > On Jun 7, 2017, at 5:47 AM, Manuel Wolfshant <wolfy at nobugconsulting.ro> > wrote: > > > > If that matters, the OS is a fully updated CentOS 6.9 and this > (latest stable ) version of nut was packaged by me. The problem appears on > any of the USB ports ( well, I tried the 2 in

Hi Thanks for the reply We have seen the same guest VM freezing on vmware ESXi machine also , so we were interested in know in the internal condition of the guest vm when the freeze happened How can we analyse the core file generated by "virsh dump " Thanks and regards Akshar On Wed, Jan 9, 2019 at 1:58 PM Manuel Wolfshant <wolfy at nobugconsulting.ro> wrote: > On 1/9/19

2017-06-13 17:49 GMT+02:00 Manuel Wolfshant <wolfy at nobugconsulting.ro>: > On 06/13/2017 05:48 PM, Arnaud Quette wrote: > > Hi Manuel > > > Hi Arno > > Hi Manuel > > > 2017-06-07 14:40 GMT+02:00 Charles Lepple <clepple at gmail.com>: > >> On Jun 7, 2017, at 5:47 AM, Manuel Wolfshant <wolfy at nobugconsulting.ro> >> wrote:

On 07/06/2017 02:38 AM, Charles Lepple wrote: > On Jul 5, 2017, at 7:23 PM, Manuel Wolfshant wrote: >>> Manuel: did you happen to regenerate the udev files, or use one of the Buildbot tarballs? We typically don't bother to do that until "make dist" before a release (since the rules files are generated from *.in files based on configure parameters), so your package might

Hi Manuel, thank you for pointing this. I know about upsshed but I have no idea how to let dependable server to discover that another server was shut down. Any examples of such scripts? чт, 17 сент. 2020 г. в 21:00, Manuel Wolfshant <wolfy at nobugconsulting.ro>: > On September 17, 2020 6:09:18 PM GMT+03:00, Kirill Nikonorov < > knikonor at gmail.com> wrote: > >Hello to

Hi Mauel, No dice. The config does not show up config: --8<-- [tripp] driver = usbhid-ups port = auto vendorid = 09ae productid = 2009 bus = 001 desc = "Tripp Lite SMX1000LCD" runtimecal = 660,100,180,50 -->8-- output: --8<-- upsc tripp Init SSL without certificate database battery.charge: 100 battery.runtime: 736 battery.type: PbAc

Not much in the way of configuration…. I’m pretty sure I’ve got it correct. -- Todd Benivegna // todd at benivegna.com On Aug 13, 2020, 8:54 PM -0400, Manuel Wolfshant <wolfy at nobugconsulting.ro>, wrote: > On August 14, 2020 3:46:05 AM GMT+03:00, Todd Benivegna <todd at benivegna.com> wrote: > > So I finally got a test in after I changed my RPi to the master and > >

On 06/13/2017 05:48 PM, Arnaud Quette wrote: > Hi Manuel Hi Arno > > 2017-06-07 14:40 GMT+02:00 Charles Lepple <clepple at gmail.com > <mailto:clepple at gmail.com>>: > > On Jun 7, 2017, at 5:47 AM, Manuel Wolfshant > <wolfy at nobugconsulting.ro <mailto:wolfy at nobugconsulting.ro>> wrote: > > > > If that matters, the

On 6/15/20 2:46 PM, Stephen John Smoogen wrote: > > > On Sun, 14 Jun 2020 at 14:49, Manuel Wolfshant > <wolfy at nobugconsulting.ro <mailto:wolfy at nobugconsulting.ro>> wrote: > > Hello > > > ??? For the past months I've been testing upgrading my Xen hosts > to CentOS 7 and I face an issue for which I need your help to solve. > >

I've eventually installed Manuel's packages (nut and nut-client). When I run the driver as root (for my tripplite ups) I get: /usr/sbin/upsdrvctl start Network UPS Tools - Generic HID driver 0.42 (v2.7.4-418-gb1314c62.7.4.1) USB communication driver (libusb 0.1) 0.33 writepid: fopen /var/run/nut/usbhid-ups-trippliteups.pid: Permission denied Can't claim USB device [09ae:1330]: could

Right, but I don't know what NUT script is actually calling it. I don't know how else I would check. On Tue, Aug 4, 2020 at 10:21 AM Manuel Wolfshant <wolfy at nobugconsulting.ro> wrote: > On 8/4/20 4:16 PM, Todd Benivegna wrote: > > Ok, so now that I think of it, that might not actually work when it is > > not run by me. I guess that it all confirms that it works

On 06/24/2017 04:52 AM, Charles Lepple wrote: > On Jun 23, 2017, at 5:50 PM, Ambrogio Coletti <ambrojohn at gmail.com> wrote: >> "This TrippLite device (09ae:1330) is not (or perhaps not yet) supported by usbhid-ups. [...]" >> but my device (SU2200RTXLCD2U) is supported, as clearly state here. > No, the HCL also mentions "protocol 4001". For Tripp-Lite,

Hi, This is my very first time using CentOS and I find documentation a little bit confusing. For example, I don't know which iso image suits my needs, isn't adding big, shining red link "READ THIS IF YOU DON'T KNOW WHICH ISO SHOULD YOU CHOOSE" a good idea? 'README' file on mirrors with instructions would also be nice. If there already is one, I wasn't able to

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/05/2015 01:52 PM, Manuel Wolfshant wrote: > On 06/05/2015 08:30 PM, Karsten Wade wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> >> Folks: >> >> A few of us (KB, Johnny, myself) have begun work on updating the >> main FAQs on the CentOS wiki. Mainly that means looking over and >> updating

Manuel, You are absolutely right.  I think this is all the Synology just being very dumb.  I guess those are my only two options at this point. I have no idea on how to set up the NUT server though on one of my NUCs or my Pi.  Do you know any good guides out there?  I’m guessing it’s easy enough to edit upsmon.conf on the Synology in order to get that to become a slave; I think would be all