"Rainer Gerhards" <[email protected]> writes: > At least for me, it would be usefuly if you could describe your > needs in relatively precise words. It may be obvious for you, but > that is what is hard to grasp for me...
Not sure what you are talking about here Rainer. I was just replying to someone who appeared to think I had made some disparaging remark about the documentation. I simply wanted to clear that up... Now if you mean for me to explain more precisely what I wanted from rsyslog, I'll do that. However, let me say first that with Aarons' pointers to URLS that I am now working my way thru and also having just watched one of your videos and the basics... I have to tell you that that caliber of the documentation is really quite high. There is in depth coverage and then very helpful outside resources such as the video and other postings of yours. I wish I had the command of a foreign language as well as you have of english. I'm a native english speaker... but am sadly nearly illiterate in my own language. The documentation really does out class the usual documentation one encounters in unix/linux tools. ------- --------- ---=--- --------- -------- What I sought to convey in my question about creating directories: Its really low level so sorry I didn't get it across very well. Once I got the clients writing across the network to the rsyslog server, and the server listening and logging the data, I thought for now it would be good to have rsyslog on the server create directories for each remote client, and write everything from each client to /var/log/%hostname%/everthing.log (as a beginning point. While I figure out how to set things up so that each incoming log from remote would be split up further under the top level directories. Kind of like the example shown at (wrapped for mail): http://wiki.rsyslog.com/index.php/ \ Sysklogd_drop-in_with_remote_logs_separated_by_dynamic_directory Just one level deeper. So one level of dynamic directory is created for each client host. Later I'll probably want to spit that a bit more Once I have a more permanent plan figured out I would at least have the full output from each client host on hand. I needed to get the basics up some whet urgently in that I had one host failing silently or at least not leaving a trace I could find in its logs. It would just freeze up, where the mouse and keyboard became unresponsive and could not connect to the problem host remotely either. On mechanical reboot, it would look like the system logger froze up too but someone told me I might catch some log data that would be lost on a hard reboot if I had that host logging remotely...thru rsyslog. I doubted that would be true since it appears as though networking is froze. But I have gotten rsyslog logging remotely now and waiting for a freezeup to see if I can get any more clues as to what is causing the problem. _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
