search for: ruoso

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

2008 Aug 31
2
smb_auth problem
...nd proxyauth sek:/home/netlogon# ls -l total 4 -rwxrwxrwx 1 root root 6 Ago 31 17:35 proxyauth sek:/home/netlogon# ls -ld drwxrwxrwx 2 root root 22 Ago 31 17:35 . sek:/home/netlogon# cat proxyauth allow 8<---------------------------------- Really thanks if someone could help me. -- Vinicius Ruoso - vkr07@c3sl.ufpr.br C3SL: http://www.c3sl.ufpr.br
2008 Sep 01
1
the field ttl in struct referral doesn't work
....My problem is when i set REFERRAL_TTL to be 10, it doesn't work. _________________________________________________________________ ÓÃÊÖ»úMSNÁÄÌìдÓʼþ¿´¿Õ¼ä£¬ÎÞÏÞ¹µÍ¨£¬·ÖÏí¾«²Ê£¡ http://mobile.msn.com.cn/From vkr07 at c3sl.ufpr.br Mon Sep 1 01:21:59 2008 From: vkr07 at c3sl.ufpr.br (Vinicius Ruoso) Date: Mon Sep 1 01:22:29 2008 Subject: [Samba] smb_auth problem In-Reply-To: <17d469250808311450p57d7bd76x56a8de607458bb3d@mail.gmail.com> References: <1343.189.58.5.170.1220218018.squirrel@webmail.inf.ufpr.br> <17d469250808311450p57d7bd76x56a8de607458bb3d@mail.gmail.com> Messa...
2008 Feb 29
0
[LLVMdev] Idea of a tool to help in library versioning
On Feb 29, 2008, at 6:10 AM, Daniel Ruoso wrote: > Then I got the idea of generating an API description file from the > public header files of the library Sounds neat. In the past I've done this with objdump for the public symbols in a library. In theory you don't care about types no findable by the api. A nice tool w...
2008 Mar 01
1
[LLVMdev] Idea of a tool to help in library versioning
Sex, 2008-02-29 às 13:48 -0800, Mike Stump escreveu: > On Feb 29, 2008, at 6:10 AM, Daniel Ruoso wrote: > > Then I got the idea of generating an API description file from the > > public header files of the library > Sounds neat. In the past I've done this with objdump for the public > symbols in a library. In theory you don't care about types no > findable by...
2008 Feb 29
2
[LLVMdev] Idea of a tool to help in library versioning
Hi, I've been thinking lately in the amount of bugs generated by improper handling of library versioning. And I realised that several developers don't understand the implications of subtle API changes (like adding a member to a struct that is member of another struct which happens to be used as an argument of a function call). Then I got the idea of generating an API description file