search for: endgam

...tions => ["custid = ?", custid] if cust.updated_on.nil? ...never gets here end Any help would be much appreciated Ken -- I use the words you taught me. If they don''t mean anything any more, teach me others. Or let me be silent. Samuel Beckett (Clov, Endgame)

...S2/Km22)) - d1*P1 == 0 + Vmax22*S2/(S2 + Km22 *(1 + S1/Km12)) + Vmax21*S2/( S2 + Km21 *(1+S1/Km11)) - d2*P2 == 0 S1, S2, P1, P2 are the Variables, u1, u2, Vmax11, Vmax12, Vmax21, Vmax22, Km11, Km12, Km21, Km22, d1 and d2 are Parameters which are given before the solving is attempted. My intention/endgame is to vary 2 or more of the Parameters and obtain a heatmap out of the resulting stationary points. Best Wishes, Andrej Schmelzer -- http://portal.gmx.net/de/go/dsl02

...reason, if any, for an `/etc/killpower` (as it is commonly named) to exist when you boot. It also has a potential for confusion if not deleted, as we discovered in some recent discussion - e.g. due to no packaged NUT init scripts running to remove it, and then upon every shutdown or reboot the late-endgame NUT integration finds it and tells the UPS to power off because at that point presence of the file means an FSD is in progress. So for a few releases now, the documented recommendation is for packagers to use a tmpfs to place that file (and do so in a root-owned subdirectory). Side considerations...

Cheers, With https://github.com/networkupstools/nut/pull/1906 and https://github.com/networkupstools/nut/pull/1912 (and probably some more later), I've been enhancing NUT driver framework with support for live reload of configuration, primarily to acknowledge changes to debug_min setting in ups.conf - but made in a generic fashion that specific drivers may take advantage of for their

Cheers, With https://github.com/networkupstools/nut/pull/1906 and https://github.com/networkupstools/nut/pull/1912 (and probably some more later), I've been enhancing NUT driver framework with support for live reload of configuration, primarily to acknowledge changes to debug_min setting in ups.conf - but made in a generic fashion that specific drivers may take advantage of for their

...itles. This may leave a smudge in the corner and some people may prefer to just see the logo instead, so the smudge could be on an alpha cannel and the viewer can decide to use it or not. A removed logo layer. It could also be a fixing layer, like the removal of the huge JVC logo in Highlander Endgame Special Edition. If good timecoding is available users could even share small overlay movies that fix visual bugs in already bought movies. Underneath It All Remember the No Doubt video where the singer straddles and orgasms and blinks of screen (to that happy place:-) to quickly return back o...

...021." So this is a provider issue, not an end user issue and 'June 30, 2021' doesn't sound like 'soon.' If this is legit, why haven't my providers said squat? > Server = 208.73.232.47 So why do you want everybody to send you their call metadata? What's your endgame? Generate leads to call to pitch your service? Poach clients? Sorry if I sound cynical. It's 2020 and I'm fresh out of "F's." -- Thanks in advance, ------------------------------------------------------------------------- Steve Edwards sedwards at sedwards.com V...

> Also the upsmon POWERDOWNFLAG fits into this question I'm confused. That flag can't be persistent across reboots, can it?

