[Samba] samba Digest, Vol 2, Issue 54

[lasaro]

O email [EMAIL PROTECTED] foi alterado para [EMAIL PROTECTED], entretanto a 
sua mensagem foi redirecionada para o novo email.
Atenciosamente,
American BankNote Ltda

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

RE: [Samba] Foxpro Test

[Gerald Drouillard]

Have a look at:
http://www.drouillard.ca/TipsTricks/Samba/Oplocks.htm

Regards
-
Gerald Drouillard
Owner and Consultant
Drouillard  Associates, Inc. 
http://www.Drouillard.ca

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf
 Of lrnobs
 Sent: Thursday, February 13, 2003 3:57 PM
 To: [EMAIL PROTECTED]
 Subject: [Samba] Foxpro Test
 
 
 I want to put a Samba server online under RedHat 7.3 to replace 
 an old Novell server.
 
 Oplocks is turned off.
 
 I ran a test last night with Visual FoxPro code like this:
 
 **
 do while not flock()request a file lock
  try again
 endo
 
 get the date and time
 insert a record into a shared table
 unlock
 
 start over again
 ***
 
 I ran this on seven windows pcs simultaneously.
 
 1. The record insertions would allow one pc to insert multiple 
 records, for example 10 in a row before another computer had a 
 chance to do an insertion.  The same test on the Novell server 
 would allow one or two records before it gave another computer a 
 chance for an insertion.
 
 2. After several thousand insertions I had only one pc consuming 
 the time viewable with the top command.  I killed that process 
 but the other pcs still were not doing insertions.  I killed the 
 process on a second pc and then the rest were free to insert records.
 
 How can I make the Samba server distribute time more evenly.  I 
 suspect that allowing one pc so much record insertion time to the 
 exclusion of others created my lock up.
 
 Thanks,
 
 Larry Nobs
 
 
 
 -- 
 To unsubscribe from this list go to the following URL and read the
 instructions:  http://lists.samba.org/mailman/listinfo/samba
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Samba Print Server Problems

[James Read]

My Samba box consists of FreeBSD 4.7-RELEASE. It has samba version 2.2.7a compiled on 
it.

The problem i have is printing via windows machines to the samba print share.

the clients can 'print' ie send the data to the samba share where i have got samba 
setup to use bsd type printing. 

smb.conf lines are

[printers]
   comment = All Printers
   path = /var/spool/samba
   browseable = no
   guest ok = no
   writeable = no
   printable = yes
   printing = bsd


[lp]
 printable = yes
 browseable = yes
 print command = lpr -s -P %p %s; rm %s
 path = /tmp


I have configured lpd with the lines in /etc/printcap as

lp| Samsung Laser ML-4500:\
:lp=/dev/lpt0:sd=/var/spool/output/lpd:\
:if=/var/log/lpd-errs:sh:mx#0:


When the clients print to the printer via samba, the data does get to lpd but checking 
the logs it spurts out

--

Feb 15 19:30:51 print lpd[221]: lp: unable to open dfA011print.domain.com('f' line)
Feb 15 19:30:51 print lpd[221]: lp: job could not be printed (cfA011print.domain.com)
---


Does anyone want know what is going on and how to make it print out instead of saying 
this error message.

Many thanks


James Read.

--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] Samba Print Server Problems

[Joel Hammer]

Can you print directly from the BSD box using the lp queue?

I ask because you have an oddly named file for your if parameter. That is
supposed to be your print filter.

I suspect, if these jobs are coming from a windows client, they are already
filtered. I would get rid of the if parameter, run checkpc -f, restart lpd,
and try it again.

Joel


On Sat, Feb 15, 2003 at 07:45:15PM -, James Read wrote:
 My Samba box consists of FreeBSD 4.7-RELEASE. It has samba version 2.2.7a compiled 
on it.
 
 The problem i have is printing via windows machines to the samba print share.
 
 the clients can 'print' ie send the data to the samba share where i have got samba 
setup to use bsd type printing. 
 
 lp| Samsung Laser ML-4500:\
 :lp=/dev/lpt0:sd=/var/spool/output/lpd:\
 :if=/var/log/lpd-errs:sh:mx#0:
 
 
 When the clients print to the printer via samba, the data does get to lpd but 
checking the logs it spurts out
 
 --
 
 Feb 15 19:30:51 print lpd[221]: lp: unable to open dfA011print.domain.com('f' line)
 Feb 15 19:30:51 print lpd[221]: lp: job could not be printed (cfA011print.domain.com)
 ---
 
 
 Does anyone want know what is going on and how to make it print out instead of 
saying this error message.
 
 Many thanks
 
 
 James Read.
 
 -- 
 To unsubscribe from this list go to the following URL and read the
 instructions:  http://lists.samba.org/mailman/listinfo/samba
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] re: File won't copy to client

[John H Terpstra]

On Sat, 15 Feb 2003, Corey McGuire wrote:

 This is strange, but I use samba for a software archive at work, and we
 are having trouble with Office 97.  I traced it back to riched20.dll.
 The file is one the server, but it never copies.  I can't even see the
 file.  If i rename it, it shows up.

We feal with your pain.

 What is up with that?

We would not need a crystal ball if you had sent a copy of your smb.conf
file and told us a little more of what you might have done to at least try
to solve your own problem. Our crystal ball is worn out a bit.

Could it be possible that your smb.conf file has in it a line like:

