Date: Thu, 02 May 2002 07:33:27 +0530 From: shubhamr <shubhamr@malkauns.nsc.com> Cc: questions@freebsd.org Subject: freebsd doubts-please help Message-ID: <3CD09E6F.465D6E03@malkauns.nsc.com> References: <5.1.0.14.0.20020501192418.02cea050@pop.wsonline.net>
next in thread | previous in thread | raw e-mail | index | archive | help
I have some questions.It wud be of great help if any of you can answer them. 1)I installed freeBSD4.5 ,but after I boot,the kernel messages keep on coming (some message on getty)and I am not able to even enter anything on the console.If this is because of me booting in wrong init level, which init level am I supposed to be in and I how do I configure so that every time my machine boots,I am in the init level I intend to get into? 2)when I do a quick install,I have the src directory /usr/src/sys or /usr/src/share and so on.But when I did a standard install,these are not there and I have some 4 directories under /usr/src..these are secure,kerboros..and so on..what am I supposed to do with these.I tried to make them and was not able to make the /usr/src/secure.even after makingthe kerber..,I did not get the usr/src/sys tree or anything...please tell me what all to do after i did the standard installation so that my FreeBSD OS looks like one..ie,with proper src trees.what are the various things to do..like in quick install I used to make world in /usr/src/...How is it when I install in standard way?,,what are the other makes to be made before my installed OS is complete? 3) If drivers are compiled onto the kernel itself,do kldunload/kldload have any relevance at all?I have an intel Network card and it does not ping/connect even if I do a kldload.Only when I reboot,it gives me the connectivity?why is this?How do I remove the drivers already built into the kernel? 4)where do I find the kernel prints log?where does the kernel print to as /var/log/messages in Linux?what are these kernel prints?are they printk? It wud be of great help if you can reply.I am literally begging for the same. Thanks for your time, shubha RichardH wrote: > This was posted to webhostingtalk.com and the Apacheusers mail list and > still no answers. I think most of them are running small 300 or so user > systems so the idea proposed in the resonse below would be fine for them. > We are looking @ 2000+ users per server (the servers can handle that with > no problem due to their configurations). This will be virtual hosting. > Please check the following and let me know of any ideas on doing this > correctly. > Original post (me): > I have looked all in here and on the net for more specific info on parsing > access logs for multiple user accounts. If I have 300 users on a server and > want to have a "log" directory in each users home directory is there a > script or a simple grep that will pull that users info from the raw access > logs and split/parse the info out to the individual log directory in each > users account so that it can then be viewed by the user with AWStats, > Analog, etc. I know this has to be accomplished failry easily but cannot > find any links or data giving the exact way of doing it. Any input would be > greatly appreciated. OS is FreeBSD4.5 w/Apache Web Server 1.3.24. > Response: > You can just put the TransferLog directive in all of your virtualhosts. > Second post (me): > The only problem with using the transferlog directive, is that for each an > every virtual host entry that is used in the manner, you have another open > file process. In time this will overload your server and create server slow > down. > By parsing out the files with a script, it reduces overall server load AND > permits the use of rewrite rules, that allow you to use a virtmap.txt type > of setup for hosting entries (in which case the transferlog entry does not > work at all). > The transferlog directive is fine for a small production server, where you > are hosting a few accounts, but for a large application, is not such a wise > idea. > > The above post says 300 users as an example, actually looking at 3000+ > users per server. > > Any input, tips, etc. would be greatly appreciated. > Thanks,Richard Hutson > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3CD09E6F.465D6E03>