similar to: 2.0.4b - Bug in dfree > 2GB reporting for 16-bit clients

Have there been any problems reported with running 2.0.2 on servers using security=server with a 1.9.18p10 DMB? We've run into a situation where I've upgraded 4 of our servers to 2.0.2 but the DMB is still running 1.9.18p10. We have had sporatic trouble with the upgraded servers rejecting correct passwords because the DMB seemingly would not properly validate them. Today, we ran into a

I'm currently investigating the appearance of this error message for a significant number of our users' password change attempts. It would seem from my research that this error occurs when the data coming from the SamOEMhash function is not of the expected format/value. I do not know if this would be due to incorrect data being sent into the SamOEMhash function from the client or something

I posted my original question below to the samba-ntdom list but it seems to be the wrong place to be discussing this problem so I'm moving my follow-up to these lists. Background...I used to be using smbpasswd and the "unix password sync", "password chat", and "password program" settings to keep my smb passwords and unix passwords in sync. This was working well

skeet@Bridgewater.EDU wrote: > > > Basically what it looks like to me is that an smbd process is spawning a > child which goes defunct for some reason I have yet to determine and the > smbd process hangs out there waiting for the child. Of course the child is > never going to answer being defunct, so the parent smbd process sticks > around and keeps its oplocks. > That

> >> On Tue, Jun 07, 2016 at 01:36:52PM -0400, Thomas Schulz wrote: >>> Running Samba 4.3.4 on a Solaris 10 i386 box and Samba 4.4.3 on a >>> Solaris 10 sparc box. >>> I have not looked at the logs for awhile. Just checking now and I see >>> many of the following on both systems. >>> >>> [2016/06/01 11:22:04.402945, 0]

> On Tue, Jun 07, 2016 at 01:36:52PM -0400, Thomas Schulz wrote: > > Running Samba 4.3.4 on a Solaris 10 i386 box and Samba 4.4.3 on a > > Solaris 10 sparc box. > > I have not looked at the logs for awhile. Just checking now and I see > > many of the following on both systems. > > > > [2016/06/01 11:22:04.402945, 0]

I saw a little discussion about this a few weeks ago but nothing concrete. We're running samba-1.9.18p8 under Solaris 2.6x86. I am periodically getting the following in the logfiles, usually _many_ at a time: 1998/11/03 14:42:00 request_oplock_break: no response received to oplock break request to pid 5411 on port 40884 for dev = 1980040, inode = 33c4d When I look up the PID (in this case

I think that I know what is going on. At first I was getting bad numbers from the DEBUG statement. It turns out that %u does not work with an unsigned 64 bit integer. So instead of passing (*dsize) I had to pass (unsigned int)*dsize. Now I am getting good numbers. The problem only occures with Windows XP machines. We have our users automounted on /home/users. We have /home/users shared as share

Pam_SMB allows Linux clients to validate their passwords against an NT PDC, so the only thing you have to do is set up the accounts on the Linux side with an '*' in the /etc/passwd entry. This can be done using a list of users: #!/bin/bash for i in `cat myuserlist`; do /usr/sbin/adduser -p '*' $i with various other command line options, such as "-s

I'm useing Samba (2.0.7) on an Compaq TRUE64 (Digital OSF) Server. Everything is working fine, but the dfree-script does not work. I think it's not even called. The corosponding entry in my smb.conf is: [global] server string = Samba %v Server, xxxx workgroup = xxxx keep alive = 30 dead time = 15 dfree command = /usr/local/samba/bin/dfree The script it self works fine

Running Samba 4.3.4 on a Solaris 10 i386 box and Samba 4.4.3 on a Solaris 10 sparc box. I have not looked at the logs for awhile. Just checking now and I see many of the following on both systems. [2016/06/01 11:22:04.402945, 0] ../source3/smbd/dfree.c:139(sys_disk_free) WARNING: dfree is broken on this system What could be the cause of this? Tom Schulz Applied Dynamics Intl. schulz at

When using Samba 3.0.23b (slightly old, I know) on CentOS 4.4, smbstatus -B fails with a segmentation fault. smbstatus works, and tdbdump is able to dump brlock.tdb and locking.tdb without any errors (which is not what I expected). Here's the backtrace (non-ASCII characters replaced with 'X'): #0 0x0017fa2c in memcpy () from /lib/tls/libc.so.6 #1 0x0029b19f in tdb_write

The patch f045f459d925 ("drm/nouveau/fbcon: fix out-of-bounds memory accesses") tries to fix some out of memory accesses. Unfortunatelly, the patch breaks the display when using fonts with width that is not divisiable by 8. The monochrome bitmap for each character is stored in memory by lines from top to bottom. Each line is padded to a full byte. For example, for 22x11 font, each line

Hi, Some time ago, I reported an issue (1) regarding to the "disk free" to Quotas mapping when Unix Extensions are enabled. The issue still persists in RHEL 5.3 (samba-3.0.33-3.7.el5). In the meanwhile I have found a workaround via the attached *ugly* patch, but an official solution would be appreciated. Best regards, Juanjo (1)

On Tue, Apr 11, 2017 at 1:32 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > On Tue, Apr 11, 2017 at 1:11 PM, Alastair Bridgewater > <alastair.bridgewater at gmail.com> wrote: > > + /* HDMI 3D support */ > > + if ((disp->disp.oclass >= NV50_DISP) > > You probably meant G82_DISP. Although I don't know if there were any > G80's

[2799/3801] Compiling source3/locking/locking.c [2800/3801] Compiling source3/locking/brlock.c ../source3/locking/brlock.c: In function 'brl_get_locks_readonly_parser': ../source3/locking/brlock.c:2071: error: expected expression before 'struct' ../source3/locking/brlock.c:2071: warning: assignment makes pointer from integer without a cast ../source3/locking/brlock.c: In function

On Tue, Apr 11, 2017 at 1:11 PM, Alastair Bridgewater <alastair.bridgewater at gmail.com> wrote: > Enable stereoscopic output for HDMI and DisplayPort connectors on > NV50+ (G80+) hardware. We do not enable stereoscopy on older > hardware in case there is some older board that still has HDMI > output but for which we have no logic for setting the Vendor > InfoFrame. > >

This patch is just a (shameless) copy from bug #28 [1]. The original patch has been sitting there for a couple of years now, and it was based on Syslinux v 4.05. The patch I am posting here is just a re-base on v.6.03. Whichever inadequate formatting (tabs, trailing spaces...), or any kind of correction that was required for the original patch to be accepted, is probably still required now.

On Tue, Jan 17, 2017 at 5:42 PM, Alastair Bridgewater <alastair.bridgewater at gmail.com> wrote: > HDMI specification 1.4a, table 8-15 is very explicitly a "must > support at least one of" table, not a "must support all of" table. > It is not hard to find hardware that does not support some of the > so-called "mandatory" modes. > > More

Store the ELD correctly, not just enough copies of the first byte to pad out the given ELD size. Signed-off-by: Alastair Bridgewater <alastair.bridgewater at gmail.com> --- drivers/gpu/drm/nouveau/nvkm/engine/disp/hdagt215.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/nouveau/nvkm/engine/disp/hdagt215.c