veto files = /*.eml/*.nws/riched20.dll/*.{*}/

Might account for this behaviour. Oops!

- John T.
-- 
John H Terpstra
Email: [EMAIL PROTECTED]
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Re: samba-docs Digest, Vol 2, Issue 5

[John H Terpstra]

 i was reading through the samba mailing list with the subject logon
 scripts. the components for the logon script to be executed are netlogon
 share and a .bat file saved in the netlogon share path.

Well, you need the [netlogon] share _and_ the netlogon service. The
netlogon service is what provides the ability to log onto the network.

If you want the logon script to be capable of being executed by Windows 9X
clients then it has to be a .bat file, MS Windows NT/2K/XP clients can
execute a .cmd file also.

 the next essential component is the samba box has to be a PDC. is this
 statement true? if this is true, is there any workaround? as i just want
 to keep it to be a workgroup as i have a small network with an
 environment of 4 computers.  thank you very much.

Please explain what you believe a PDC is. It will help us to answer your
question. What do you understand by the difference between a workgroup and
a domain?

The fact is that a domain controller is one that provides the netlogon
service. So figure from there!

- John T.
-- 
John H Terpstra
Email: [EMAIL PROTECTED]
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Default settings for print drivers

[Ian Eure]

Hi. I've finally got Samba to serve up print drivers for the printers I serve. 
However, I'm not able to set the default driver options.

This is what I'm doing (from a Win2k Pro box)

Start-Run
\\(samba server)
open Printers folder
right click printer, Properties
Device Settings tab
Configure e.g. default paper size
Click OK
Reopen Properties-Device Settings, and the old paper size is still selected.

Some settings seem to work, but I haven't been able to get the paper size 
settings to work. This is a problem because we have some printers which only 
have legal paper, and they require manual intervention if they get a job for 
some other size paper.

Any suggestions?
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Turning Off Roaming Profiles?

[Jarl McConnel]

Basically, as the subject says, I've found heaps of information on turning them on, 
but I don't particularly want them as my profile is quite large.
--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Turning Off Roaming Profiles? (resend)

[Jarl McConnel]

Sigh, here is me, trying to make a decent first impression of myself by
providing as much information as I could, and then Outlook Expresses 'Send
message later' option does something I didn't expect it to. So, here is the
full message.

Basically, as the subject says, I've found heaps of information on turning
them on, but I don't particularly want them as my profile is quite large.
I'm not quite sure why its even trying to use roaming profiles, I don't have
a logon path = set in my smb.conf.

My only guess is that if it doesn't find the logon path, it just puts the
profile in your logon home directory in a subdirectory called profile.  If
anyone can give me some info in to how to turn this functionality off it'd
be greatly appreciated.

Below is what I believe to be relevant bits of my smb.conf file.

[global]
netbios name = CASPAR
encrypt passwords = true
local master = yes
preferred master = yes
logon script = logon.bat
domain logons = yes
domain master = yes
logon drive = H:
logon home = \\caspar\%u
os level = 99

[homes]
path = /home/%u/shared
create mode = 0600
directory mode = 0700
read only = No
browseable = No

[netlogon]
path = /home/samba/netlogon
read only = No
read list = nobody


Domain logons work (almost) perfectly for my needs except for this problem.
The other problems aren't so much ones which would stop me from using samba
as a PDC, just little annoyances like group mappings.

I am using samba version 2.2.3a-12 for Debian (Debian 3.0).

If anyone could help it'd be greatly appreciated.


-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] Mangling problem

[Andrew Bartlett]

On Mon, 2003-02-10 at 19:38, John H Terpstra wrote:
 On Mon, 10 Feb 2003, Ivan Gustin wrote:
 
  Hi,
 
  I have a strange problem with Samba on RedHat 7.2. In one directory there is
  many files with similar long file name (10+ digit file name for many
  pictures). When I dir this directory, I can see many files with different
  long file name, but with exactly the same short file name. There is about
  3-5 files with the same 8.3 DOS file name.
 
  I really don't understand how can it happen and what is cause of that
  problem. I have Samba 2.2.3, so I put Samba 2.2.7, but the problem is still
  the same. I can't say that is mangling bug within Samba, but I never see
  such
  situation.
 
 Have you seen this problem on MS Windows NT4/2000/XP or is it unique to
 samba?

This is a known issue with Samba, relating to the quality of the hash
function used to mangle file names.   You can set 'mangle method =
hash2' in your smb.conf to 'fix' it.  (chances of a hash collision are
greatly reduced).  This setting is now the default in Samba 3.0, but
make sure you read the smb.conf manpage section on this, as it *will*
change all your mangled (short) names.

Andrew Bartlett
-- 
Andrew Bartlett [EMAIL PROTECTED]
Manager, Authentication Subsystems, Samba Team  [EMAIL PROTECTED]
Student Network Administrator, Hawker College   [EMAIL PROTECTED]
http://samba.org http://build.samba.org http://hawkerc.net



signature.asc
Description: This is a digitally signed message part
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] Samba not printing

[Michael Alaimo]

I have installed samba on a openbsd 3.2 machine.  I am able to mount a file
system from the windows machine, but I am unable to print.
When I try and print from the server with smbspool I get this message.


ERROR: NT_STATUS_ACCESS_DENIED opening remote file test

this is the command used

smbspool smb://user:passwd@WORKGROUP/claudia/lp 1 mike test 1 
/home/mike/index.html

here is the contents of my smb.conf
[global]
   domain master = yes
;   printing = bsd
   allow hosts = 10.1.1.18, 10.1.1.1
   dns proxy = no
   encrypt passwords = yes
   logon path = \\%L\Profiles\%U
   valid users = root, mike
   socket options = TCP_NODELAY
   wins support = true
   max log size = 50
   security = share
   printer admin = root, administrator, mike
   workgroup = WORKGROUP
   log level = 5
   netbios name = claudia
   log file = /var/log/smbd.%m
   os level = 20
   default = lp
   printcap name= /etc/printcap
   load printers = yes


[lp]
   printer = lp
   valid users = mike, @mike
;   writeable = yes
;   postscript = no
;   comment = Samsung ML-1210
;   print command = /usr/bin/lpr
   printable = yes
   path = /var/spool/lpd/lp
   browseable = yes
;   lpq command = /usr/bin/lpq
;   lprm = /usr/bin/lprm
;   printer drive location = \\h\printer$

[alaimo]
   path = /home/mike/.share
   valid users = mike,@mike
   writeable = yes

If you need anything else let me know.
P.S. I can print from the openbsd machine with the lpr command perfectly.

Mike

_
Help STOP SPAM with the new MSN 8 and get 2 months FREE*  
http://join.msn.com/?page=features/junkmail

--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

[Samba] NT Domain BDC

[Nezar Elgaili Elshiekh]

Dear Sir
Iam pleased to contcat you and ihope that you will solve my problem.
Ihave NT domain more than 30 sites in each site ihave BDC can i use samba as
BDC instat of NT BDC for authentication and control share please reply me as
soon as possible
Nezar Elgaili
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] Turning Off Roaming Profiles?

[Kurt Weiss]

Jarl McConnel schrieb:

Basically, as the subject says, I've found heaps of information on turning them on, but I don't particularly want them as my profile is quite large.


*) u can use a policy file to turn them off
*) u can switch it at the client to a local profile

*) we always move the temporary internet files and the temp files 
away from profiles, so the profiles kept small.

gk

--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: [Samba] NT Domain BDC

[Kurt Weiss]

Nezar Elgaili Elshiekh schrieb:

Dear Sir
Iam pleased to contcat you and ihope that you will solve my problem.
Ihave NT domain more than 30 sites in each site ihave BDC can i use samba as
BDC instat of NT BDC for authentication and control share please reply me as


u can use samba as BDC and PDC in a domain. - no problem


soon as possible
Nezar Elgaili



--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba

Re: Winbindd limited by select

[Michael Steffens]

Michael Steffens wrote:

Ken Cross wrote:


There is pretty much a one-to-one correspondence between the number of
smbd processes open (i.e. connected users) and winbindd file descriptors
(per fstat).



Hmm, it may be platform specific. smbd connects winbindd both directly
and via NSS. On HP-UX it consumes two client pipes per smbd, and this
might be due to linking libnss_winbind.1 with -B symbolic, having
symbols resolved locally, such that the two ways used by every smbd
don't share client environment? It's just a guess.


It seems correct, the behaviour is depending on how the NSS backend
library was linked. Build libnss_winbind.1 without the linker option
-B symbolic and, bingo, there is only one client connection per smbd.

For the PAM module libpam_winbind.1 preferred local resolution of
symbols with -B symbolic is still required to work properly. So
optimally the two backend libraries should be linked differently.

Cheers!
Michael

Re: Winbindd limited by select

[Michael Steffens]

David Collier-Brown -- Customer Engineering wrote:

Ken Cross wrote:


#define FD_SETSIZE 2048  /* Max # of winbindd connections */

