Hi,
Apart from the fact that profiling is not as cleanly implemented as it
could be, there are problems of the following sort:
1. Some SMB ops call VFS ops. The VFS ops were not using the _NESTED
versions of the profiling calls.
2. Some trans2 calls do other functions, that use the _NESTED op
On Mon, 2002-07-22 at 13:02, Max TenEyck Woodbury wrote:
> This is part of the 'do it at least once before you automate it' section of
> my larger build automation project. (That was described here some time ago,
> and it has morphed more than a little since I posted it, but you may be able
> to s
On Mon, Jul 22, 2002 at 02:48:48PM +0800, [EMAIL PROTECTED] wrote:
> As we know, in linux, there's no the concept of DENY MODE.
> In M$ windows, when open a file, you use the API
> CreateFile (LPCTSTR lpFileName,
> DWORD dwDesiredAccess,
> DWORD dwShareMode,
> LPSECURITY_ATTRIBUTES
On Mon, Jul 22, 2002 at 02:06:43PM -0400, Max TenEyck Woodbury wrote:
> > Also, RH has a package named rpm-redhatdb or something like this. It
> > contains additional RPM database with all RH packages installed (only
> > database records are there of course). You can use it for resolving
> > depen
Alexander Bokovoy wrote:
>
> On Mon, Jul 22, 2002 at 01:02:17PM -0400, Max TenEyck Woodbury wrote:
>> 2) extract the dependency information from the distribution.
>> 3) extract the .spec files for RH samba and rpm.
>> 4) compare RH's samba .spec file with yours. Also, your 2.2.5 and 2.2.3a.
>> 5)
On Mon, Jul 22, 2002 at 01:02:17PM -0400, Max TenEyck Woodbury wrote:
> 2) extract the dependency information from the distribution.
> 3) extract the .spec files for RH samba and rpm.
> 4) compare RH's samba .spec file with yours. Also, your 2.2.5 and 2.2.3a.
> 5) identify what belongs in the Buil
OK. I've had a little sleep. We got into that argument because I was cranky
with lack of sleep and you don't know all that much about my background and
you may have misjudged my intent and the impact of this particular issue, both
in its importance to users and in the amount of work it implies. Al
On Mon, 22 Jul 2002 [EMAIL PROTECTED] wrote:
> ServerWorks Grand Champion HE chipset supports dual Pentium 4
> processors. There's 3.2 GB/s to each proc, and with quad-interleaved
> DDR memory, you've got a 6.4 GB/s memory bandwidth.
Hmmm, that is the way to go, by the sounds of it.
> Compa
On Mon, 22 Jul 2002, Biswapesh Chattopadhyay wrote:
> Hi all
>
> Are there any docs/tutorials for libsmbclient except
You have found them ...
> examples/libsmbclient/*.c ? Or some code that shows everything that is
> possible to be done with it ? Is the API stable ? What is the minimum
> versi
Title: RE: rerun autoconf ?
No, autoconf creates "configure" using "configure.ac" or "configure.in" as input. (Edit autoconf for more info, it's a script.) The "configure" script is included with the source code as a convenience.
You want to run autoconf first, then ./configure, then make.
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, July 22, 2002 4:19 PM
Subject: Re: How to *use* multiple GigE adapters into a single PC
> ServerWorks Grand Champion HE chipset supports dual Pentium 4
> processors. There's 3.2 GB/s to each
ServerWorks Grand Champion HE chipset supports dual Pentium 4
processors. There's 3.2 GB/s to each proc, and with quad-interleaved
DDR memory, you've got a 6.4 GB/s memory bandwidth.
Compaq's DL530 and ML580 seem to fit what you're looking for. They
have 4 100MHz 64bit PCI-X busses. The ML5
Patch includes:
- brand new trust relationships listing code, purely
in rpc-way
- new cli_samr_enum_dom_users() function
- slight fix to libsmb code (anonymous fallback in connecting
ti IPC$)
- a few typos
It's a little rough code and as such it needs some clean-ups yet.
However the ma
Hi all
Are there any docs/tutorials for libsmbclient except
examples/libsmbclient/*.c ? Or some code that shows everything that is
possible to be done with it ? Is the API stable ? What is the minimum
version of Samba from which this API is available ? Where do I get more
info ? Should I join thi
The build completed OK. The resulting binary size is 11767808. The one on the
samba.org FTP site seems have a size of 11765894. The resulting SRPM is 5197778
versus 5190622. Now to figure out why they differ.
I'll try to put together a list for the a minimal BuildRequires section but
that is no
On Mon, Jul 22, 2002 at 06:38:43AM +0930, Richard Sharpe wrote:
> The BuildRequires field seems to be to only be relevant to a source RPM.
> Why even bother to put it into the SPEC file for the binary RPMs we
> supply, because it represents a lot of work that must be checked each time
> we rele
...
creating ./config.status
creating include/stamp-h
creating Makefile
creating script/findsmb
creating include/config.h
[root@box source]# make
WARNING: you need to rerun autoconf <-!
Using FLAGS = -O -Iinclude -I./include -I./ubiqx -I./smbwrapper -I.
-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BIT
17 matches
Mail list logo
