[go-nuts] SYSLOG in Linux, it's a bug or I use it in wrong way?

Can you please post some sample code demonstrating the issue.

To the best of my knowledge, log rolling is an implementation detail
of syslog/rsyslog/syslog-ng and it intended to be transparent to the
caller.

at the service init func:

srvlog, _ := syslog.New( syslog.LOG_ERR , "myservice" )


then I use syslog.Notice(********) / syslog.Info(********)
/ syslog.Warning(********) such things in other funcs

the question is, when the log rolled, my program won't write log to
/var/log/message ( of cause not, the file descriptor changed )

and to void this, I must reopen the log file use syslog.New every time
before writing log?



在 2012年11月29日星期四UTC+8下午1时38分45秒，Dave Cheney写道：

You're ignoring the error return value. Therefore, you have no idea if the
creation of the syslog object actually succeeded.

srvlog, err := syslog.New(syslog.LOG_ERR, "myservice")
if err != nil {
log.Fatalf("Couldn't start syslog writer: %s", err)
}

If you ignore errors, you should not expect anything to work.

- Dave

I think it's not the point, syslog.New only called once at the beginning of
the program, and this program will run for months
At the first few days, it goes well, writes logs to /var/log/messages
but after log rolled, I mean the system move /var/log/messages to
/var/log/messages[date], and make a new /var/log/messages, the program
doesn't write logs to /var/log/messages

在 2012年11月29日星期四UTC+8下午2时51分16秒，David Anderson写道：

Mate, you're ignoring the error.

Also, syslog, from the point of view of the produce knows nothing
about the final log files (yes, generally syslog output goes to
several locations), it only knows about the unix domain socket that
syslogd listens on.

I made a test:

func main () {
srvlog, err := syslog.New( syslog.LOG_ERR , "golog" )
if err != nil {
println("Log start err")
}
for {
time.Sleep(2*time.Second)
srvlog.Notice("write log")
}
}


After this program run, I can see it writes logs in /var/log/messages, but
after restart the rsyslog service, it won't write logs.
So, the socket is not fixed?

在 2012年11月29日星期四UTC+8下午2时52分08秒，Dave Cheney写道：

Right, ok, now we're getting to the real issue.

I believe you are reporting issue
https://code.google.com/p/go/issues/detail?id=2264

thx a lot

one more question, it was reported and fixed at r59, why it still in go1,
which the version I am using
will it be fixed in later version?



在 2012年11月29日星期四UTC+8下午3时28分49秒，Dave Cheney写道：

issue 2264 is still marked state accepted, it's not fixed.

i think we should raise its priority to Go1.1, IMO this is a serious bug.
I hope the recent CLs that try to make log/syslog more standard compliant
could address this issue.

--