must occur before the first invocation of sys/types.

This could be a build option, but it might be much simpler to hard-code
it in local.h, which is what I did to fix it.

Can somebody check the implications of this on Solaris, HPUX, etc.?


 
	On Solaris, compiled as a 32-bit app, the limit
	applies.  Compiled as a 64-bit app, you can have 
	as many FDs as you want.

	However, there is currently no good reason to build
	Samba as a 64-bit app: it doesn't need a bigger
	address space.

I'm wondering, basically concerning all platforms, whether this
is about the size of fd_set, or about the number of FDs the
kernel will actually assign to a process.

If the latter one is not limited, wouldn't a single excessive FD
consumer impact other processes?

Cheers!
Michael

RE: Winbindd limited by select

[Ken Cross]

Michael:

It's both.  I hadn't mentioned it, but I also had to add this to
winbindd:

  rlim.rlim_cur = 1500;  // Files
  rlim.rlim_max = rlim.rlim_cur;
  stat = setrlimit( RLIMIT_NOFILE, rlim );
  if( stat != 0 ) DEBUG(0, (Failed to set file limits: %s,
strerror(errno) ) );

The default file limit in NetBSD is 128, so that killed winbindd sooner
than the fd set.

However, in NetBSD, there's no real limit to the size of the fd set
passed in the select function.  If it's larger than the size defined in
the kernel (256), the kernel just malloc's more to accommodate it.  So
changing FD_SETSIZE in the calling program was sufficient to fix the
problem.

Ken


Ken Cross

Network Storage Solutions
Phone 865.675.4070 ext 31
[EMAIL PROTECTED] 

-Original Message-
From: Michael Steffens [mailto:[EMAIL PROTECTED]] 
Sent: Saturday, February 15, 2003 7:39 AM
To: David Collier-Brown -- Customer Engineering
Cc: [EMAIL PROTECTED]; Ken Cross; 'Multiple recipients of list
SAMBA-TECHNICAL'
Subject: Re: Winbindd limited by select


David Collier-Brown -- Customer Engineering wrote:
 Ken Cross wrote:
 
 #define FD_SETSIZE 2048  /* Max # of winbindd connections */

must occur before the first invocation of sys/types.

This could be a build option, but it might be much simpler to 
hard-code it in local.h, which is what I did to fix it.

Can somebody check the implications of this on Solaris, HPUX, etc.?
 
  
   On Solaris, compiled as a 32-bit app, the limit
   applies.  Compiled as a 64-bit app, you can have 
   as many FDs as you want.
 
   However, there is currently no good reason to build
   Samba as a 64-bit app: it doesn't need a bigger
   address space.

I'm wondering, basically concerning all platforms, whether this is about
the size of fd_set, or about the number of FDs the kernel will actually
assign to a process.

If the latter one is not limited, wouldn't a single excessive FD
consumer impact other processes?

Cheers!
Michael

Re: Winbindd limited by select

[Michael Steffens]

Ken Cross wrote:

My $0.02...


Mike Sweet wrote:


Sooo, my recommendations are as follows:

   1. Provide a configure option (--with-maxfiles or similar)
  to configure the upper limit you want to support in SAMBA.
   2. Provide a smb.conf option to control the max number of
  file descriptors.



There's currently a max smbd processes in 3.0.  Would that suffice for
max number of fd's for winbindd?


I don't think so. It's not desireable to restrict the number
of smbds to the number of FDs that winbindd can have
simultanously, IMHO.

Michael

Re: Winbindd limited by select

[Mike Sweet]

Michael Steffens wrote:

Mike Sweet wrote:


Sooo, my recommendations are as follows:

1. Provide a configure option (--with-maxfiles or similar)
   to configure the upper limit you want to support in SAMBA.
2. Provide a smb.conf option to control the max number of
   file descriptors.
3. Provide a definition on Solaris for FD_SETSIZE before
   including sys/select.h so that the correct version of
   select() is used.
4. On startup, query the current FD limit and set it to the
   smaller of the maxfiles definition, the max value
   reported by the kernel, and the max value in smb.conf.
5. Allocate the fd_set buffers [(maxfiles + 7) / 8 bytes]
   and replace all use of FD_ZERO with memset/bzero with
   the correct size.
6. Make sure all calls to FD_SET and FD_CLR are updated to
   not use set, since set is now allocated.



Sounds good! And, for winbindd's client connections, shut down
idle connections when the limit is about to be exceeded?


Right.  CUPS keeps track of the last activity for each client,
and shuts down inactive connections after a configurable amount of
time (30 seconds by default).


Would need to also take FDs for TCP connections, TDBs, logs, etc
into account.


For CUPS we limit the number of network connections to 1/3 of the
available file descriptors (to account for log files, pipes, IPP
and other data files, and job processing; I'm sure there are other
(more accurate) ways of tracking this, and for winbindd you'll likely
have different requirements...

--
__
Michael Sweet, Easy Software Products  [EMAIL PROTECTED]
Printing Software for UNIX   http://www.easysw.com

RE: Winbindd limited by select

[Ken Cross]

I was suggesting the other way around -- the number of winbindd fd's
shouldn't be more than the max # of smbd's (well, maybe a *few* more).

Ken


-Original Message-
From: Michael Steffens [mailto:[EMAIL PROTECTED]] 
Sent: Saturday, February 15, 2003 11:18 AM
To: Ken Cross
Cc: 'Mike Sweet'; 'Multiple recipients of list SAMBA-TECHNICAL'
Subject: Re: Winbindd limited by select


Ken Cross wrote:
 My $0.02...
 
 
 Mike Sweet wrote:
 
Sooo, my recommendations are as follows:

1. Provide a configure option (--with-maxfiles or similar)
   to configure the upper limit you want to support in SAMBA.
2. Provide a smb.conf option to control the max number of
   file descriptors.
 
 
 There's currently a max smbd processes in 3.0.  Would that suffice 
 for max number of fd's for winbindd?

I don't think so. It's not desireable to restrict the number
of smbds to the number of FDs that winbindd can have simultanously,
IMHO.

Michael

Re: Winbindd limited by select

[Mike Sweet]

Ken Cross wrote:

My $0.02...


Mike Sweet wrote:


Sooo, my recommendations are as follows:

   1. Provide a configure option (--with-maxfiles or similar)
  to configure the upper limit you want to support in SAMBA.
   2. Provide a smb.conf option to control the max number of
  file descriptors.



There's currently a max smbd processes in 3.0.  Would that suffice for
max number of fd's for winbindd?


It might; I'm not sure how winbindd and smbd are tied together
(I don't use it myself...)


   3. Provide a definition on Solaris for FD_SETSIZE before
  including sys/select.h so that the correct version of
  select() is used.



It's not just Solaris - I think it's fairly universal.  And it must be
defined before sys/types.h


It doesn't work on Linux or OSX, and of the systems in our (ESP's)
build farm (AIX, FreeBSD, HP-UX, IRIX, Linux, OSX, Solaris, and
Tru64) only Solaris uses a different select() function when dealing
with more than 1024 fd's.

In this case, we are only setting FD_SETSIZE to get the right version
of select, not to increase the size of fd_set.  We could just #ifdef
__sun and define select to select_large_fdset, however that is only
appropriate for newer versions of Solaris (starting with 7 IIRC).


   4. On startup, query the current FD limit and set it to the
  smaller of the maxfiles definition, the max value
  reported by the kernel, and the max value in smb.conf.



And call setrlimit with this value.


Right.


   5. Allocate the fd_set buffers [(maxfiles + 7) / 8 bytes]
  and replace all use of FD_ZERO with memset/bzero with
  the correct size.



It currently (and correctly, IMO) computes the largest *actual* fd and
uses that.  

If you have that info, great.  In CUPS, we just memcpy() a common
input/output set to temporary ones (makes tracking FDs simpler...)

--
__
Michael Sweet, Easy Software Products  [EMAIL PROTECTED]
Printing Software for UNIX   http://www.easysw.com

Re: Winbindd limited by select

[Michael Steffens]

Ken Cross wrote:

I was suggesting the other way around -- the number of winbindd fd's
shouldn't be more than the max # of smbd's (well, maybe a *few* more).


But if you are having a system hard limit of 1024 FDs per process,
for example, which you can't raise via setrlimit, you could only
configure less than that number of smbds.

Coupling these numbers does not make sense IMHO for another reason:
Every process can become a winbind client, even without knowing
about winbind or Samba, via NSS and PAM. How to take these into
account?

I think winbindd shutting down idle connections (not immediately,
there may further requests come along quickly, and never if
a connection carries a getpwent/getgrent status) is less trouble.

Cheers!
Michael

RE: Winbindd limited by select

[Ken Cross]

Good point about non-smbd processes being winbindd clients.  I've got
some myself :-)

