Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kLoggerOption_UseSSL disabled wont connect to client #218

Open
akotulu opened this issue Mar 15, 2017 · 0 comments
Open

kLoggerOption_UseSSL disabled wont connect to client #218

akotulu opened this issue Mar 15, 2017 · 0 comments

Comments

@akotulu
Copy link

akotulu commented Mar 15, 2017

Disabling SSL on local network with only one computer should speed up the logging, but after removing the option, logger stopped connecting to the client.

Version: 1.7.0 Cocoapods

let logger = LoggerInit()
let options:UInt32 = UInt32(kLoggerOption_BufferLogsUntilConnection | kLoggerOption_CaptureSystemConsole)
LoggerSetViewerHost(logger, "192.168.1.153" as NSString, 50000)
LoggerSetOptions(logger, options)
LoggerStart(logger)

Adding kLoggerOption_UseSSL to options solves to connection problem, but no logs messages appair. Adding kLoggerOption_BrowseBonjour to see log output.

let options:UInt32 = UInt32(kLoggerOption_BufferLogsUntilConnection | kLoggerOption_CaptureSystemConsole | kLoggerOption_UseSSL | kLoggerOption_BrowseBonjour)

We have a requirement to see both system console and external client app console log, but currently this seems to be force to only support one pipe.

let options:UInt32 = UInt32(kLoggerOption_LogToConsole | kLoggerOption_BufferLogsUntilConnection | kLoggerOption_CaptureSystemConsole)

Should log to both pipes, but currently LogToConsole flag disables functionality but should be opposite as adding the pipe.

Another option would be adding a new option kLoggerOption_LogToNetwork so both can be defined.

Also when my app sends 50 log lines a second, client app starts to hog the CPU. My late 2014 MacBook pros CPU went as high as 70%, which is unusually high for such a small task.

Otherwise, good work and thanks for the support 🥇

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant