On Thu, 11 Apr 2002, Beschorner Daniel wrote:
Hi!
Every time a user logs out from the Samba-PDC and the user profile is
written to the profile share on the Samba-PDC this error occures on some
(5-10) files of the profile in the log.
[2002/04/11 09:39:06, 0] smbd/open.c:open_file(179)
Update to bug list
On Fri, 17 May 2002, Gerald Carter wrote:
On Fri, 17 May 2002, Gerald Carter wrote:
* confirm/deny reports of access denied problems from
win2k client attempting to maniuplate printer properties.
* inherit acls crash on IRIX (reported by Nicholas Brealey)
*
On Tue, 28 May 2002, Michael Sweet wrote:
OK, I'm awake now and it's an easy fix; change ac_cv_enable_cups to
enable_cups, and then autoconf/configure again.
Updated patch is attached...
Applying to 2.2 now. HEAD to soon follow
cheers, jerry
On Tue, 4 Jun 2002, Michel Stoop (samba) wrote:
I think we already fixed this in the latest SAMBA_2_2
cvs code. Please retest and let me know.
I just updated my SAMBA_2_2 and the problem is still there.
Look in configure.in line 2730
WINBIND_LTARGETS=
So no winbind then
Simo,
I'm not willing to remove this for 2.2.5 at this point. As much trouble
as it has caused, it is hard to determine how removing it will affect
existing installations.
Granted there are other issues that need to be addressed.
jerry
On 4 Jun 2002, Simo Sorce wrote:
KILL IT
/simo
On Fri, 31 May 2002 [EMAIL PROTECTED] wrote:
source/lib/interfaces.c conditionally include sys/time.h and
sys/sockio.h (autoconf macros already exist)
This change broke SAMBA_2_2. The reason is that lib/interfaces.c
is used in the autoconf test so
On Wed, 26 Jun 2002, David W. Chapman Jr. wrote:
I think I've tracked down exactly what happened. A while back
someone sent some FreeBSD patches to fix the VFS modules WRT DYNEXP
flags. The flags that FreeBSD needs are DYNEXP=-Wl,--export-dynamic
Later on someone from openbsd posted
On Mon, 1 Jul 2002 [EMAIL PROTECTED] wrote:
Modified Files:
Tag: SAMBA_2_2
clientgen.c clilist.c libsmbclient.c
Log Message:
Include the patches by Tom Jansen. I have fixed a couple of problems, and it
compiles, but I have not tested it.
However, this week I will, because
On 28 Jun 2002, Simo Sorce wrote:
I may be wrong but I remember a fix in 2.2.5, I think jeremy or jerry
may tell you more however.
Not for tdb corruption.
On Fri, 2002-06-28 at 11:11, Volker Lendecke wrote:
On Fri, Jun 28, 2002 at 11:08:00AM +0200, [EMAIL PROTECTED] wrote:
- From
On Tue, 2 Jul 2002, Volker Lendecke wrote:
Thanks. I recently got another error message from that machine, running 2.2.4:
[2002/07/01 07:56:17, 0, pid=3781] passdb/passdb.c:pdb_init_sam(116)
pdb_init_sam: error while allocating memory
This essentially means that process 3781 can not
On Wed, 26 Jun 2002, Johnston, Christopher (DCSA) wrote:
Excellent.. however we are attempting to try and put together an LDAP
solution here at ML to keep a centralized database of SID-UID
mappings.. than letting the LDAP client make calls against the database
for a UID.. what we would need
On Wed, 3 Jul 2002, Richard Sharpe wrote:
Is there a reason that this has to go into SAMBA_2_2?
I don't work in any other area at the moment.
That's not a real good reason IMO. The libsmbclient
code should be sync'd between HEAD and SAMBA_2_2
so you should be able to work in either
On Wed, 24 Jul 2002, Boyce, Nick wrote:
San asked the original question.
*I* can't answer it, but I thought I'd help out by pointing out to him that
he didn't specify what kind of system compiler he's using.
He replied, but personally to me, which won't get him very far :-(
So here's his
On Thu, 1 Aug 2002, Steve Langasek wrote:
It appears that pam_smbpass is once again broken in HEAD, due to
unresolved symbols. The attached diff attempts a somewhat more
permanent solution to the problem.
Steve, The last time I checked pam_smbpass.so compiled fine
(this was as of yesterday
On Wed, 14 Aug 2002 [EMAIL PROTECTED] wrote:
I am tring to use the new method available for printing (MS-RPC) from my Win NT
4.0 Clients to my Samba Box (FreeBSD)
I have two problems:
1. The Printers Share that shows up under the server takes a long time to show
up.
This is probably smbd
On Wed, 14 Aug 2002 [EMAIL PROTECTED] wrote:
We run SAMBA on a Unix box with case sensitive file naming (i.e. standard
Unix usage).
Relevant entries in smb.conf
case sensitive = yes
This is really bad. Do no do this unless you are willing to suffer the
consequences of certain file
On Tue, 13 Aug 2002, Kapoor, Sandeep [IT] wrote:
Hello, (Resent with extension of .sh file changed to .txt to avoid block by
anti-virus software)
I have installed Samba 2.2.1a on Solaris 5.8 with NIS+ option. Initially I
was getting the following error
[2002/08/08 16:38:05, 0]
On Thu, 18 Jul 2002, Steve Langasek wrote:
Hello,
With the recent announcement that the Samba Team is focusing all further
development efforts on 3.0, a push has begun to sort through the niggly
issues that need to be resolved in order to produce packages for Debian
that can be uploaded
On Thu, 15 Aug 2002, Gerald (Jerry) Carter wrote:
On Thu, 18 Jul 2002, Steve Langasek wrote:
Hello,
With the recent announcement that the Samba Team is focusing all further
development efforts on 3.0, a push has begun to sort through the niggly
issues that need to be resolved
On Mon, 29 Jul 2002 [EMAIL PROTECTED] wrote:
Hello,
we use Samba 2.2.5 as a PDC. Profiles and Printer drivers are stored on
the server. Server OS is Solaris 7 intel.
HowTo show the problem:
Freshly installed WinNT SP6a Workstation. User Fred logs on. In his
profile Printer A is
On 29 Jul 2002, Bradley W. Langhorst wrote:
Do we really need a log at level 2 for successful database
connections?
I'm applying most of the other patches to HEAD now (after some more
testing). I'll leave this one for abartlet in case he feels it is
necessary.
cheers, jerry
On Sun, 11 Aug 2002, odc wrote:
brlock.tdb
byte range locking (volatile)
browse.dat
browse lists maintained by nmbd (volatile)
connections.tdb
connection information (volatile)
locking.tdb
share mode, oplocks, etc... (volatile)
messages.tdb
Samba messaging system (volatile)
On Fri, 16 Aug 2002, Tim Potter wrote:
On Thu, Aug 15, 2002 at 01:06:40PM +0200, Thomas Reifferscheid wrote:
If I have more then 21 printers in smb.conf I get
[2002/08/15 12:30:50, 5] rpc_parse/parse_prs.c:prs_werror(618)
000c status: WERR_INSUFFICIENT_BUFFER
with the
On Mon, 19 Aug 2002, Gerald (Jerry) Carter wrote:
On Mon, 19 Aug 2002, Thomas Reifferscheid wrote:
There is an undocumented feature in Samba_2_2, too.
rpc_server/srv_spoolss_nt.c, function static BOOL
add_printer_hook(NT_PRINTER_INFO_LEVEL *printer),
line 4880:
/* Set
On Wed, 28 Aug 2002, Richard Sharpe wrote:
On Tue, 27 Aug 2002, Luke Kenneth Casson Leighton wrote:
On Tue, Aug 27, 2002 at 11:13:10AM +0930, Richard Sharpe wrote:
BTW, did you see that the Extreme Blue team announced at CIFS2002 that
they had implemented shared libraries for external
On Thu, 5 Sep 2002, Arnold Jones wrote:
samba-technical,
When we switched to a new web site the document for some reason did
not make it. It is now at:
http://www.snia.org/tech_activities/CIFS
- Arnold
Thanks. I've posted a note about this on Samba.org. :-)
cheers, jerry
On Wed, 11 Sep 2002, Gavrie Philipson wrote:
What do you mean by saying 3.0 is not being maintained? I thought new
development work is being done on 3.0, and fixes on 2.2. Am I mistaken?
Development is going in in HEAD which will become 3.0. I'm a little
behind but will post the roadmap
On Sun, 1 Sep 2002, Juergen Hasch wrote:
attached are three small patches for Samba_2_2 CVS. The first patch
fixes a typo in web/swat.c.
The second patch changes a compiler option for AIX to allow the compiler
to use more memory.
The last patch updates the recylce bin. This change was
On Tue, 3 Sep 2002, Max TenEyck Woodbury wrote:
Once I've got the process down pat, I'd like to make a few changes in
the packaging for Red Hat linux distributions. I intend to make the
packages generated one-for-one replacements for the original Red Hat
packages. With the understanding that
Anyone?
Why do we still have a configure flag for this since it is selectable
at run time ?
cheers, jerry
On Thu, 26 Sep 2002, Jelmer Vernooij wrote:
On Thu, Sep 26, 2002 at 02:20:06PM -0500, Gerald (Jerry) Carter wrote about
'--with-libsmbclient=no the default ?':
I thought libsmbclient should be built by default in 3.0 ?
When ( why) did this change ? Was it me ?
According to configure.in
Folks,
With the release of 3.0alpha20, I'm declaring the official
maintainence of the SAMBA_3_0 cvs branch. WHat this means
is that there will be no more blind copy HEAD onto SAMBA_3_0
for the next alpha. Any bugs fixes into HEAD should also be fixed
in SAMBA_3_0. Developers are responsible
On Fri, 27 Sep 2002, Jelmer Vernooij wrote:
What should happen to features that are marked 'not required' on the
roadmap ? Should these go into HEAD or 3_0 when they are developed? What
about the sam system?
My opinion is that something that is not required for 3.0 to ship
should continue to
On Thu, 26 Sep 2002 [EMAIL PROTECTED] wrote:
Date: Fri Sep 27 01:02:37 2002
Author: abartlet
Update of /data/cvs/samba/source
In directory dp.samba.org:/tmp/cvs-serv18726
Modified Files:
configure.in configure
Log Message:
Readd the 2.2 --with-ldapsam paramaters so as
On Fri, 27 Sep 2002, Andrew Bartlett wrote:
OK, in HEAD I dropped 'ldap server' and 'ldap port' as parmaters, moving
to the 'passdb backend' scheme. However, this would mean that a valid
2.2 configuration would not function in 3.0.
This change (and the bit I forgot - making ldapsam the
On Mon, 30 Sep 2002, Gerald Carter wrote:
Thanks to Jelmer we mow have a good framework for adding
Developer specific documentation. See
http://www.samba.org/samba/ftp/docs/Samba-Developer-Guide.[pdf|html]
Should be
http://www.samba.org/samba/docs/Samba-Developers-Guide.[pdf|html]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Heads up everyone
This is a preview snapshot of SAMBA_2_2 cvs branch. This is a
non-production release provided for testing purposes only.
Hopefully this will be the last RC before the final release but
you never know until you taste it.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Can anyone comment on this?
On Tue, 15 Oct 2002, Louis-David Mitterrand wrote:
Upon upgrading from 2.2.5 to 3.0alpha20 on Debian unstable, filenames
with accented characters (ie: éàî etc.) became unreadable. For example
in W2K a filename
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Everyone,
I am glad to say that 2.2.6 is out and is the last planned 2.2 release.
I know many people have been working on Samba 3.0 for several months
now. Now we can all focus on 3.0. Thanks to everyone who helped
out in the past 4 months to get
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Let's stop cross posting this thread ok. If people are interested
in Samba development, they should be on this list anyways
On Tue, 22 Oct 2002, Luke Kenneth Casson Leighton wrote:
having done the surs draft RFC, and outlining the issues
in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please post general use questions to the [EMAIL PROTECTED]
list (see http://lists.samba.org/listinfo/samba for details).
The samba-technical mailing is for discussions of Samba
internals and development issues. Thanks.
jerry
On Wed, 23 Oct
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 7 Oct 2002, Hakanson, David J. wrote:
I am taking over the samba-audit patch (logs user actions to syslog)
written by Andy Bakun
(http://thwartedefforts.org/software/samba/samba-audit.html
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 18 Oct 2002, Jelmer Vernooij wrote:
Hi all!
I've tried to investigate what docs still need work before 3.0:
Outdated docs:
docs/OID/allocated-arcs.txt - does this file really belong here?
docs/OID/samba-oid.mail - does this file
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 19 Oct 2002, Kurt Pfeifle wrote:
I am going to look into the CUPS-related stuff. However, I still
need to get 1st Samba 3.0 installation up and running.
What is the projected timescale for a 1st release? (Of course,
there is no damage
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
FYI...
Just giving everyone a heads up. I will also roll RPMS
for the various RedHat versions on this release.
Also i will be examining the growing diff's between
HEAD and SAMBA_3_0 tomorrow probably. So beware if you
have not been merging
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 23 Oct 2002, Jelmer Vernooij wrote:
I was wondering whether we could move those to the 'web' CVS module..
they only confuse users when they're part of the distribution. (just a
detail, though)
I don't have a problem moving them to the web
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 23 Oct 2002, Jelmer Vernooij wrote:
On Wed, Oct 23, 2002 at 09:54:49AM -0500, Gerald (Jerry) Carter wrote about
'Planning 3.0alpha21 for Friday (10/25)':
FYI...
Just giving everyone a heads up. I will also roll RPMS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 17 Oct 2002, Jon Monroe wrote:
Hi Jerry,
I tried disabling kernel oplocks. I also tried disabling in different
combinations:
oplocks
level2 oplocks
posix locking
locking
All variations seem to produce similar results -- 2 extra
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steve,
Please post general use questions to the [EMAIL PROTECTED]
list (see http://lists.samba.org/listinfo/samba for details).
The samba-technical mailing is for discussions of Samba
internals and development issues. Thanks.
btwmake sure
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 17 Oct 2002, Christopher R. Hertel wrote:
Do I understand correctly that Samba does not offer a per-share
password, even when running under security=share?
In the original, outdated design of SMB (COREP.TXT) passwords were
assigned to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 18 Oct 2002, Christopher R. Hertel wrote:
That's what I thought. I'm not trying to make share-level security work
as originally intended, I'm just trying to figure out how we do it.
If the client sent an SMBsessetupX request, we save the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 22 Oct 2002, Stefan (metze) Metzmacher wrote:
Tag: SAMBA_3_0
samba2.spec.tmpl
shouldn't this move to samba3.spec.tmpl
Details, Details, Details, .
Eventually i will rename it, but just getting it working was
the first
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 24 Oct 2002, Rashkae wrote:
Has there ever been an explanation found for the brief rash of people
who had tidbits of Samba log file data inserted in their network shared
files when sharing over a Samba server?? If indeed that problem was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 25 Oct 2002, Gareth Davies wrote:
Apparently they need to be Global or Universal to be shown by Winbind.
Local groups are supported by winbindd using rpc. The LDAP backends for
winbindd needs this support added (it's a no-op function
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please post general use questions to the [EMAIL PROTECTED]
list (see http://lists.samba.org/listinfo/samba for details).
The samba-technical mailing is for discussions of Samba
internals and development issues. Thanks.
cheers, jerry
On Wed, 23
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 23 Oct 2002 [EMAIL PROTECTED] wrote:
Hi...
I still have a hope that you can help me...
I have to write a program that send text messages over SMB (AKA winpopup
messages), but have trouble. I do following things:
1) Resolving machine
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The original thread for this starts here in case anyone needs it
http://lists.samba.org/pipermail/samba-technical/2002-October/040119.html
John,
Does this look like your bug ?
http://lists.samba.org/pipermail/samba/2002-October/083160.html
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
After exluding these files from the diff
configure
CVS
*proto.h
The diff is still rather large. NMow I'm a little skeptical to think that
all the changes in HEAD are not meant for 3.0. My other conclusion is
that people have not been
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 25 Oct 2002, Jean Francois Micouleau wrote:
you mean local groups within the S-1-5-32 sid sub tree or the local
domain groups under the PDC SID ? If that's the first case, winbind
shouldn't even read them, they have no meaning outside
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25 Oct 2002, Simo Sorce wrote:
JF is totally right winbind should never ask for PDCs local group.
But there is a third option, MS has defined an obscure (to me) new type
of group in w2k, the global local group do you mean this one jerry?
Folks,
We have two bugs fixed since 2.2.6rc2 went out two days ago.
Please continue to test (especially Win9x batch file users).
See change log below
( Changes since 2.2.6rc2 )
81) Fix memory leak in smbspool
82) Fix bug in mangling code that resulted in Win9x clients not being
able
On Sat, 12 Oct 2002, Andrew Bartlett wrote:
We need a race-proof scheme to allocate RIDs, and I would prefer not to
need to use a local TDB - I would like it all 'in ldap', if at all
possible.
See the uidPool objectclass in samba.schema. You would do it like
this
do {
get the curent
On Sat, 12 Oct 2002, Andrew Bartlett wrote:
OK, that make much more sense. But what to do in between the delete and
the add? Spin, and hope the entry 'comes back'?
It should local the entry, test for the presence of the old
value/attribute before any delete, remove it, and add the new one.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 17 Oct 2002, Jon Monroe wrote:
I'm seeing tons of leftover directory handles for any directories
visited on a samba share (via a win2k/win9x workstation). For every
directory access inside a samba share, 3 handles are initially opened --
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 25 Oct 2002, Jean Francois Micouleau wrote:
ok then it's still a problem of vocabulary :) Can we settle on a
definitive wording ?
local groups, domain groups, domain local groups, universal groups.
Fine by me :-)
cheers, jerry
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 25 Oct 2002 [EMAIL PROTECTED] wrote:
I am facing problem with deleting drivers from the server. I am using
rpcclient tool to delete drivers. 'deldriver' is implemented in
cmd_spoolss.c. Kindly let me know if anything can be done.
What
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 29 Oct 2002, Axel Thimm wrote:
o tarfile: allow samba-${VERSION} to be a symlink to another directory
(e.g. plain samba)
Thanks.
o Use rpmbuild instead of rpm, as rpm under RedHat 8.0 does no more support
building etc.
Cool. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 29 Oct 2002, James Braid wrote:
I had the same problem aswell..
I found it was due to the fact the groups weren't 'Global' groups only
'Local' groups...
Apparently they need to be Global or Universal to be shown by Winbind.
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 30 Oct 2002, Andrew Bartlett wrote:
No, no more than you can indicate SASL preferences in a URL. You
*could* embed this information in a URI string, but there would be
nothing particularly standard about this, and the LDAP libraries
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 24 Oct 2002, Lars Madsen wrote:
I have just upgraded a previous (I don't have the versione number any
more) XP to XP version 5.1 (and later to SP1) Both are the professional
danish version.
Ummm... I didn't know know that there is a new
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 2 Nov 2002, Andrew Bartlett wrote:
If we are a normally bound to an ldap slave, and use and ldap referral
to contact the master, we encounter the problem that the slave hasn't
caught up by the time we do the next search on the slave.
This
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 6 Nov 2002, Sean Gillaspy wrote:
Thank you.
You can unsubscribe yourself at http://lists.samba.org/
cheers, jerry
-
Hewlett-Packard
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 8 Nov 2002, Arne wrote:
Adding smbfs to the kernel gives a slightly larger kernel, found out. What
portons of samba is unneeded with such a kernel (2.4.18)?
The kernel docs refer to samba.org to find out, but I don't find it there.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 7 Nov 2002, Urban Widmark wrote:
On Wed, 23 Oct 2002, Gerald (Jerry) Carter wrote:
Any chance of someone reviewing and possibly adding these changes before
then? I first posted this on the 19th.
I'll grab them.
Did you do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 8 Nov 2002 [EMAIL PROTECTED] wrote:
We are using Samba 2.2.6 at our site on Solaris 8 in conjunction with
nss_ldap from padl.com. We often use the valid users option in our
smb.conf to restrict access to a given share to members of a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 9 Nov 2002, Jelmer Vernooij wrote:
Hi!
I've written a simple script to produce daily snapshots of the 3.0 and
HEAD branches. Available at:
http://samba.org/~jelmer/snapshot/
All I ask is that people be good citizens and use bandwidth
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 12 Nov 2002, Paul Reilly wrote:
I'd like to link a program against the winbind libraries, so that it can
call a winbind function to do a NT authentication. Is the winbind API
described anywhere, or can anyone point me to the function call
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 20 Nov 2002, Jeff Mandel wrote:
Since the recent announcement for the 2.2.7 release, I looked again for
solaris binaries. For a while there were packages up to 2.2.4. After
2.2.5 came out the others vanished and 2.2.2 and 2.0.7 were left.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 22 Nov 2002, Steve Langasek wrote:
On Fri, Nov 22, 2002 at 02:31:21PM -0800, Martin Pool wrote:
According to samba.html, the distribution key is
http://us1.samba.org/samba/ftp/samba-pubkey.asc
gpg: key 2F87AF6F: public key
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 26 Nov 2002, Green, Paul wrote:
In the last day, someone has added a call to inet_aton to
samba/source/lib/util_str.c.
Stratus VOS does not have this function. Rsync happens to have a substitute
implementation of this function in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 27 Nov 2002, Stefan (metze) Metzmacher wrote:
I think adding VFSLIBDIR is not nice, because jelmer is working on the
modules stuff in HEAD and we'll load the modules via the 'modules = '
and 'modules path =' (not yet added) parameters. and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 27 Nov 2002, Stefan Metzmacher wrote:
I decided with Jelmer that the codepages/*.dat files should be installed
in ${datadir}/samba witch is ${prefix}/share/samba
Great that you decided, but no one told me about that.
And the Makefile had
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 27 Nov 2002, Stefan Metzmacher wrote:
At 10:21 27.11.2002 -0600, Gerald (Jerry) Carter wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 27 Nov 2002, Stefan Metzmacher wrote:
I decided with Jelmer that the codepages
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 28 Nov 2002, Kätzler, Ralf wrote:
I like to use a samba-server as printer-server for about 500 users with
~ 40 different printers. The client OS is NT4 or XP. The problem I
encountered is that there are printerdrivers out there which use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 27 Nov 2002, Jim Morris wrote:
Now their corporate headquarters has identified this issue (unlimited
login attempts allowed) as the primary violation on a recent security
audit of the network in this branch office of the company. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 28 Nov 2002, Olaf Flebbe wrote:
A samba server with encrypted paawords on Solaris8 does not correctly
handle passwords containing more than eight characters. A local
smbclient can correctly handle this situation, but NT 4.0 and W2K cannot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 3 Dec 2002, Matthew Mastracci wrote:
I just spent a few hours diagnosing a problem with 2.2.7 on Redhat 7.3
that turned out to be (what I believe) is a packaging bug.
The symbolic link from libnss_winbind.so to libnss_winbind.so.2 is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 25 Nov 2002, Ken Cross wrote:
G'Day:
In the get_pdc_ip routine in libsmb/namequery.c in -current, there's an
assertion:
SMB_ASSERT(count == 1);
which bombs out if the PDC has multiple IP addresses. I have a PDC with
3 network
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Anyone?
Can someone confirm or deny that there is not net equivalent
of smbpasswd -j DOMAIN -R PDC in HEAD? All I see requires an admin
username/pw
cheers, jerry
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 4 Dec 2002, Jim McDonough wrote:
Can someone confirm or deny that there is not net equivalent
of smbpasswd -j DOMAIN -R PDC in HEAD? All I see requires an admin
username/pw
Just net rpc join should do it.
Try net help rpc join
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 4 Dec 2002, Jim McDonough wrote:
Can someone confirm or deny that there is not net equivalent
of smbpasswd -j DOMAIN -R PDC in HEAD? All I see requires an admin
username/pw
Just net rpc join should do it.
Try net help rpc join
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 4 Dec 2002, Ken Cross wrote:
To Jerry's original question: it seems to fail without an admin
username/pw. With the old smbpasswd, it would work if a machine account
was first set up on the PDC -- now it doesn't.
I found some code named
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 5 Dec 2002, Rafal Szczesniak wrote:
I found it. Who came up with the function names? They're horrible!
Originally it was an attempt to follow underlying mechanism name.
As 'net' gets general and therefore complicated tool, we getting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 4 Dec 2002, Zdenek Niederle wrote:
I'm using Samba 2.2.5 and CUPS to handle printing on our network.
Unfortunately, the smbprn.xx spool files are not being cleaned up
and instead are quickly filling the spool directory. Is their a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 5 Dec 2002, Rafal Szczesniak wrote:
Oh, it's being changed now, by me. I recently renamed the file and put
another trust-related function there. I'm also going to rename the
just_change_the_password() and (possibly) give it more general
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 11 Dec 2002, David Lechnyr wrote:
While convenient for web browsers, it's not exactly backwards-compatible
for both GPG and the average sysadmin who's probably struggling with
verifying PGP signatures for the first time. It's not Samba's
In case anyone missed this...
cheer, jerry
Original Message
-BEGIN PGP SIGNED MESSAGE-
- --
Title: Flaw in SMB Signing Could Enable Group Policy to be
Modified (309376)
Date:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In case someone needed this
jerry
- -- Forwarded message --
Date: Wed, 11 Dec 2002 21:23:59 -0500
From: Eric Nichols [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Finding Domains in the GC
I answered my own question. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
stored in clear text in secrets.tdb (HEAD) when i join an NT 4.0
domain? It doesn't store the the last change time either.
Unless someone yells, i'm going to fix this.
cheers, jerry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan,
Please send me the patch and I'll work on getting it in.
cheers, jerry
On Fri, 6 Dec 2002, Dan Kegel wrote:
Here's the only use of HAVE_GETTIMEOFDAY_TZ:
void GetTimeOfDay(struct timeval *tval)
{
#ifdef HAVE_GETTIMEOFDAY_TZ
1 - 100 of 177 matches
Mail list logo