Also agreed about benefits of shutting down idle connections -- just not
done yet.

Ken


Ken Cross

Network Storage Solutions
Phone 865.675.4070 ext 31
[EMAIL PROTECTED] 

-Original Message-
From: Michael Steffens [mailto:[EMAIL PROTECTED]] 
Sent: Saturday, February 15, 2003 11:46 AM
To: Ken Cross
Cc: 'Mike Sweet'; 'Multiple recipients of list SAMBA-TECHNICAL'
Subject: Re: Winbindd limited by select


Ken Cross wrote:
 I was suggesting the other way around -- the number of winbindd fd's 
 shouldn't be more than the max # of smbd's (well, maybe a *few* more).

But if you are having a system hard limit of 1024 FDs per process, for
example, which you can't raise via setrlimit, you could only configure
less than that number of smbds.

Coupling these numbers does not make sense IMHO for another reason:
Every process can become a winbind client, even without knowing about
winbind or Samba, via NSS and PAM. How to take these into account?

I think winbindd shutting down idle connections (not immediately, there
may further requests come along quickly, and never if a connection
carries a getpwent/getgrent status) is less trouble.

Cheers!
Michael

Well, the large file offset stuff in smbclient seems to work

[Richard Sharpe]

Hi,

Just reporting that the large file offset code in smbclient and libsmb now 
seems to work. 

I have been chasing a weird problem with 20+ second delays in completing 
writes at times, and have got to 130 GB in a file. Heading towards 350GB 
and later 1TB.
 
Regards
-
Richard Sharpe, rsharpe[at]ns.aus.com, rsharpe[at]samba.org, 
sharpe[at]ethereal.com, http://www.richardsharpe.com

Samba and PPP

[Pavel Fedin]

 Hello!

 Could anyone of you tell me, how to configure my Samba server to work with
PPP interfaces?
 I have an Amiga machine running Samba v2.0.7. And a Windoze95 PC
connected to it via null-modem cable.
 The problem is: Samba ignores all non-broadcast interfaces. So smbd and
nmbd just do not sit on ppp0 interface, so PC can't connect to Samba. Also
smbclient can't find my PC by name (i have to specify an -I option), because
it ignores ppp0 too.
 After examining a source code, i found the following procedure:
 --- cut ---
static void add_interface(struct in_addr ip, struct in_addr nmask)
{
struct interface *iface;
if (iface_find(ip)) {
DEBUG(3,(not adding duplicate interface %s\n,inet_ntoa(ip)));
return;
}

if (ip_equal(nmask, allones_ip)) {
DEBUG(3,(not adding non-broadcast interface %s\n,inet_ntoa(ip)));
return;
}

iface = (struct interface *)malloc(sizeof(*iface));
if (!iface) return;

ZERO_STRUCTPN(iface);

iface-ip = ip;
iface-nmask = nmask;
iface-bcast.s_addr = MKBCADDR(iface-ip.s_addr, iface-nmask.s_addr);

DLIST_ADD(local_interfaces, iface);

DEBUG(2,(added interface ip=%s ,inet_ntoa(iface-ip)));
DEBUG(2,(bcast=%s ,inet_ntoa(iface-bcast)));
DEBUG(2,(nmask=%s\n,inet_ntoa(iface-nmask))); 
}
 --- cut ---
 My interfaces are:
 --- cut ---
16.System: ifconfig
lo0: flags=C9UP,LOOPBACK,RUNNING,NOARP MTU=1536
inet 127.0.0.1 netmask FF00 
Hardware type: Loopback

eth0: flags=4863UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,SANA MTU=1500
inet 10.4.20.98 netmask FFFC broadcast 10.4.20.99
Hardware type: Ethernet, address: 0:80:ad:c6:be:75

ppp0: flags=40F1UP,POINTOPOINT,NOTRAILERS,RUNNING,NOARP,SANA MTU=1500
inet 192.168.255.254 -- 192.168.255.253 netmask  
Hardware type: PPP

Use ifconfig -h for usage.
16.System: 
 --- cut ---
 PC has IP 192.168.255.253.
 When i try to specify a 255.255.255.252 (FFFC) netmask for ppp0, Samba
adds ppp0 to the list of interfaces, but the interface just does not pass
broadcasts.
 What's wrong? How to solve my problem?

 Kind regards.

Re: improved dos attribute handling

[John E. Malmberg]

Ola Lundqvist wrote:

Sorry. I'm not subscribed to this list so I could not
preserve the reply-to header. Please Cc: me if you
want me to know the mail. :)


Bcc: by request.

snipped

On the other hand, with the current setup users must have administrative
rights to modify read-only bit. This is a problem because in a windows
environment (with users used to windows stuff) there is no such thing as
file owners.


There is such a thing as file owners in a domain file server.  This will 
show up in the file properties on Windows under the security properties.

As long as your patch is a selectable behavior, there are probably a lot 
of systems that could use it.


I just wanted to make clear that it does have side effects when you are 
not running in an appliance mode, or if your users are in multiple UNIX 
groups.

I do not run UNIX, I run OpenVMS.  It uses a UIC based protection model 
that is similar to UNIX but there might be some differences that are 
important that I may be overlooking.

I can give users write access to a file with out giving them write 
access to the entire directory.  Write access to the directory implies 
that they can add and remove files.

So adding the world write permission back to a file that the user owns 
when the READONLY bit is cleared will allow every other user on the 
system write access to that file, if they know it's path.

Does UNIX require you to have write access to a directory to modify a 
file that you have write access to?

You simply do not know what the Group and World settings were prior to 
the Readonly attribute being set.


And that is why I check the directory permissions. Iff the user has
write access to the directory and is member of the file it can
modify the permissions.


As I pointed out above, at least on OpenVMS, that is not a valid 
assumption as to what the users wishes are for the world and group 
access.  Just because they have permission to set them does not mean 
that they mean to.


-John
[EMAIL PROTECTED]
Personal Opinion Only

Re: Well, the large file offset stuff in smbclient seems to work

[John E. Malmberg]

Michael B. Allen wrote:

Richard Sharpe [EMAIL PROTECTED] wrote:


Just reporting that the large file offset code in smbclient and libsmb now 
seems to work. 

I have been chasing a weird problem with 20+ second delays in completing 
writes at times, and have got to 130 GB in a file. Heading towards 350GB 
and later 1TB.

Wouldn't anything after 4GB be redundant?


No.  Strange effects can happen at many different file sizes.  If you do 
not test it, you do not know that it works.

The weakness may not be in smbclient or libsmb though.

-John
[EMAIL PROTECTED]
Personal Opinion Only

Re: Well, the large file offset stuff in smbclient seems to work

[Michael B. Allen]

On Sat, 15 Feb 2003 21:26:16 -0500
John E. Malmberg [EMAIL PROTECTED] wrote:

 Michael B. Allen wrote:
  Richard Sharpe [EMAIL PROTECTED] wrote:
  
 Just reporting that the large file offset code in smbclient and libsmb now 
 seems to work. 
 
 I have been chasing a weird problem with 20+ second delays in completing 
 writes at times, and have got to 130 GB in a file. Heading towards 350GB 
 and later 1TB.
  
  Wouldn't anything after 4GB be redundant?
 
 No.  Strange effects can happen at many different file sizes.  If you do 
 not test it, you do not know that it works.

Can you give me a specific example? I've written a client and I never
tested it past 5-6GB. You have me worried now :-/

Mike

-- 
A  program should be written to model the concepts of the task it
performs rather than the physical world or a process because this
maximizes  the  potential  for it to be applied to tasks that are
conceptually  similar and, more important, to tasks that have not
yet been conceived. 

Re: Well, the large file offset stuff in smbclient seems to work

[Christopher R. Hertel]

Richard,

Any chance you can do some jCIFS testing for us?

Chris -)-

On Sat, Feb 15, 2003 at 10:01:48PM -0500, Michael B. Allen wrote:
 On Sat, 15 Feb 2003 21:26:16 -0500
 John E. Malmberg [EMAIL PROTECTED] wrote:
 
  Michael B. Allen wrote:
   Richard Sharpe [EMAIL PROTECTED] wrote:
   
  Just reporting that the large file offset code in smbclient and libsmb now 
  seems to work. 
  
  I have been chasing a weird problem with 20+ second delays in completing 
  writes at times, and have got to 130 GB in a file. Heading towards 350GB 
  and later 1TB.
   
   Wouldn't anything after 4GB be redundant?
  
  No.  Strange effects can happen at many different file sizes.  If you do 
  not test it, you do not know that it works.
 
 Can you give me a specific example? I've written a client and I never
 tested it past 5-6GB. You have me worried now :-/
 
 Mike
 
 -- 
 A  program should be written to model the concepts of the task it
 performs rather than the physical world or a process because this
 maximizes  the  potential  for it to be applied to tasks that are
 conceptually  similar and, more important, to tasks that have not
 yet been conceived. 

-- 
Samba Team -- http://www.samba.org/ -)-   Christopher R. Hertel
jCIFS Team -- http://jcifs.samba.org/   -)-   ubiqx development, uninq.
ubiqx Team -- http://www.ubiqx.org/ -)-   [EMAIL PROTECTED]
OnLineBook -- http://ubiqx.org/cifs/-)-   [EMAIL PROTECTED]

Re: Well, the large file offset stuff in smbclient seems to work

[John E. Malmberg]

Michael B. Allen wrote:


No.  Strange effects can happen at many different file sizes.  If you do 
not test it, you do not know that it works.
 
Can you give me a specific example? I've written a client and I never
tested it past 5-6GB. You have me worried now :-/

There may not be a problem in your client.

But problems may show up in file systems and the support C library 
calls.  In older systems, bits were precious, so there may be many 
fields that do not have enough, and now backwards compatability may be 
showing it's age.  Sometimes it is found in a device driver that because 
at the time a 1GB disk was unimaginable, that the bits above there were 
used for flags.

Some algorithms are sound but do not scale well, hence the unexplained 
slowdowns.

Every 4 bit nybble barrier can be an issue, and the signed/unsigned 
usage may also be an issue.  The granualarity of blocks in the file system.

Once you get past 4GB, I would expect the next hiccup may be at the 1TB 
level and then every power of 2 beyond that.

How many people are dealing with files larger than 4G on a regular basis?

You can not test every thing though. :-)

-John
[EMAIL PROTECTED]
Personal Opinion Only

Re: Well, the large file offset stuff in smbclient seems to work

[Richard Sharpe]

On Sat, 15 Feb 2003, Christopher R. Hertel wrote:

 Richard,
 
 Any chance you can do some jCIFS testing for us?

I might be able to. Send me the code or a pointer ...

At least I have GigE between the test machine and the server ...

Regards
-
Richard Sharpe, rsharpe[at]ns.aus.com, rsharpe[at]samba.org, 
sharpe[at]ethereal.com, http://www.richardsharpe.com

Re: Well, the large file offset stuff in smbclient seems to work

[Richard Sharpe]

On Sat, 15 Feb 2003, Michael B. Allen wrote:

 On Sat, 15 Feb 2003 21:26:16 -0500
 John E. Malmberg [EMAIL PROTECTED] wrote:
 
  Michael B. Allen wrote:
   Richard Sharpe [EMAIL PROTECTED] wrote:
   
  Just reporting that the large file offset code in smbclient and libsmb now 
  seems to work. 
  
  I have been chasing a weird problem with 20+ second delays in completing 
  writes at times, and have got to 130 GB in a file. Heading towards 350GB 
  and later 1TB.
   
   Wouldn't anything after 4GB be redundant?
  
  No.  Strange effects can happen at many different file sizes.  If you do 
  not test it, you do not know that it works.
 
 Can you give me a specific example? I've written a client and I never
 tested it past 5-6GB. You have me worried now :-/

Well, I would expect problems at 64GB, etc, and 1TB or so. In my case, 
until I have access to a multi-shelf setup, I won't be able to test much 
beyond 1TB.

But the testing has already paid dividends in turning up these weird 
delays for some writes. However, that is a file system issue.

Regards
-
Richard Sharpe, rsharpe[at]ns.aus.com, rsharpe[at]samba.org, 
sharpe[at]ethereal.com, http://www.richardsharpe.com

Libsmbclient question

[Michael Grube]

This is kind of a trivial question for a technical mailing list, but
with libsmbclient, how do you connect to a computer by IP address,
rather than by smb/nmb name?
Thanks,
Mike Grube

Re: Libsmbclient question

[Richard Sharpe]

On Sat, 15 Feb 2003, Michael Grube wrote:

 This is kind of a trivial question for a technical mailing list, but
 with libsmbclient, how do you connect to a computer by IP address,
 rather than by smb/nmb name?

Well, reading the code would pay a healthy dividend, but in anycase:

Try smb://a.b.c.d/share/...

Now to see if someone's spam filter trips up on a word or two :-)

Regards
-
Richard Sharpe, rsharpe[at]ns.aus.com, rsharpe[at]samba.org, 
sharpe[at]ethereal.com, http://www.richardsharpe.com

Re: Libsmbclient question

[Michael Grube]

I read the code, but it didn't occur to me that I could use an address
instead of a name. Sorry for the waste :-).
Mike Grube

On Sat, 2003-02-15 at 21:33, Richard Sharpe wrote:
 On Sat, 15 Feb 2003, Michael Grube wrote:
 
  This is kind of a trivial question for a technical mailing list, but
  with libsmbclient, how do you connect to a computer by IP address,
  rather than by smb/nmb name?
 
 Well, reading the code would pay a healthy dividend, but in anycase:
 
 Try smb://a.b.c.d/share/...
 
 Now to see if someone's spam filter trips up on a word or two :-)
 
 Regards
 -
 Richard Sharpe, rsharpe[at]ns.aus.com, rsharpe[at]samba.org, 
 sharpe[at]ethereal.com, http://www.richardsharpe.com
 

Re: Well, the large file offset stuff in smbclient seems to work

[Michael B. Allen]

On Sat, 15 Feb 2003 23:04:29 -0500
John E. Malmberg [EMAIL PROTECTED] wrote:

 Michael B. Allen wrote:
 
 No.  Strange effects can happen at many different file sizes.  If you do 
 not test it, you do not know that it works.
   
  Can you give me a specific example? I've written a client and I never
  tested it past 5-6GB. You have me worried now :-/
 
 There may not be a problem in your client.
 
 But problems may show up in file systems and the support C library 
 calls.  In older systems, bits were precious, so there may be many 
 fields that do not have enough, and now backwards compatability may be 
 showing it's age.  Sometimes it is found in a device driver that because 
 at the time a 1GB disk was unimaginable, that the bits above there were 
 used for flags.
 
 Some algorithms are sound but do not scale well, hence the unexplained 
 slowdowns.
 
 Every 4 bit nybble barrier can be an issue, and the signed/unsigned 
 usage may also be an issue.  The granualarity of blocks in the file system.
 
 Once you get past 4GB, I would expect the next hiccup may be at the 1TB 
 level and then every power of 2 beyond that.

Ok, so you're citing unforseen problems with how libraries, drivers,
hardware, etc handle the 64 bit type as opposed to some issue known to
the protocol like some bits getting trampled if the field isn't aligned
with the planets or some such.

 How many people are dealing with files larger than 4G on a regular basis?

Not many.

 You can not test every thing though. :-)

Yes, even over loopback the process is a too tedious :-)

Mike

-- 
A  program should be written to model the concepts of the task it
performs rather than the physical world or a process because this
maximizes  the  potential  for it to be applied to tasks that are
conceptually  similar and, more important, to tasks that have not
yet been conceived. 

CVS update: samba/source/libsmb

[abartlet]

Date:   Sat Feb 15 12:20:22 2003
Author: abartlet

Update of /data/cvs/samba/source/libsmb
In directory dp.samba.org:/tmp/cvs-serv32322/libsmb

Modified Files:
asn1.c cliconnect.c clispnego.c errormap.c ntlmssp.c 
ntlmssp_parse.c 
Log Message:
Move our NTLMSSP client code into ntlmssp.c.  The intention is to provide a 
relitivly useful external lib from this code, and to remove the dupicate
NTLMSSP code elsewhere in samba (RPC pipes, LDAP client).

The code I've replaced this with in cliconnect.c is relitivly ugly, and 
I hope to replace it with a more general SPENGO layer at some later date.

Andrew Bartlett 


Revisions:
asn1.c  1.16 = 1.17
http://www.samba.org/cgi-bin/cvsweb/samba/source/libsmb/asn1.c?r1=1.16r2=1.17
cliconnect.c1.124 = 1.125

http://www.samba.org/cgi-bin/cvsweb/samba/source/libsmb/cliconnect.c?r1=1.124r2=1.125
clispnego.c 1.27 = 1.28

http://www.samba.org/cgi-bin/cvsweb/samba/source/libsmb/clispnego.c?r1=1.27r2=1.28
errormap.c  1.19 = 1.20

http://www.samba.org/cgi-bin/cvsweb/samba/source/libsmb/errormap.c?r1=1.19r2=1.20
ntlmssp.c   1.8 = 1.9
http://www.samba.org/cgi-bin/cvsweb/samba/source/libsmb/ntlmssp.c?r1=1.8r2=1.9
ntlmssp_parse.c 1.1 = 1.2

http://www.samba.org/cgi-bin/cvsweb/samba/source/libsmb/ntlmssp_parse.c?r1=1.1r2=1.2

CVS update: samba/source/include

[abartlet]

Date:   Sat Feb 15 12:20:22 2003
Author: abartlet

Update of /data/cvs/samba/source/include
In directory dp.samba.org:/tmp/cvs-serv32322/include

Modified Files:
ntlmssp.h 
Log Message:
Move our NTLMSSP client code into ntlmssp.c.  The intention is to provide a 
relitivly useful external lib from this code, and to remove the dupicate
NTLMSSP code elsewhere in samba (RPC pipes, LDAP client).

The code I've replaced this with in cliconnect.c is relitivly ugly, and 
I hope to replace it with a more general SPENGO layer at some later date.

Andrew Bartlett 


Revisions:
ntlmssp.h   1.4 = 1.5

http://www.samba.org/cgi-bin/cvsweb/samba/source/include/ntlmssp.h?r1=1.4r2=1.5

CVS update: samba/docs/docbook/projdoc

[jelmer]

Date:   Sat Feb 15 14:13:55 2003
Author: jelmer

Update of /home/cvs/samba/docs/docbook/projdoc
In directory dp.samba.org:/tmp/cvs-serv11140

Modified Files:
GroupProfiles.sgml 
Log Message:

Fix *a lot* of syntax errors


Revisions:
GroupProfiles.sgml  1.1 = 1.2

http://www.samba.org/cgi-bin/cvsweb/samba/docs/docbook/projdoc/GroupProfiles.sgml?r1=1.1r2=1.2

CVS update: samba/docs/textdocs

[jelmer]

Date:   Sat Feb 15 14:17:03 2003
Author: jelmer

Update of /home/cvs/samba/docs/textdocs
In directory dp.samba.org:/tmp/cvs-serv11533

Removed Files:
CreatingGroupProfiles-Win2K.txt 
CreatingGroupProfiles-Win9X.txt CreatingGroupProfilesInNT4.txt 
Log Message:

Remove obsolete textdocs - they have been migrated to SGML


Revisions:
CreatingGroupProfiles-Win2K.txt 1.3 = NONE

http://www.samba.org/cgi-bin/cvsweb/samba/docs/textdocs/CreatingGroupProfiles-Win2K.txt?rev=1.3
CreatingGroupProfiles-Win9X.txt 1.2 = NONE

