similar to: Wrong output from smbstatus

samba@samba.org schrieb: > SAMBA Digest 1928 > > For information on unsubscribing see http://samba.org/listproc/ > Topics covered in this issue include: > > 1) Re: NT Logon Authentication > by Gerald Carter <cartegw@Eng.Auburn.EDU> > 2) Samba-> No [.] and [..] directories > by Kai Schaeffer

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

Hello, If I use Samba as a PDC, what does the output from "smbstatus" mean? Will all logged in users be displayed at all times when I do "smbstatus -b"? The reason I ask is that users who are logged in occasionally disappear from the output of smbstatus, even though they are still logged in. Is this to be expected? regards, David

Can anyone tell me how smbstatus does its host name resolution? When I run smbstatus with no switches (3.0.20 on Suse 10.0), the output of hosts mostly shows IP addresses, but a couple hosts will show up by name. I've confirmed that all of the hosts are resolving in DNS through both forward and backward lookups (dig and dig -x) from the Samba host. Also, wins lookups also seem correct

Hey all, I'm preparing to start development of a new version of 'smbstatus' that produces XML output, instead of the tabular data it currently produces. This follows an attempt to parse the output of the current 'smbstatus' ( 3.0.22) using grep and a few other shell tools, from a system call in PHP, and then further RegEx parsing to create a multidimensional array of the

Somemore information regarding the smbstatus error. The sigbus error is occuring where I noted below. I now have data values to go along with the location. The SIGBUS generating bit is "entry_scanner_p->e.pid" which looks to be in an unaccessable area of memory. Looking back through the code, I find a couple of bizarities. For example file_scanner_p->num_share_mode_entries

-------- Original Message -------- Subject: smbstatus getting a SIGBUS error Date: Thu, 08 Jun 2000 13:52:13 +0700 From: Arnold Troeger <stssart@bkk.unocal.com> To: samba-bugs@samba.org CC: arnold.troeger@bkk.unocal.com I'm running Samba 2.0.7 and have been having a few problems with it. Just to keep things focused, I'll stick with smbstatus as this one has been the longest lasting

On Mon, 4 Feb 2019 18:44:57 +0100 Meike Stone via samba <samba at lists.samba.org> wrote: > Hello dear group, > > we have migrated our Samba server from version 3.6 to Samba 4.6. > > Everyting is working fine, but I have seen one difference in the > output from "smbstatus -b". > > The hostname in the output is no longer displayed (see examples below)

On Mon, 4 Feb 2019 20:32:53 +0100 Meike Stone via samba <samba at lists.samba.org> wrote: > Hello Rowland, > thanks for answering so fast. > > > > > > > we have migrated our Samba server from version 3.6 to Samba 4.6. > > > > > > Everyting is working fine, but I have seen one difference in the > > > output from "smbstatus -b".

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

Hi all, I just figured out something that I could not find any solutions on any where, and thought I'd share it with you. Initially I had a standard rpm install from the distribution for Samba (2.2.1a). A new fix version came out and since the rpm version was older I decided to switch to installing from src (2.2.2). Then in a weak moment I executed an online software upgrade, in

Hi, I updated from Samba 2.2.5 to 2.2.8a. und Redhat 6.2 and since then, smbstatus shows strange values The dates and the pid's are wrong. Any ideas? Was there a change in a locking.tdb? Do I have to remove it? Greetings Hansj?rg 28643 DENY_NONE 0x3f407996 RDONLY LEVEL_II ?7??W? Tue Jan 6 22:38:12 1970 1633824626 0x706d622e NONE ?7??W? Thu Jan 1 02:00:00 1970 1836017711 0x56414143

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 ----------------------------------------------

Hello Rowland, thanks for answering so fast. > > > > we have migrated our Samba server from version 3.6 to Samba 4.6. > > > > Everyting is working fine, but I have seen one difference in the > > output from "smbstatus -b". > > > > The hostname in the output is no longer displayed (see examples below) > > 1) The hostname must come from

Hi we use samba 3.0.25a on FreeBSD 6.2. We use a 'multiple' approach on our server: we have a smbd daemon for the Users section (with its configuration file) and a smbd daemon for the Groups section (with another configuration file). We would like to discriminate the locks and the other details for these two daemons: we would like to have a report for smbd-users and a report for

Hello dear group, we have migrated our Samba server from version 3.6 to Samba 4.6. Everyting is working fine, but I have seen one difference in the output from "smbstatus -b". The hostname in the output is no longer displayed (see examples below) 1) The hostname must come from Session setup or similar, because we don't have any name resolution for clients. 2) The hostname from

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

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

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

Have just upgraded to samba 1.9.18p3 on a RedHat 5.0 linux system... now... when i type smbstatus... this is what i get.. Couldn't open status file /var/lock/samba/STATUS..LCK so i assume that for some reason... this status file is not created upon startup.. Pat.