search for: upsdebug_ascii

...log, and if syslog one gets the program name. So upsdebugx should therefore 1) not have the driver name and 2) should have a function, for things that aren't clearly locatable. Correct? 4) I want to print mostly-ASCII strings with non-ASCII escaped. Is there a routine to convert strings? s_upsdebug_ascii output is difficult for mostly-ascii. There is a log of a read string "\nOK" that is messy (and there's a real bug lurking that this exposes). I think I want (actually I want octal because I was raised PDP-11, but not trying to rock that boat): ABCD\{LF}EFG\[89]\\ or similar for...

...rept in. Please find main description in github issue tracker https://github.com/networkupstools/nut/issues/69 and, for completness, both patches attached to this mail. Thanks beforehand, Kirill -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-common-upsdebug_ascii-to-dump-a-message-in-ascii.patch Type: text/x-diff Size: 3695 bytes Desc: not available URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20131118/b15b631e/attachment-0002.patch> -------------- next part -------------- A non-text attachment was scrubbed... Name: 0002-al175...

...n compilers providing the __func__ macro. Technically also __FILE__ and __LINE__ may be used. Neither is guaranteed across the portability board however, but that is likely to only bite very old systems nowadays. The `configure` script tries some fallbacks for __func__ but not for others. As for s_upsdebug_ascii() - I do not think it is a perfectly good idea to change it (maybe is - not much used in NUT codebase; but possibly some forks have more use for it). It sounds reasonable however to define and implement a different method for this purpose, when you expect that sort of content - and call it where su...