http://www.samba.org/cgi-bin/cvsweb/samba/docs/textdocs/CreatingGroupProfiles-Win9X.txt?rev=1.2
CreatingGroupProfilesInNT4.txt  1.2 = NONE

http://www.samba.org/cgi-bin/cvsweb/samba/docs/textdocs/CreatingGroupProfilesInNT4.txt?rev=1.2

CVS update: samba/docs/docbook/projdoc

[jelmer]

Date:   Sat Feb 15 14:44:25 2003
Author: jelmer

Update of /home/cvs/samba/docs/docbook/projdoc
In directory dp.samba.org:/tmp/cvs-serv14152

Added Files:
passdb.sgml 
Log Message:

Add draft of universal passdb document that combines ENCRYPTION.sgml, 
Samba-LDAP-HOWTO.sgml, pdb_mysql.sgml and pdb_xml.sgml


Revisions:
passdb.sgml NONE = 1.1

http://www.samba.org/cgi-bin/cvsweb/samba/docs/docbook/projdoc/passdb.sgml?rev=1.1

CVS update: samba/source

[ab]

Date:   Sat Feb 15 15:47:32 2003
Author: ab

Update of /home/cvs/samba/source
In directory dp.samba.org:/tmp/cvs-serv20820

Modified Files:
configure.in 
Log Message:
Add support for krb5-config from recent MIT and Heimdal. And fallback to traditional 
guessing only if krb5-config was not found.

Revisions:
configure.in1.401 = 1.402
http://www.samba.org/cgi-bin/cvsweb/samba/source/configure.in?r1=1.401r2=1.402

CVS update: samba/source

[ab]

Date:   Sat Feb 15 15:50:24 2003
Author: ab

Update of /home/cvs/samba/source
In directory dp.samba.org:/tmp/cvs-serv21041

Modified Files:
configure.in 
Log Message:
When checking for tgetent, include libtinfo from recent Ncurses as well

Revisions:
configure.in1.402 = 1.403
http://www.samba.org/cgi-bin/cvsweb/samba/source/configure.in?r1=1.402r2=1.403

CVS update: samba/docs/docbook/projdoc

[jelmer]

Date:   Sat Feb 15 16:35:20 2003
Author: jelmer

Update of /home/cvs/samba/docs/docbook/projdoc
In directory dp.samba.org:/tmp/cvs-serv25813

Modified Files:
passdb.sgml 
Log Message:

Some small updates


Revisions:
passdb.sgml 1.1 = 1.2

http://www.samba.org/cgi-bin/cvsweb/samba/docs/docbook/projdoc/passdb.sgml?r1=1.1r2=1.2

CVS update: samba/source

[ab]

Date:   Sat Feb 15 19:13:53 2003
Author: ab

Update of /home/cvs/samba/source
In directory dp.samba.org:/tmp/cvs-serv9935/source

Modified Files:
  Tag: SAMBA_3_0
configure.in 
Log Message:
Merger krb5-config and libtinfo to SAMBA_3_0

Revisions:
configure.in1.300.2.44 = 1.300.2.45

http://www.samba.org/cgi-bin/cvsweb/samba/source/configure.in?r1=1.300.2.44r2=1.300.2.45

CVS update: samba/source/client

[idra]

Date:   Sat Feb 15 21:34:45 2003
Author: idra

Update of /data/cvs/samba/source/client
In directory dp.samba.org:/tmp/cvs-serv25453/client

Modified Files:
  Tag: SAMBA_2_2
smbspool.c 
Log Message:

fix dumb perror used without errno beeing set.
thanks to RedHat developers for the report



Revisions:
smbspool.c  1.4.4.7 = 1.4.4.8

http://www.samba.org/cgi-bin/cvsweb/samba/source/client/smbspool.c?r1=1.4.4.7r2=1.4.4.8

CVS update: samba/source/client

[idra]

Date:   Sat Feb 15 21:36:28 2003
Author: idra

Update of /data/cvs/samba/source/client
In directory dp.samba.org:/tmp/cvs-serv25752/client

Modified Files:
smbspool.c 
Log Message:
fix dumb perror used without errno beeing set.
thanks to RedHat developers for the report



Revisions:
smbspool.c  1.21 = 1.22

http://www.samba.org/cgi-bin/cvsweb/samba/source/client/smbspool.c?r1=1.21r2=1.22

CVS update: samba/source/client

[idra]

Date:   Sat Feb 15 21:37:15 2003
Author: idra

Update of /data/cvs/samba/source/client
In directory dp.samba.org:/tmp/cvs-serv25811/client

Modified Files:
  Tag: SAMBA_3_0
smbspool.c 
Log Message:
fix dumb perror used without errno beeing set.
thanks to RedHat developers for the report



Revisions:
smbspool.c  1.15.2.5 = 1.15.2.6

http://www.samba.org/cgi-bin/cvsweb/samba/source/client/smbspool.c?r1=1.15.2.5r2=1.15.2.6

CVS update: samba/source

[ab]

Date:   Sat Feb 15 22:51:15 2003
Author: ab

Update of /home/cvs/samba/source
In directory dp.samba.org:/tmp/cvs-serv2143

Modified Files:
aclocal.m4 configure.in 
Log Message:
Third-party configuration scripts may produce undesirable additions to CFLAGS/CPPFLAGS 
and LIBS/LDFALGS. In particular, they often don't check where the appropriate libraries
were installed and pass -I/usr/include and -L/usr/lib as part of CFLAGS/LDFLAGS.

While the latter isn't dangerous, passing system include directory through -I lead
to change of its status in CPP from system to user-defined in many cases.

This patch cleans up CFLAGS/CPPFLAGS from errorenous -I/usr/include and LIBS/LDFLAGS
from -L/usr/lib. This is done as two m4 macros which are called before AC_OUTPUT.



Revisions:
aclocal.m4  1.14 = 1.15
http://www.samba.org/cgi-bin/cvsweb/samba/source/aclocal.m4?r1=1.14r2=1.15
configure.in1.403 = 1.404
http://www.samba.org/cgi-bin/cvsweb/samba/source/configure.in?r1=1.403r2=1.404

CVS update: samba/source

[ab]

Date:   Sat Feb 15 23:07:59 2003
Author: ab

Update of /home/cvs/samba/source
In directory dp.samba.org:/tmp/cvs-serv5609

Modified Files:
  Tag: SAMBA_3_0
aclocal.m4 configure.in 
Log Message:
Merge from head CFLAGS/CPPFLAGS and LIBS/LDFLAGS sanitizing

Revisions:
aclocal.m4  1.10.2.3 = 1.10.2.4

http://www.samba.org/cgi-bin/cvsweb/samba/source/aclocal.m4?r1=1.10.2.3r2=1.10.2.4
configure.in1.300.2.45 = 1.300.2.46

http://www.samba.org/cgi-bin/cvsweb/samba/source/configure.in?r1=1.300.2.45r2=1.300.2.46

CVS update: samba/source/include

[jerry]

Date:   Sat Feb 15 23:30:42 2003
Author: jerry