.../1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:131:in `const_missing'' from (irb):5 Thanks, Ken -- I use the words you taught me. If they don''t mean anything any more, teach me others. Or let me be silent. Samuel Beckett (Clov, Endgame)

...;setservice'', :method=>:post Why isn''t the default route working for this particular form action? Thanks Ken -- I use the words you taught me. If they don''t mean anything any more, teach me others. Or let me be silent. Samuel Beckett (Clov, Endgame) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, se...

...ion states vs. OL/OB and/or loss of connection to data server. Hopefully we tuned the state machine better with each iteration, but any glaring issues would better be found and fixed before the release. Some changes also arrived to the `nutshutdown` script that is typically part of systemd-shutdown endgame, but could be used in other platforms as well. Earlier changes since 2.8.0 also touched `upssched` and ability of driver daemons to initiate shutdown (as an alternative to killing the daemon and starting another copy for `drivername -K` action which would take time again to detect and initialize t...

...ion states vs. OL/OB and/or loss of connection to data server. Hopefully we tuned the state machine better with each iteration, but any glaring issues would better be found and fixed before the release. Some changes also arrived to the `nutshutdown` script that is typically part of systemd-shutdown endgame, but could be used in other platforms as well. Earlier changes since 2.8.0 also touched `upssched` and ability of driver daemons to initiate shutdown (as an alternative to killing the daemon and starting another copy for `drivername -K` action which would take time again to detect and initialize t...

WORLDWIDE EMERGENCY The code below needs to be executed before any SIP or PJSIP call destined to the US network, or soon no call will terminate. This is called Stir-Shaken, a new law from the FCC. If this is not working the whole Asterisk industry will crash, vanish, be gone. I am assuming that the caller ID and the Destination Number are in the variables "${CALLERID(num):-10}"

Seconding ... or firsting, considering the recent call to testing hidden somewhere in a recent mail post ;) Currently I'm aiming at cutting a NUT 2.8.1 release during October. As a bit of self-imposed retrospective: I did hope for a faster (quarterly or so) cadence when I made the 2.8.0 release, but then a few issues came up as regressions of 2.8.0 and it became a sort of crusade to fix

Seconding ... or firsting, considering the recent call to testing hidden somewhere in a recent mail post ;) Currently I'm aiming at cutting a NUT 2.8.1 release during October. As a bit of self-imposed retrospective: I did hope for a faster (quarterly or so) cadence when I made the 2.8.0 release, but then a few issues came up as regressions of 2.8.0 and it became a sort of crusade to fix

...der issue, not an end user issue and 'June 30, 2021' > doesn't sound like 'soon.' If this is legit, why haven't my providers said > squat? > > > Server = 208.73.232.47 > > So why do you want everybody to send you their call metadata? What's your > endgame? Generate leads to call to pitch your service? Poach clients? > > Sorry if I sound cynical. It's 2020 and I'm fresh out of "F's." > > -- > Thanks in advance, > ------------------------------------------------------------------------- > Steve Edwards...

...t. Got it. One thing that did bite me when I was a young sysadmin was not so trivial: the UPSes were nice and fancy with SNMP monitoring/management, powered a rack of indeed redundant servers (and their gear on an ePDU fed from STS/ATS which used any live input from the two UPSes it got). And late-endgame UPS shutdowns did not work sometimes. Some theorizing ang troubleshooting later, the problem was that the `ups.conf` entry relied on a DNS name for the UPS, and the networking infra servers were among those to go down - so when the late hook (what is now `nutshutdown` script) found there's a...

Jim Klimov <jimklimov+nut at gmail.com> writes: > I'd say this is not so much about "often enough" (or it would have been > addressed earlier), but neither are ethernet cable/port outages yet people > do LACP/trunking/bonding anyway. And "out of band" serial consoles for good > measure. Sure, but that's for things whose failure is a much bigger deal.

...in with cleanup patches 4. Document how to do this right. I keep getting asked about this, and it helps to point to some documentation file. The series is avaialable for testing at [1]. Arnd [1] https://git.kernel.org/pub/scm/linux/kernel/git/arnd/playground.git/log/?h=compat-ioctl-endgame Arnd Bergmann (24): compat: ARM64: always include asm-generic/compat.h compat: scsi: sg: fix v3 compat read/write interface compat_ioctl: block: handle BLKREPORTZONE/BLKRESETZONE compat_ioctl: block: handle BLKGETZONESZ/BLKGETNRZONES compat_ioctl: block: handle add zone open, close and...

Hi Stepan, Sorry for the delay. It's great that you are working on MergeFunctions as well and I agree, we should definitely try to combine our efforts to improve MergeFunctions. Just to give you some context, the pass (with the similar function merging patch) is already being used in a production setting. From my point of view, it would be better if we focus on improving its capability