similar to: smbstatus after upgrade from 3.5 to 3.6

Dear list, I have just upgraded our main Samba server from version 2.2.8a to 3.0.6. It seems to be working fine except for 2 things: 1. when I use smbstatus(or swat/status) only some of the connections are listed and then smbstatus hangs forever(swat comes back after a while, but only with some of the connections) Have any of you experienced something similar ? How can I debug

Hallo, in 3.0.8pre2 the smbstatus command always shows connections _and_ shares even if using the switches '-p' for showing processes only or '-S' for showing shares only or '-B' for showing locks only: test2 # smbstatus --help Usage: [OPTION...] -p, --processes Show processes only -v, --verbose Be verbose -L, --locks

I am running Samba version 2.0.6 on Solaris 2.6. When I run smbstatus, it coredumps. Here is some detailed information that may help in killing this bug. This is a run of smbstatus where it coredumps, and afterwards, a gdb session. root@grads:/depot/samba-2.0.6/bin 174# ./smbstatus Samba version 2.0.6 Service uid gid pid machine ----------------------------------------------

Because of Plain text mode, my output example is split across several lines and hence is totally meaningless. If you want to see the example, follow this link : http://download.caoba.fr/r3tb7hxb2pl5/ I marked in red the places where the bug appears. ------------------------- Santiago DIEZ Quark Systems & CAOBA 23 rue du Buisson Saint-Louis, 75010 Paris ------------------------- On Thu, Feb

hello, can anybody explain or point me to a document that explain the locked files section produced by smbstatus -L (see below). what means denymode ? access ? what means exclusive+batch in the oplock section ? can anybody point me to a document explaining the way file locking works ? regards # smbstatus -L Locked files: Pid DenyMode Access R/W Oplock Name

Hi, I just installed Samba 3.0.4 on a Solaris 2.6 server. I had no problem compiling, intalling and configuring it, and everything seems to go OK. People can connect to all the configured shares without any problem. But I have some problems when getting server status either via SWAT/STATUS or using smbstatus: First, in the "Client" field of the SWAT/STATUS report I have problems

Currently I'm running Samba 1.9.18p3 on a production server. Smbstatus gives wrong information about locked files. For a client, still connected but closed the program, smbstatus still displays the locked files. Is there a solution or parameter I missed ? I think I read it somewhere in a digest but can't find it anymore. Can anyone direct me to the digest or know the problem ? I didn't

Hello, we frequently face locking issues with office applications and documents on samba shares. The office applications claim that the document is locked and hence no write access is possible. I can check on the samba server that there is no concurrent access/locking from other computers or users. It looks like the same user holds some lock and is denied to access the document because it?s

Hello all, I get the following and am not sure what is going on. Its on a solaris10 box. And my share is named 'hold' Thanks, Abhimanyu. # /opt/samba/bin/smbstatus Processing section "[hold]" Error loading module '/opt/samba/lib/charset/ISO8859-1.so': ld.so.1: smbstatus: fatal: /opt/samba/lib/charset/ISO8859-1.so: open failed: No such file

Hi all, But I do see the protocol version against each client connection in smbstatus output as below, =============================================================================== Samba version 4.2.0rc5 PID Username Group Machine Protocol Version ------------------------------------------------------------------------------ 10350 -1 -1

Hi, My output of smbstatus is bugged somehow in the Locked files section. For every line with a non ascii character, the whole string from the character to the end (included) is removed. Hence the line is attached to the next one. Here is a simplified example Locked files: Pid ... SharePath Name Time --------------------------------- 8910 ... /path

linux 2.0.35, samba2.0.0 compiled from tgz. I have: character set = ISO8859-1 and client codepage defaults to 850, so that testparm shows client code page = 850 With samba 1.9.18p8, smbstatus showed the filenames with localized characters ok (ie: libert?.txt) I use the same smb.conf with 2.0.0 Now, with samba 2.0.0, if I connect with smbclient to a Samba share I see those characters ok, but

Have any of you seen behavior like this before? We are currently having problems with our Samba server coming up telling a lot of our users that Word files "are locked for editing." and will only let users open them Read Only. We are running Samba 2.2.5 from standard RedHat 7.2 RPMS, on i386 RedHat 7.2, Kernel 2.4.9-34smp. Im putting this to the list as a symptom to see if anyone has

Sorry I should have said in my original post, this server is a NT4 style domain server. Looking in /var/log/samba I see log files with the machine names in the file names, so samba definitely knows the machine names. On Thu, Dec 18, 2014 at 1:17 PM, Ricky Nance <ricky.nance at gmail.com> wrote: > > Mark, I think (and I may be wrong here, so if a dev sees this correct me) >

Hi, testparm: --------- testparm shows: ERROR: the 'passwd program' (/usr/bin/passwd %u) requires a '%u' parameter. You can see, passwd program _is_ /usr/bin/passwd %u smbstatus: ---------- smbstatus command always shows processes _and_ shares even if using the switches '-p' for showing processes only or '-S' for showing shares only or '-B' for

L.S. We use SAMBA 2.0.7 on SGI IRIX 6.5.4m to facilitate using unix shares on NT/W95 clients. I created a users.map with e.g. next line: aitht = nltroo01 when NT-domain user nltroo01 maps a unix share (via unix homes share) indeed his unix home directory (usr/people/aitht) is mapped to the client. Inspecting the process on the SGI-machine (SGUX07) with smbstatus however shows that user nobody

Mark, I think (and I may be wrong here, so if a dev sees this correct me) smbstatus works with sockets. With that being said, I don't think it has been updated to work with samba as an AD DC, but should still work fine on other configurations (member server, legacy DC, etc). If you are running with a non ad dc config, let us know, there may be a bug there. Ricky On Wed, Dec 17, 2014 at 5:12

In Samba 4.1 I get the following output for smbstatus: Samba version 4.1.1 PID Username Group Machine ------------------------------------------------------------------- 2482 john Everyone 10.0.0.109 (ipv4:10.0.0.109:49178) 7364 george Everyone 10.0.0.60 (ipv4:10.0.0.60:49232) In Samba 3.6 it was like this: Samba version 3.6.24 PID

character set = iso8859-1 client code page = 850 Through win9x I save a file, whose filename contains characters as: ? ? ? ? ?, on a samba share. I can see those filenames (on a samba share) ok through win9x explorer. I can see those filenames ok through ls on linux. If I open one of those file, and then look at locked files with smbstatus, they are showed with a LF in place of the localized

I've recently added the following line to inetd.conf, to allow clients to connect at Port 445: microsoft-ds stream tcp nowait root /usr/local/sbin/smbd smbd -d 1 That works, but the connections that are started that way produce the machine name "smbd" in the output of "smbstatus". The machines that connect to the main listener (at port 139, started with