-
Notifications
You must be signed in to change notification settings - Fork 55
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
Wrong process name/pid #4
Comments
In my use case specifically, I'd like to be able to customize the identifier and not take automatically the process name. See https://github.com/antirez/redis/blob/unstable/redis.conf#L145 as a reference. |
Could you show me the ode you are using? Right now, for me, on OSX I get (with
If I change the function to
|
I'll add a function to modify the process name |
Ok, 1c768ad should have the functions you need. |
In both cases, I'm using the code from extern crate syslog;
use syslog::{Facility,Severity};
fn main() {
match syslog::unix(Facility::LOG_USER) {
Err(e) => println!("impossible to connect to syslog: {:?}", e),
Ok(writer) => {
let r = writer.send(Severity::LOG_ALERT, String::from("hello world"));
if r.is_err() {
println!("error sending the log {}", r.err().expect("got error"));
}
}
}
} |
Do you want me to run it with some extra debug code? |
Can you try with the version 2.2.0? I'll update the readme to put |
It works fine if I use |
README fixed in 2dd4245 |
In c287654 perhaps? 😀 |
Yes, obviously. Sorry, I am really tired right now, and should not mess around much with code :) Did the set_process function work for you? |
Yes, |
In OS X the logs look like this
Notice
Unknown[4294967295]
, which are supposed to be the process name and id, both are incorrect.In Linux, they look like this
Included ntpdate as a reference. Process name and pid are skipped.
The text was updated successfully, but these errors were encountered: