Displaying 5 results from an estimated 5 matches for "dervied".
Did you mean:
derived
2005 Dec 16
1
Re: Bug#343530: nut: logging to rrd database
2005/12/15, Alexander V. Inyukhin <shurick@sectorb.msk.ru>:
>
> Package: nut
> Version: 2.0.2-2
> Severity: wishlist
>
> Hello.
Hi Alexander,
I think it is a good idea to log ups variables to rrd
> database instead of log file. So, I create standalone
> rrd logger dervied from upslog nut client.
> Of course, this could be easily implemented using
> upsc or upslog clients and a cron script
> but stanalone application is better for some reasons.
>
> Does anybody else need this functionality?
> Should such a client be included in the nut
> (with ad...
2012 Nov 04
0
[LLVMdev] symbols for exception handling
On Fri, Nov 02, 2012 at 07:53:41PM -0700, reed kotler wrote:
> Basically, labels that are not landing pad symbols that are inserted
> for exception handling
> and dwarf purposes, must declared :
>
> $mysym = .
>
> as opposed to:
>
> $mysym:
Can't you use $mysym +/- 1 in the landing pad reference to work this
idiosyncracy?
Joerg
2004 Dec 22
2
Asterisk Interface to propriotary system and GPL
Hi All,
I am wondering if I will be breaking the GPL,
if I write for example, a channel driver or
make some modifications to the astrisk source code,
to interface at RUN TIME, through sockets, with
a proprietary system.
Eg.
1. I write chan_xxx + modify asterisk source
(make changes + new code publicly available)
2. chan_xxx supports hardware by XXX Corp.
3, XXX Corps interface is
2012 Nov 03
4
[LLVMdev] symbols for exception handling
mips16 has some unusual requirements for label symbols in .s.
I think that arm thumb has the same issue but have not located yet how
this is handled.
When you have a label of an instruction in mips16, when you reference
the label, the linker
adds a 1 to the address. When you call an odd numbered address, the
procesor switches to mips16 mode and when you call an even numbered
address it
2017 Jun 06
10
[Bug 2727] New: ssh_dispatch_run_fatal: Connection to 127.0.0.1 port 8002: message authentication code incorrect
https://bugzilla.mindrot.org/show_bug.cgi?id=2727
Bug ID: 2727
Summary: ssh_dispatch_run_fatal: Connection to 127.0.0.1 port
8002: message authentication code incorrect
Product: Portable OpenSSH
Version: 7.5p1
Hardware: ix86
OS: Linux
Status: NEW
Severity: major
Priority: P5