search for: s_value

...t to do with > > them (and I can no longer find that piece of information...). > > Here's where the battery.charge variable is calculated: > > https://github.com/networkupstools/nut/blob/master/drivers/tripplite_usb.c#L1099 > > battery_charge = (unsigned)(s_value[5]); > > (In that file, the 3003 protocol is denoted by "tl_model == TRIPP_LITE_SMARTPRO".) > > Due to the command prefix characters in the protocol, the > ups.debug.S hex values are actually indexed from 1 as follows: > > 1 2 3 4 5 6 7 &...

On May 19, 2014, at 7:12 PM, Stefan Bruda wrote: > Hello, > > First of all thank you so much for the information. No problem, glad it is useful. > [...] > Therefore as far as my UPS is concerned s_value[5] is wildly > incorrect. So it turns out that the RM15002U also does not report anything useful for s_value[5]: http://lists.alioth.debian.org/pipermail/nut-upsuser/2007-January/002076.html We really should ask the author of tripplite_usb what he was thinking :-) > Many thanks for the po...

...ng time that is), but I don't know what to do with > them (and I can no longer find that piece of information...). Here's where the battery.charge variable is calculated: https://github.com/networkupstools/nut/blob/master/drivers/tripplite_usb.c#L1099 battery_charge = (unsigned)(s_value[5]); (In that file, the 3003 protocol is denoted by "tl_model == TRIPP_LITE_SMARTPRO".) Due to the command prefix characters in the protocol, the ups.debug.S hex values are actually indexed from 1 as follows: 1 2 3 4 5 6 7 ups.debug.S: 31 30 30 00 28 30 0d '100...

Hello, I own an older Tripp Lite SMART3000RM2U (protocol 3003). It does not work with usbhid-ups but it mostly works with the tripplite_usb driver (nut 2.7.1, the latest in the Gentoo tree), in the sense that the status (on line, on battery, etc.) is detected correctly, the machine is shut down on critical battery, and I can even get some information from the UPS. This is how it all looks:

...Using SMARTPRO protocol (%x)", proto); return TRIPP_LITE_SMARTPRO; @@ -861,7 +865,7 @@ return; } - if(tl_model != TRIPP_LITE_OMNIVS) { + if(tl_model != TRIPP_LITE_OMNIVS && tl_model != TRIPP_LITE_OMNIVS2) { dstate_setinfo("ups.debug.S","%s", hexascdump(s_value+1, 7)); } @@ -893,6 +897,44 @@ } } + + if(tl_model == TRIPP_LITE_OMNIVS2) { + switch(s_value[2]) { + case '0': + dstate_setinfo("battery.test.status", "Battery OK"); + break; + case '1': + dstate_setinfo("battery.test.status", &...

Hello, At 22:19 -0400 on 2014-5-19 Charles Lepple wrote: > > On May 19, 2014, at 7:12 PM, Stefan Bruda wrote: > > > Therefore as far as my UPS is concerned s_value[5] is wildly > > incorrect. > > So it turns out that the RM15002U also does not report anything useful for s_value[5]: > > http://lists.alioth.debian.org/pipermail/nut-upsuser/2007-January/002076.html > > We really should ask the author of tripplite_usb what he was...

...gt; verify the code. For instance is this only applicable to tl_model == > TRIPP_LITE_SMARTPRO (as in my code)? How about tl_model == > TRIPP_LITE_SMART_0004? This one supposedly also responds to a "D" > message with (again supposedly) the same kind of response, but maybe > s_value[5] is better in this case. In my patch I simply did not care > about it and I would not know whether to care or not since I don't > have access to this kind of UPS. Any modification would be a matter > of wild guesses for me (though I am not sure whether others have better > found...

