pb syslog in compilation Perl 5.10.0 (book 6.5)

2009-09-22 Thread julien
Hi, I'm using LFS 6.5 and the book 6.5. I'm on 6.32, installation of Perl 5.10.0 I've got an error : Failed 1 test out of 1384, 99.93% okay. ../ext/Sys/Syslog/t/syslog.t perl harness doesn't give more details but ./perl -T ./ext/Sys/Syslog/t/syslog.t gives : not ok 176 - setlogsock

Re: pb syslog in compilation Perl 5.10.0 (book 6.5)

2009-09-22 Thread Christian Sergelius
works fine. 2009/9/22 julien serval2...@yahoo.fr: Hi, I'm using LFS 6.5 and the book 6.5. I'm on 6.32, installation of Perl 5.10.0 I've got an error : Failed 1 test out of 1384, 99.93% okay.        ../ext/Sys/Syslog/t/syslog.t perl harness doesn't give more details but ./perl -T ./ext

Re: Syslog logs - why not just one?

2006-09-24 Thread Jeremy Henty
searching the whole file. I will let syslog separate my messages into as many files as are needed to keep relevant information for each subsystem in it's own place. Hmm, my auth.log contains messages from *four* subsystems: login, PAM, sshd and su . Can I get syslog to follow your recommendation

Re: Syslog logs - why not just one?

2006-09-22 Thread Douglas J Hunley
Jeremy Henty stated: LFS installs a fairly standard looking syslog.conf but doesn't explain its contents.  I'm wondering if there is any justification for splitting the log messages to different files?  There's so much to wade through you'll be using some log analysis/monitoring program

Re: Syslog logs - why not just one?

2006-09-22 Thread Dan Nicholson
analysis/monitoring program anyway, so why not send everything to one file and process it in one go? Doesn't it completely remove the functionality of the syslog to have everything dumped to one file? The entire point of syslog is that you can attach different meaning to the messages and have them

syslog

2006-01-31 Thread mrdaniel
hi, i got another situation here that the following messages appeared in the boot process :- starting system log daemon ... nice: syslogd: no such file or directory starting kernel log daemon nice: klogd: no such file or directoty. we had checked and the /etc/syslog.conf has been coded

Re: syslog

2006-01-31 Thread Jeremy Huntwork
mrdaniel wrote: hi, i got another situation here that the following messages appeared in the boot process :- starting system log daemon ... nice: syslogd: no such file or directory starting kernel log daemon nice: klogd: no such file or directoty. we had checked and the

Re: syslog

2006-01-31 Thread mrdaniel
--- Jeremy Huntwork [EMAIL PROTECTED] wrote: Before you ask another question here, please list what you steps have taken to find the answer to this problem yourself. Before *ever* you post a request for help here, you should have at least used Google to search for an answer. As you may

Re: syslog

2006-01-31 Thread Luca Dionisi
On 1/31/06, mrdaniel [EMAIL PROTECTED] wrote: Chinese Lunar New Year for the urge to do one at least perfect LFS. but till now not there yet. If you expert could lend a hand LFS sould be up and running in perfection I believe in less than a normal working week. Doing searches elsewhere only

Re: syslog

2006-01-31 Thread mrdaniel
--- Luca Dionisi [EMAIL PROTECTED] wrote: Then, you don't need LFS. You can live easily and *productively* with any recent linux distro. Really. Try and you'll see. ok, that's equivalent to the notion of mastering an art it may take as long as 3 years before one can come down from the

Re: syslog

2006-01-31 Thread Luca Dionisi
On 1/31/06, mrdaniel [EMAIL PROTECTED] wrote: ok, that's equivalent to the notion of mastering an art it may take as long as 3 years before one can come down from the mountain to deliver in the real world. IMHO 3 years is too much, one week is too few. Regards Luca --

Re: syslog

2006-01-31 Thread Ricardo Frydman Eureka!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 mrdaniel wrote: --- Jeremy Huntwork [EMAIL PROTECTED] wrote: Before you ask another question here, please list what you steps have taken to find the answer to this problem yourself. Before *ever* you post a request for help here, you should

Re: syslog

2006-01-31 Thread Matt Darcy
mrdaniel wrote: hi, i got another situation here that the following messages appeared in the boot process :- starting system log daemon ... nice: syslogd: no such file or directory starting kernel log daemon nice: klogd: no such file or directoty. we had checked and the

Re: syslog

2006-01-31 Thread mrdaniel
--- Jeremy Huntwork [EMAIL PROTECTED] wrote: probably missing some of the finer points in the book. When you encounter a word or phrase you're not familiar with, how do you work out its meaning? by experimetation. for example the page for untaring had been misunderstood and a new

Re: syslog

2006-01-31 Thread mrdaniel
--- Ricardo Frydman Eureka! [EMAIL PROTECTED] wrote: I am a non-English speaker too. I think that LFS is not for everyone, I hope you understand what I mean You need some basic requirements to get it succesfully working: + some linux basis have improved trying with LFS. thanks for