That's extremely unflexible imho. If you want to get kannel to log alone without being cluttered with other daemon's logs, you're out of luck.
In our case, we'd like to use it for remote logging, so we'd use one of the "user" facilities to get kannel and _only_ kannel on it, directed to kannel-only log files. I don't see the problem on allowing the extra flexibility. It's definitely useful for our scenario at least. Regards, -- Alejandro Guerrieri aguerri...@kannel.org On 30/11/2010, at 14:39, Alexander Malysh wrote: > Hi, > > please don't allow changing syslog-faility because it's "standartized" to use > log_daemon for > daemons which bearerbox/smsbox/wapbox is. > > Thanks, > Alexander Malysh > > Am 30.11.2010 um 13:41 schrieb Stipe Tolj: > >> looking at the created output to /var/log/syslog: >> >> Nov 30 13:40:28 xxx bearerbox[24686]: [24686] [6] ERROR: error connecting to >> server `localhost' at port `2345' >> Nov 30 13:40:28 xxx bearerbox[24686]: [24686] [6] ERROR: SMPP[smpp_a]: >> Couldn't >> connect to server. >> >> it would be nice to ommit the OWN [pid] value here, since syslog provides us >> with that information already. Sort of double the information and takes away >> the >> space for the "real" log message. >> >> Checking if we can do this without performance loose. >> >> Stipe >> >> -- >> ------------------------------------------------------------------- >> Kölner Landstrasse 419 >> 40589 Düsseldorf, NRW, Germany >> >> tolj.org system architecture Kannel Software Foundation (KSF) >> http://www.tolj.org/ http://www.kannel.org/ >> >> mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org >> ------------------------------------------------------------------- >> >
