similar to: Revive support for HP PowerTrust?

Hi all! As I'm currently porting the HP PowerTrust driver from nut-1.4.3, I have a question regarding ups.delay.*. The PTs can delay the Shutdown/Restart and Kill commands by an arbitrary number of seconds, i.e. they wait for n seconds and then shutdown or kill. The delay for the restart after the shutdown can't be changed. Which of the ups.delay.* variables correspond to these values?

Hi all! As I'm currently porting the HP PowerTrust driver from nut-1.4.3, I have a question regarding ups.delay.*. The PTs can delay the Shutdown/Restart and Kill commands by an arbitrary number of seconds, i.e. they wait for n seconds and then shutdown or kill. The delay for the restart after the shutdown can't be changed. Which of the ups.delay.* variables correspond to these values?

I have a CentOS-6.2 server in Italy. Every few months the server gets into a strange state and stops working after a power outage. I should say that this does not occur after every power outage; I suspect, but have no real evidence for this, that if the power comes back too quickly then the machine gets confused because it is in the middle of closing down. If I am in Italy the solution is simple;

Hello, It's been about 15 years since I've enjoyed working in the Unix space, and I am trying to reintegrate myself. A few things have changed in the intervening years. I've installed the first Centos6 iso without too much difficulty, but I am rusty on commands and such. It appears the install doesn't install mans so would somebody suggest a way to find and install them. It

[I took the liberty of replying on nut-upsdev - not many people are using github yet since the NUT repository native format is still SVN.] On Sep 4, 2012, at 10:17 AM, Emilien Kia wrote: > This is a proposal for a new client library which scopes an higher level than the existing libupsclient. > > It needs less dependencies to be compiled than the libupsclient and can be easier to

Thanks, Mark. Um, how's about from the commandline or how do I get, I guess we're still using X11, windows to load. Sorry, :<}}} Clayton >-----Original Message----- >From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On >Behalf Of Mark LaPierre >Sent: Sunday, December 14, 2014 5:50 PM >To: centos at centos.org; Mark LaPierre >Subject: Re:

Hi I am interested to know: are there are any LLVM targets in the works for Nvidia's PTX ISA? Also if anyone knows about Ocelot (a project done by some students at my school): it does the opposite of what I am trying to do (translates PTX to LLVM IR to run Cuda kernels on the CPU). Thanks in advance. -Puyan

On Mar 26, 2010, at 11:28 PM, Puyan Lotfi wrote: > Hi > > I am interested to know: are there are any LLVM targets in the works > for Nvidia's PTX ISA? > > Also if anyone knows about Ocelot (a project done by some students at > my school): it does the opposite of what I am trying to do (translates > PTX to LLVM IR to run Cuda kernels on the CPU). I don't know of

>> Here is a mod to X86 that allows GAS to be used with MS Visual C++. >> >> I introduces a 'forWindows' variable like 'forCygwin' in th >> X86SharedAsmPrinter class. >> > > A couple of comments: > > 1. Please send patches instead of full files. The best way to do this is > to use CVS like this: 'cvs diff -u' in the

G'day. I hope this isn't off-topic for the list. I am looking at an Asterisk setup that includes cordless phones. The three choices I can see, at this stage, are: * wifi phones * an ATA and a cordless analog phone * a DECT to SIP basestation The various wifi phone options don't grab us as suitable -- they are costly, have poor battery life and even the best have pretty mixed

On Mon, 11 Jul 2005, Aaron Gray wrote: > Here is a mod to X86 that allows GAS to be used with MS Visual C++. > > I introduces a 'forWindows' variable like 'forCygwin' in th > X86SharedAsmPrinter class. > A couple of comments: 1. Please send patches instead of full files. The best way to do this is to use CVS like this: 'cvs diff -u' in the directory

On Sun, 6 Jan 2002, Jack Moffitt wrote: > Unfortunately MP3 is not really an editable format (another reason to > use Vorbis). Its frame headers and frame data don't necessarily come > together in the file, so chopping the file would require quite a lot of > reorganization. The only decent methods I've seen proposed meant > turning the beginning and ends of files into

Here is a mod to X86 that allows GAS to be used with MS Visual C++. I introduces a 'forWindows' variable like 'forCygwin' in th X86SharedAsmPrinter class. This may prompt thurther normalization, on the otherhand it may not :) Aaron -------------- next part -------------- An HTML attachment was scrubbed... URL:

Emilien, just saw your commit in Buildbot for testing some Windows changes. That's great that someone is working on this again! We have had a few users ask for updates to the 2.6.5+ version of NUT for Windows. The problem is that we do not have a good branch in Git to work from. The windows_port branch got rebased, but since it has merge commits, it is a bit of a mess. I apologize for

2014/1/15 Charles Lepple <clepple at gmail.com>: > Emilien, > > just saw your commit in Buildbot for testing some Windows changes. That's great that someone is working on this again! > We have had a few users ask for updates to the 2.6.5+ version of NUT for Windows. I am just fixing some bugs and implementing some minor windows-specific features. > The problem is that

To the list:<br /> <br /> Tons of LLVM research is being done that is damn near worthless to anyone but the person who did it because the team doesn't publish supporting code or even describe at a high level description of the algorithms they're using. And the excuse is always, ALWAYS the same: "we need to clean up the code before we release it."<br /> <br

Earlier, I was using GNOME and Firefox and the Mouse died. I had to kill the power, to get the box going again, because it doesn't have a reset switch; which is *not* an elegant way to get going. What key combination would get me going or to a shell? CentOS 5, fully updated, 32 bit. TIA!

Hi, folks: I remain intrigued by the gap in BRI implementation between North America and Europe, and I wanted to get feedback from the list members on the matter. I'm seriously considering making the leap in our office. In Europe, the idea that an office that does not have enough lines to justify PRI would use analog lines is perceived as technologically backwards, and yet that's what

This reinstates the autogen.sh-based test for the two required ocaml packages. I've tested it by running autoconf.sh first with neither of the two packages installed, then with only ocaml-xml-light installed. In both cases, autogen.sh failed as required. When both were installed, it worked as expected. >From 825d855b225c7c76371c72eae4d505a32c374007 Mon Sep 17 00:00:00 2001 From: Jim

Hello On Wed, 2008-01-23 at 00:10 +0300, Nikita Danilov wrote: > Hello, > > below is a tentative list of tasks into which WBC effort can be > sub-divided. I also provided a less exact list for the EPOCH component, > and an incomplete list for the STL component. > > WBC tasks are estimated in lines-of-code with the total of (9100 + 3000) > LOC, where LOC is a non-comment,