> I am having trouble getting some of the syslogging features to work. From > the documentation at http://projects.unbit.it/uwsgi/wiki/Doc I found: > log-syslog > Log to syslog instead of a log-file. > Passing a parameter makes uwsgi use the parameter as program-name in the > syslog entry header: > --log-syslog mywebapp
Here it must be (for a limit in linux getopt implementation): --log-syslog="mywebapp" or (if the name has no spaces) --log-syslog=mywebapp > > > [uwsgi] > master = true > lazy = true > processes = 5 > buffer-size = 3200 > pythonpath = /var/www/ERP/Application > virtualenv = /var/www/ERP/Environment/ > logto = localhost:514 > log-syslog = erp <-- this line doesn't seem to matter. If I remove it > logs to syslog. However If I remove the logto line it won't log.. > logdate = true > pidfile2 = /var/run/uwsgi/erp.pid > socket = /tmp/uwsgi-erp.sock > chmod-socket = 660 > vacuum = true > uid = web > gid = web > wsgi-file = /var/www/ERP/Application/app.wsgi > stats = /tmp/stats-erp.sock > > Should log-syslog work and when working can you pass it a variable as well > for the program name? > > yes you can use variables, and logto is not needed (are you sure you need logdate too? date is already reported by syslog) Be sure to use 0.9.9.2 (or 1.0-rc* as its syslog handling is much better) -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
