From owner-freebsd-hackers@FreeBSD.ORG Wed May 16 11:45:27 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 64A40106566C for ; Wed, 16 May 2012 11:45:27 +0000 (UTC) (envelope-from tzabal@it.teithe.gr) Received: from alpha.it.teithe.gr (alpha.it.teithe.gr [195.251.240.232]) by mx1.freebsd.org (Postfix) with ESMTP id B30458FC08 for ; Wed, 16 May 2012 11:45:26 +0000 (UTC) Received: from localhost (babel.noc.teithe.gr [195.251.240.240]) by alpha.it.teithe.gr (8.14.3/8.14.3/Debian-9.4) with ESMTP id q4GBjSrM008453; Wed, 16 May 2012 14:45:29 +0300 Received: from 37.32.238.191 ([37.32.238.191]) by webmail.teithe.gr (Horde Framework) with HTTP; Wed, 16 May 2012 14:45:24 +0300 Message-ID: <20120516144524.19813u8j0pnxpbh0@webmail.teithe.gr> Date: Wed, 16 May 2012 14:45:24 +0300 From: tzabal@it.teithe.gr To: Ilya Bakulin References: <20120516003020.82068pr8h9dyqjfw@webmail.teithe.gr> <4FB34CF0.6000306@kibab.com> In-Reply-To: <4FB34CF0.6000306@kibab.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.3.9) Cc: freebsd-hackers@freebsd.org Subject: Re: GSoC Project: Automated Kernel Crash Reporting System - Discussion X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 May 2012 11:45:27 -0000 Quoting Ilya Bakulin : > On 15.05.12 23:30, tzabal@it.teithe.gr wrote: >> Hello Community, >> >> I have the project "Automated Kernel Crash Reporting System" for this >> GSoC and I would like to discuss my plans about it before starting the >> coding on May 21. > >> * Can you recommend a secure way of sending a report from a FreeBSD >> system to the Central Collector machine? >> > You can use scp(1) and ship a SSH public key with your software. The > target server must be configured to disable PTY allocation for this key, > so only SCP/SFTP transfer will be possible. Good, this is a scenario that I was looking for. >> * Which data do you want kcrashreporter to collect? At the moment I >> have considered the panic message, the backtrace, the version level of >> the release, the hardware platform (uname -vm) and the configuration >> file of the panicked kernel (config -x `sysctl -n kern.bootfile`). > Collecting the list of loaded modules (kldstat) is also nessesary :-) You are right. Added to the list. >> * Do you propose a different Web Server than the Apache HTTP Server? >> For example, on my initial planning I had included MySQL as the >> selected DBMS and after some discussions I changed to PostgreSQL. > As far as I remember, you're going to use PHP as a programming language? Yes, PHP along with SQL for the Server Side part. > In this case Apache is a good choice. I would however recommend using > www/nginx and PHP in FastCGI mode (FPM option in lang/php5 port). This > is a preffered setup for almost all Russian highloaded websites. > At the beginning using Apache is a reasonable choice. I have never used nginx before. I have considered also the lighttpd. Both with BSD licenses (nginx with a 2-clause BSD like license) and FastCGI support. As I read from Wikipedia, PHP performance has received special attention in lighttpd. I will test both Web servers and then I will make up my mind. ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.