...@ -1929,3 +1929,31 @@ error: free (ret); return NULL; } + +int +do_btrfstune_seeding (const char *device, int svalue) +{ + const size_t MAX_ARGS = 64; + const char *argv[MAX_ARGS]; + size_t i = 0; + CLEANUP_FREE char *err = NULL; + CLEANUP_FREE char *out = NULL; + int r; + const char *s_value = svalue ? "1" : "0"; + + ADD_ARG (argv, i, str_btrfstune); + ADD_ARG (argv, i, "-S"); + ADD_ARG (argv, i, s_value); + if (svalue == 0) + ADD_ARG (argv, i, "-f"); + ADD_ARG (argv, i, device); + ADD_ARG (argv, i, NULL); + + r = commandv (&out, &a...

I have a function that needs to be attached to a bunch of text fields when the page loads. I would like to use the Prototype methods that are added to DOM elements by using the $() function, but I in the function it refers to things with "this". For example, this.style.borderColor. Is there a way to extend elements from the kind of scope I am looking at? For example, is there a way to

Add the note about compatible in TODO for libblkid. Signed-off-by: Wanlong Gao <gaowanlong at cn.fujitsu.com> --- TODO | 3 +++ 1 file changed, 3 insertions(+) diff --git a/TODO b/TODO index 3955552..d604d10 100644 --- a/TODO +++ b/TODO @@ -192,6 +192,9 @@ would make more sense to just use libblkid for this. There are some places where we call out to the 'blkid' program. This

This series adds new APIs to support btrfstune. v2: - merge btrfstune_S_[enable|disable] together - fix naming issue Chen Hanxiao (3): New API: btrfstune_seeding New API: btrfstune_enable_extended_inode_refs New API: btrfstune_enable_skinny_metadata_extent_refs daemon/btrfs.c | 76 ++++++++++++++++++++++++++++++++++++++++++++++++++++ generator/actions.ml | 47

...=numeric(), eta=numeric(), niter=numeric(), niter_changes=numeric(), perform_sum=logical(), verbose=logical())) # # Builds a Remora configuration object. # # [...] # remoraConfiguration <- function(number_clusters, class_name, weighting_function = FUNCTION_REMORA_EUCLIDEAN, scale_variance=TRUE, s_value = 0.001, d = 0.3, alfa = 0.9, eta = 0.01, niter=-1, niter_changes=5, perform_sum = TRUE, verbose=FALSE) { result_configuration <- new(CLASS_REMORA_CONFIGURATION) [...] result_configuration } I'm using R version 2.8.1 (2008-12-22). Sorry for the long email, but I don't want to m...

...== -1) { reply_with_error ("%s: %s", device, err); return -1; @@ -1973,7 +1957,6 @@ do_btrfstune_seeding (const char *device, int svalue) const char *argv[MAX_ARGS]; size_t i = 0; CLEANUP_FREE char *err = NULL; - CLEANUP_FREE char *out = NULL; int r; const char *s_value = svalue ? "1" : "0"; @@ -1985,7 +1968,7 @@ do_btrfstune_seeding (const char *device, int svalue) ADD_ARG (argv, i, device); ADD_ARG (argv, i, NULL); - r = commandv (&out, &err, argv); + r = commandv (NULL, &err, argv); if (r == -1) { reply_with_e...

...rr, str_btrfstune, "--help", NULL); + int r = commandr (NULL, &err, "btrfstune", "--help", NULL); if (r == -1) { reply_with_error ("btrfstune: %s", err); @@ -868,7 +861,7 @@ do_btrfs_set_seeding (const char *device, int svalue) const char *s_value = svalue ? "1" : "0"; - r = commandr (NULL, &err, str_btrfstune, "-S", s_value, device, NULL); + r = commandr (NULL, &err, "btrfstune", "-S", s_value, device, NULL); if (r == -1) { reply_with_error ("%s: %s", device, er...

...rr, str_btrfstune, "--help", NULL); + int r = commandr (NULL, &err, "btrfstune", "--help", NULL); if (r == -1) { reply_with_error ("btrfstune: %s", err); @@ -868,7 +864,7 @@ do_btrfs_set_seeding (const char *device, int svalue) const char *s_value = svalue ? "1" : "0"; - r = commandr (NULL, &err, str_btrfstune, "-S", s_value, device, NULL); + r = commandr (NULL, &err, "btrfstune", "-S", s_value, device, NULL); if (r == -1) { reply_with_error ("%s: %s", device, er...

...*devices, const char *fs) return -1; } - ADD_ARG (argv, i, "btrfs"); + ADD_ARG (argv, i, str_btrfs); ADD_ARG (argv, i, "device"); ADD_ARG (argv, i, "delete"); @@ -609,7 +614,7 @@ do_btrfs_set_seeding (const char *device, int svalue) const char *s_value = svalue ? "1" : "0"; - r = commandr (NULL, &err, "btrfstune", "-S", s_value, device, NULL); + r = commandr (NULL, &err, str_btrfstune, "-S", s_value, device, NULL); if (r == -1) { reply_with_error ("%s: %s", device, er...

...*devices, const char *fs) return -1; } - ADD_ARG (argv, i, "btrfs"); + ADD_ARG (argv, i, str_btrfs); ADD_ARG (argv, i, "device"); ADD_ARG (argv, i, "delete"); @@ -609,7 +614,7 @@ do_btrfs_set_seeding (const char *device, int svalue) const char *s_value = svalue ? "1" : "0"; - r = commandr (NULL, &err, "btrfstune", "-S", s_value, device, NULL); + r = commandr (NULL, &err, str_btrfstune, "-S", s_value, device, NULL); if (r == -1) { reply_with_error ("%s: %s", device, er...

This is a simpler patch that removes GUESTFSD_EXT_CMD completely.

Replace GUESTFSD_EXT_CMD with a command line option ‘./guestfsd --print-external-commands’