On Wed, Sep 23, 2009 at 11:59 AM, Bryan Liles bryan@osesm.com wrote:
Is there any reason why chef-client and chef-server shouldn't log to
syslog by default?I second this question. Is there any reason why?
Other than my general dislike of Syslog, probably not. If the
majority of you want it to log to syslog by default, I'm happy to
switch. Drop your +1/-1 in reply.
Adam
--
Opscode, Inc.
Adam Jacob, CTO
T: (206) 508-7449 E: adam@opscode.com
+1 For Syslog 
On Wed, Sep 23, 2009 at 8:02 PM, Adam Jacob adam@opscode.com wrote:
On Wed, Sep 23, 2009 at 11:59 AM, Bryan Liles bryan@osesm.com wrote:
Is there any reason why chef-client and chef-server shouldn't log to
syslog by default?I second this question. Is there any reason why?
Other than my general dislike of Syslog, probably not. If the
majority of you want it to log to syslog by default, I'm happy to
switch. Drop your +1/-1 in reply.Adam
--
Opscode, Inc.
Adam Jacob, CTO
T: (206) 508-7449 E: adam@opscode.com
--
$ echo "kpfmAdpoofdufevq/dp/vl" | perl -pe 's/(.)/chr(ord($1)-1)/ge'
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
+1 syslog by default, goes well with rsyslog cookbook (I'm biased!)
Though if chef-client is run from a commandline (ie, there's a tty),
it should output STDOUT as well.
On Sep 23, 2009, at 1:02 PM, Adam Jacob wrote:
On Wed, Sep 23, 2009 at 11:59 AM, Bryan Liles bryan@osesm.com wrote:
Is there any reason why chef-client and chef-server shouldn't log to
syslog by default?I second this question. Is there any reason why?
Other than my general dislike of Syslog, probably not. If the
majority of you want it to log to syslog by default, I'm happy to
switch. Drop your +1/-1 in reply.Adam
--
Opscode, Inc.
Adam Jacob, CTO
T: (206) 508-7449 E: adam@opscode.com
Opscode, Inc
Joshua Timberman, Senior Solutions Engineer
C: 720.878.4322 E: joshua@opscode.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
iEYEARECAAYFAkq6dfUACgkQO97WSdVpzT0Y0ACgm4v2R4Ro2K/Q0XeSalTRtqkv
5TcAmQG7y/1tUFlQg7EyWFvaic8wYWf1
=U0gO
-----END PGP SIGNATURE-----
fyi, to go through history (irc loggins is great for this)
15:29 sigmonsays: something like Chef::Log.logger =
SyslogLogger.new("chef")
put that in /etc/chef/client.rb
gem install SyslogLogger also
Scott
On Sep 23, 2009, at 12:02 PM, Adam Jacob wrote:
On Wed, Sep 23, 2009 at 11:59 AM, Bryan Liles bryan@osesm.com wrote:
Is there any reason why chef-client and chef-server shouldn't log to
syslog by default?I second this question. Is there any reason why?
Other than my general dislike of Syslog, probably not. If the
majority of you want it to log to syslog by default, I'm happy to
switch. Drop your +1/-1 in reply.Adam
--
Opscode, Inc.
Adam Jacob, CTO
T: (206) 508-7449 E: adam@opscode.com!DSPAM:4aba70e3292811804284693!
+1 for syslog but perhaps this should be a switch rather than default?
-Joe
On Wed, 23 Sep 2009 12:02:51 -0700
Adam Jacob adam@opscode.com wrote:
On Wed, Sep 23, 2009 at 11:59 AM, Bryan Liles bryan@osesm.com wrote:
Is there any reason why chef-client and chef-server shouldn't log
to syslog by default?I second this question. Is there any reason why?
Other than my general dislike of Syslog, probably not. If the
majority of you want it to log to syslog by default, I'm happy to
switch. Drop your +1/-1 in reply.Adam
--
Name: Joseph A. Williams
Email: joe@joetify.com
Blog: http://www.joeandmotorboat.com/
That's really the question - it's easy to add the switch, the question
is whether it should be the default.
Adam
On Wed, Sep 23, 2009 at 12:44 PM, Joe Williams joe@joetify.com wrote:
+1 for syslog but perhaps this should be a switch rather than default?
-Joe
On Wed, 23 Sep 2009 12:02:51 -0700
Adam Jacob adam@opscode.com wrote:On Wed, Sep 23, 2009 at 11:59 AM, Bryan Liles bryan@osesm.com wrote:
Is there any reason why chef-client and chef-server shouldn't log
to syslog by default?I second this question. Is there any reason why?
Other than my general dislike of Syslog, probably not. If the
majority of you want it to log to syslog by default, I'm happy to
switch. Drop your +1/-1 in reply.Adam
--
Name: Joseph A. Williams
Email: joe@joetify.com
Blog: http://www.joeandmotorboat.com/
--
Opscode, Inc.
Adam Jacob, CTO
T: (206) 508-7449 E: adam@opscode.com
On Wed, Sep 23, 2009 at 12:50:44PM -0700, Adam Jacob wrote:
That's really the question - it's easy to add the switch, the question
is whether it should be the default.Adam
+1 for syslog by default.
Just out of curiosity has anyone else noticed that the file based
logging gets wedged from time to time ?
On Wed, Sep 23, 2009 at 9:50 PM, Adam Jacob adam@opscode.com wrote:
That's really the question - it's easy to add the switch, the question
is whether it should be the default.
-1
Jonathan
On Wed, Sep 23, 2009 at 12:02 PM, Adam Jacob adam@opscode.com wrote:
On Wed, Sep 23, 2009 at 11:59 AM, Bryan Liles bryan@osesm.com wrote:
Is there any reason why chef-client and chef-server shouldn't log to
syslog by default?I second this question. Is there any reason why?
Other than my general dislike of Syslog, probably not. If the
majority of you want it to log to syslog by default, I'm happy to
switch. Drop your +1/-1 in reply.
I'd be happy if the default was rsyslog. My general thought is that
chef should do the right thing by default, and make it easy to
customize.
The right thing is centralized logging via rsyslog.
--
Joe Van Dyk
http://fixieconsulting.com
+1
On Wed, Sep 23, 2009 at 3:48 PM, Joe Van Dyk joe@fixieconsulting.comwrote:
On Wed, Sep 23, 2009 at 12:02 PM, Adam Jacob adam@opscode.com wrote:
On Wed, Sep 23, 2009 at 11:59 AM, Bryan Liles bryan@osesm.com wrote:
Is there any reason why chef-client and chef-server shouldn't log to
syslog by default?I second this question. Is there any reason why?
Other than my general dislike of Syslog, probably not. If the
majority of you want it to log to syslog by default, I'm happy to
switch. Drop your +1/-1 in reply.I'd be happy if the default was rsyslog. My general thought is that
chef should do the right thing by default, and make it easy to
customize.The right thing is centralized logging via rsyslog.
--
Joe Van Dyk
http://fixieconsulting.com
I'd second joshua's comments that if we have a tty i'd really like to
see output to it and to where ever we end up logging to,
but that said +1 for syslog by default.
-T
On Thu, Sep 24, 2009 at 2:35 AM, Nate Mueller nate@cs.wisc.edu wrote:
+1
On Wed, Sep 23, 2009 at 3:48 PM, Joe Van Dyk joe@fixieconsulting.com
wrote:On Wed, Sep 23, 2009 at 12:02 PM, Adam Jacob adam@opscode.com wrote:
On Wed, Sep 23, 2009 at 11:59 AM, Bryan Liles bryan@osesm.com wrote:
Is there any reason why chef-client and chef-server shouldn't log to
syslog by default?I second this question. Is there any reason why?
Other than my general dislike of Syslog, probably not. If the
majority of you want it to log to syslog by default, I'm happy to
switch. Drop your +1/-1 in reply.I'd be happy if the default was rsyslog. My general thought is that
chef should do the right thing by default, and make it easy to
customize.The right thing is centralized logging via rsyslog.
--
Joe Van Dyk
http://fixieconsulting.com
On Thu, Sep 24, 2009 at 1:24 AM, Thom May thom@clearairturbulence.org wrote:
I'd second joshua's comments that if we have a tty i'd really like to
see output to it and to where ever we end up logging to,
but that said +1 for syslog by default.
The final count here is 7 for, 4 against - so Syslog as the default it is.
The ticket to track Syslog support: http://tickets.opscode.com/browse/CHEF-273
And adding an option to log to STDOUT if you want it:
http://tickets.opscode.com/browse/CHEF-573
Thanks for the replies, everyone! I've scheduled both these tickets for 0.8.
Adam
--
Opscode, Inc.
Adam Jacob, CTO
T: (206) 508-7449 E: adam@opscode.com