search for: talagrand

Displaying 5 results from an estimated 5 matches for "talagrand".

2004 Jan 23
2
keyboard activity logging in FreeBSD
Hi, I would like to log all keyboard activities in all ttys in my FreeBSD 5.2 box. Is there anyway to do it? I read the watch man page and it seems like I should run watch with tty as many times as number of ttys. Am I right? Also is it possible to do the log in invisible way? The main reason is to log all commands typed in shell and tty and send the log to the remote server. How can I
2004 Jul 08
1
[LLVMdev] Visual C++ Toolkit
Hi, Have you tried the new VC8 Beta? It's been out for less than 2 weeks: http://lab.msdn.microsoft.com/express/visualc/default.aspx It's supposed to have improved standards compliance. Regards, -Eugene Talagrand On Thu, 8 Jul 2004, Chris Lattner wrote: > Date: Thu, 08 Jul 2004 01:56:03 -0500 (CDT) > From: Chris Lattner <sabre at nondot.org> > Reply-To: llvmdev at cs.uiuc.edu > To: llvmdev at cs.uiuc.edu > Subject: Re: [LLVMdev] Visual C++ Toolkit > > On Thu, 8 Jul 2004, Vladi...
2004 Jul 08
0
[LLVMdev] Visual C++ Toolkit
On Thu, 8 Jul 2004, Vladimir Prus wrote: > > Sorry, but it is not even close to working (its template and STL support > > is horribly lacking). The Visual Studio "Whidbey" compiler, now in beta, > > will handle it though with only a reasonable amount of tweaking to the > > LLVM sources. I have no idea about when Microsoft intends to release it > > though,
2004 Jul 08
3
[LLVMdev] Visual C++ Toolkit
Chris Lattner wrote: > On Thu, 8 Jul 2004, Bill Wendling wrote: > > I just wanted to know if anyone's looked into using the free version of > > Microsoft's Visual C++ toolkit for LLVM: > > > > http://msdn.microsoft.com/visualc/vctoolkit2003/ > > Sorry, but it is not even close to working (its template and STL support > is horribly lacking). The
2004 Jan 06
5
Logging user activities
Hello, What do you recommend for keeping track of user activities? For preserving bash histories I followed these recommendations: http://www.defcon1.org/secure-command.html They include using 'chflags sappnd .bash_history', enabling process accounting, and the like. My goal is to "watch the watchers," i.e. watch for abuse of power by SOC people with the ability to view