Re: High-res Timers

2012-05-16 Thread Jason Hellenthal
> >> > >> Does anyone have a quick list of high-resolution timer functions? Both > >> user-land and kernel-land? It would be greatly appreciated (doing some > >> performance timing for applications). > >> clocks(7) - various system timers getitimer(2), setitimer(2) - get/set value of interval ti

Re: High-res Timers

2012-05-16 Thread Zhihao Yuan
On Wed, May 16, 2012 at 8:44 PM, David Xu wrote: > On 2012/5/17 4:59, Brandon Falk wrote: >> >> Does anyone have a quick list of high-resolution timer functions? Both >> user-land and kernel-land? It would be greatly appreciated (doing some >> performance timing for applications). >> >> -Brandon >

Re: High-res Timers

2012-05-16 Thread David Xu
On 2012/5/17 4:59, Brandon Falk wrote: Does anyone have a quick list of high-resolution timer functions? Both user-land and kernel-land? It would be greatly appreciated (doing some performance timing for applications). -Brandon AFAIK, there is no high-resolution timer available. ___

Re: GSoC Project: Automated Kernel Crash Reporting System - Discussion

2012-05-16 Thread tzabal
Quoting Fernando Apesteguía : I wonder if it would be good to have a configuration file to specify the amount of information (the type of, also) the system is going to send. Just my 2 cents. This would be a useful feature. This

High-res Timers

2012-05-16 Thread Brandon Falk
Does anyone have a quick list of high-resolution timer functions? Both user-land and kernel-land? It would be greatly appreciated (doing some performance timing for applications). -Brandon ___ freebsd-hackers@freebsd.org mailing list http://lists.free

Re: GSoC Project: Automated Kernel Crash Reporting System - Discussion

2012-05-16 Thread tzabal
Quoting Mateusz Guzik : On Wed, May 16, 2012 at 12:30:20AM +0300, tza...@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. Cogratulations. :) I

Re: Periodic ports checksum

2012-05-16 Thread Bryan Drewery
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/16/2012 02:36 PM, rank1see...@gmail.com wrote: > REL 8.2 added script for finding installed port's files, with > mismatched checksum: /etc/periodic/security/460.chkportsum > > It also said to look for it at # man 5 periodic.conf > > However, ev

Periodic ports checksum

2012-05-16 Thread rank1seeker
REL 8.2 added script for finding installed port's files, with mismatched checksum: /etc/periodic/security/460.chkportsum It also said to look for it at # man 5 periodic.conf However, even up to now in REL 9.0, there is no reference to it, in man pages. -- daily_status_security_chkportsum_enable=

Re: GSoC Project: Automated Kernel Crash Reporting System - Discussion

2012-05-16 Thread Fernando Apesteguía
On Tue, May 15, 2012 at 11:30 PM, 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. > > I have created a page in the FreeBSD Wiki > (http://wiki.freebsd.o

Separating IP addresses between users

2012-05-16 Thread Jakub Szafrański
Hi! So, I was given a task to separate IP addresses from (or between) users. The server has two groups of IP addresses, public and private. A public IP can be used by any user. A private IP can be used only by one, specific user. At the beginning, there were two obvious ways to perform this: a fi

Re: GSoC Project: Automated Kernel Crash Reporting System - Discussion

2012-05-16 Thread Mateusz Guzik
On Wed, May 16, 2012 at 12:30:20AM +0300, tza...@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. > Cogratulations. :) > I have created a

Your monthly income can be increased to 1950 dollars paid.

2012-05-16 Thread simokawa
We invite you to work in the remote assistant position. This work takes 2-3 hours per week and requires absolutely no investment. The essence of this work for incoming client requests in your city. The starting salary is about 2500 EUR per month + bonuses. You get paid your salary every 2 weeks a

Re: GSoC Project: EFI on amd64/i386

2012-05-16 Thread Eric McCorkle
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/15/12 11:44, John Baldwin wrote: > The i386 kernel assumes it starts out with a flat 32-bit mode with > the kernel loaded into a contiguous memory region at a fixed > physical address. If we need a relocatable kernel (as Marcel > hinted at I thi

RE: GSoC Project: Automated Kernel Crash Reporting System - Discussion

2012-05-16 Thread Andrew Duane
I'm interested in the server side of this project, as it's something we've been working on here. We are developing an internal tool for our own crash reporting that does analysis of backtraces and provides a pretty accurate synopsis of what happened. I have a set of heuristics that can find vari

Re: GSoC Project: Automated Kernel Crash Reporting System - Discussion

2012-05-16 Thread tzabal
Quoting Ilya Bakulin : On 15.05.12 23:30, tza...@it.teithe.gr wrote: * The implementation of the kcrashreporter is planned to be done in two shell scripts. Are you really going to name your program "kcrashreporter"? I'd suggest using a different name since everything matching "^k" is automatic

Re: GSoC Project: Automated Kernel Crash Reporting System - Discussion

2012-05-16 Thread tzabal
Quoting Ilya Bakulin : On 15.05.12 23:30, tza...@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

Re: GSoC Project: Automated Kernel Crash Reporting System - Discussion

2012-05-16 Thread tzabal
Quoting Wojciech Puchar : sorry if off topic but is today Google needed to do anything and must supervise everything? Cannot people just write a code as they always did? I think that Google only suggests the 21st of May the starting date for coding. If you start earlier, you will not face