Update of /data/cvs/samba/source/include
In directory dp.samba.org:/tmp/cvs-serv8687/include

Modified Files:
  Tag: APPLIANCE_HEAD
rpc_spoolss.h 
Log Message:
* set PRINTER_ATTRIBUTE_RAW_ONLY; CR 1736
* never save a pointer to an automatic variable (they go away)
  implement a deep copy for SPOOLSS_NOTIFY_MSG to correct
  messages being sent that have junk for strings; 
  fix in response to changes for CR 1504
  

Revisions:
rpc_spoolss.h   1.39.2.29 = 1.39.2.30

http://www.samba.org/cgi-bin/cvsweb/samba/source/include/rpc_spoolss.h?r1=1.39.2.29r2=1.39.2.30

CVS update: samba/source/printing

[jerry]

Date:   Sat Feb 15 23:30:43 2003
Author: jerry

Update of /data/cvs/samba/source/printing
In directory dp.samba.org:/tmp/cvs-serv8687/printing

Modified Files:
  Tag: APPLIANCE_HEAD
notify.c nt_printing.c 
Log Message:
* set PRINTER_ATTRIBUTE_RAW_ONLY; CR 1736
* never save a pointer to an automatic variable (they go away)
  implement a deep copy for SPOOLSS_NOTIFY_MSG to correct
  messages being sent that have junk for strings; 
  fix in response to changes for CR 1504
  

Revisions:
notify.c1.1.2.19 = 1.1.2.20

http://www.samba.org/cgi-bin/cvsweb/samba/source/printing/notify.c?r1=1.1.2.19r2=1.1.2.20
nt_printing.c   1.83.2.122 = 1.83.2.123

http://www.samba.org/cgi-bin/cvsweb/samba/source/printing/nt_printing.c?r1=1.83.2.122r2=1.83.2.123

CVS update: samba/source/printing

[jerry]

Date:   Sat Feb 15 23:33:30 2003
Author: jerry

Update of /data/cvs/samba/source/printing
In directory dp.samba.org:/tmp/cvs-serv9059/printing

Modified Files:
  Tag: SAMBA_3_0
nt_printing.c notify.c 
Log Message:
* set PRINTER_ATTRIBUTE_RAW_ONLY; CR 1736
* never save a pointer to an automatic variable (they go away)
  implement a deep copy for SPOOLSS_NOTIFY_MSG to correct
  messages being sent that have junk for strings; 
  fix in response to changes for CR 1504
  

Revisions:
nt_printing.c   1.204.2.19 = 1.204.2.20

http://www.samba.org/cgi-bin/cvsweb/samba/source/printing/nt_printing.c?r1=1.204.2.19r2=1.204.2.20
notify.c1.3.2.10 = 1.3.2.11

http://www.samba.org/cgi-bin/cvsweb/samba/source/printing/notify.c?r1=1.3.2.10r2=1.3.2.11

CVS update: samba/source/rpc_server

[jerry]

Date:   Sat Feb 15 23:33:30 2003
Author: jerry

Update of /data/cvs/samba/source/rpc_server
In directory dp.samba.org:/tmp/cvs-serv9059/rpc_server

Modified Files:
  Tag: SAMBA_3_0
srv_spoolss_nt.c 
Log Message:
* set PRINTER_ATTRIBUTE_RAW_ONLY; CR 1736
* never save a pointer to an automatic variable (they go away)
  implement a deep copy for SPOOLSS_NOTIFY_MSG to correct
  messages being sent that have junk for strings; 
  fix in response to changes for CR 1504
  

Revisions:
srv_spoolss_nt.c1.277.2.37 = 1.277.2.38

http://www.samba.org/cgi-bin/cvsweb/samba/source/rpc_server/srv_spoolss_nt.c?r1=1.277.2.37r2=1.277.2.38

CVS update: samba/source/include

[jerry]

Date:   Sat Feb 15 23:33:30 2003
Author: jerry

Update of /data/cvs/samba/source/include
In directory dp.samba.org:/tmp/cvs-serv9059/include

Modified Files:
  Tag: SAMBA_3_0
rpc_spoolss.h 
Log Message:
* set PRINTER_ATTRIBUTE_RAW_ONLY; CR 1736
* never save a pointer to an automatic variable (they go away)
  implement a deep copy for SPOOLSS_NOTIFY_MSG to correct
  messages being sent that have junk for strings; 
  fix in response to changes for CR 1504
  

Revisions:
rpc_spoolss.h   1.77.2.7 = 1.77.2.8

http://www.samba.org/cgi-bin/cvsweb/samba/source/include/rpc_spoolss.h?r1=1.77.2.7r2=1.77.2.8

CVS update: samba/source/printing

[jerry]

Date:   Sat Feb 15 23:36:18 2003
Author: jerry

Update of /data/cvs/samba/source/printing
In directory dp.samba.org:/tmp/cvs-serv9710/printing

Modified Files:
nt_printing.c notify.c 
Log Message:
* set PRINTER_ATTRIBUTE_RAW_ONLY; CR 1736
* never save a pointer to an automatic variable (they go away)
  implement a deep copy for SPOOLSS_NOTIFY_MSG to correct
  messages being sent that have junk for strings; 
  fix in response to changes for CR 1504
  

Revisions:
nt_printing.c   1.244 = 1.245

http://www.samba.org/cgi-bin/cvsweb/samba/source/printing/nt_printing.c?r1=1.244r2=1.245
notify.c1.15 = 1.16

http://www.samba.org/cgi-bin/cvsweb/samba/source/printing/notify.c?r1=1.15r2=1.16

CVS update: samba/source/rpc_server

[jerry]

Date:   Sat Feb 15 23:36:18 2003
Author: jerry

Update of /data/cvs/samba/source/rpc_server
In directory dp.samba.org:/tmp/cvs-serv9710/rpc_server

Modified Files:
srv_spoolss_nt.c 
Log Message:
* set PRINTER_ATTRIBUTE_RAW_ONLY; CR 1736
* never save a pointer to an automatic variable (they go away)
  implement a deep copy for SPOOLSS_NOTIFY_MSG to correct
  messages being sent that have junk for strings; 
  fix in response to changes for CR 1504
  

Revisions:
srv_spoolss_nt.c1.380 = 1.381

http://www.samba.org/cgi-bin/cvsweb/samba/source/rpc_server/srv_spoolss_nt.c?r1=1.380r2=1.381

CVS update: samba/source/include

[jerry]

Date:   Sat Feb 15 23:36:18 2003
Author: jerry

Update of /data/cvs/samba/source/include
In directory dp.samba.org:/tmp/cvs-serv9710/include

Modified Files:
rpc_spoolss.h 
Log Message:
* set PRINTER_ATTRIBUTE_RAW_ONLY; CR 1736
* never save a pointer to an automatic variable (they go away)
  implement a deep copy for SPOOLSS_NOTIFY_MSG to correct
  messages being sent that have junk for strings; 
  fix in response to changes for CR 1504
  

Revisions:
rpc_spoolss.h   1.94 = 1.95

http://www.samba.org/cgi-bin/cvsweb/samba/source/include/rpc_spoolss.h?r1=1.94r2=1.95