similar to: Failure in "man 8 vfs_full_audit"?

Hello All, now that the BUG 14343: (s3: vfs_full_audit: Add missing fcntl entry in vfs_op_names[] array.) was fixed I wanted to try 4.12 again. This is the relevant config which has been running for years: vfs objects = acl_xattr full_audit shadow_copy2 full_audit:failure = none full_audit:success = pwrite write rename unlink full_audit:prefix = IP=%I|USER=%u|MACHINE=%m|VOLUME=%S

On Fri, 11 May 2018 09:14:24 +0200 Marco Gaiarin via samba <samba at lists.samba.org> wrote: > Mandi! Rowland Penny via samba > In chel di` si favelave... > > > You would replace 'FACILITY' with one of the facilities shown in > > 'man syslog' e.g. full_audit:facility = LOG_AUTH > > OK, done. But samba (as stated in previous email) still reply:

Hello alAl, after update of our test server to 4.12.1 from 4.11 it crashes. If the vfs module is removed from the config everthing works as before. Logs from the crash see here: .0.31:445] Apr 16 13:36:47 lx-sv-03 smbd_audit[6263]: [2020/04/16 13:36:47.546559, 0] ../../source3/lib/util.c:830(smb_panic_s3) Apr 16 13:36:47 lx-sv-03 smbd_audit[6263]: PANIC (pid 6263): vfs_full_audit.c: name table

I've tried to setup VFS full audit facility in some share, like: vfs objects = [...] full_audit full_audit:prefix = %S|%d|%I|%M|%u full_audit:success = mkdir rmdir read pread write pwrite rename unlink full_audit:failure = none full_audit:facility = auth full_audit:priority = info but samba refuse 'full_audit:facility = auth' as a good

On Thu, 10 May 2018 15:31:23 +0200 Marco Gaiarin via samba <samba at lists.samba.org> wrote: > > > > >From 'man vfs_full_audit' > > > > > > full_audit:facility = FACILITY > > > Log messages to the named syslog(3) facility. > > > > > > See 'man syslog' for the 'facilities' you can use.

Hi Samba, I am configuring a samba on CentOS 6.6. I would like set up an full audit log on it but encounter below error message in /var/log/messages. Do you know any reason and can you fix it for me? Thanks [root at ndfss ~]# uname -a Linux ndfss 2.6.32-504.1.3.el6.x86_64 #1 SMP Tue Nov 11 17:57:25 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux [root at ndfss ~]# uname -m x86_64 [root at ndfss ~]#

Mandi! Rowland Penny via samba In chel di` si favelave... > >From 'man vfs_full_audit' > > full_audit:facility = FACILITY > Log messages to the named syslog(3) facility. > > See 'man syslog' for the 'facilities' you can use. [2018/05/08 17:34:42.388486, 0] ../source3/param/loadparm.c:1179(lp_enum) lp_enum(LOG_AUTH,enum): value

On Tue, 8 Oct 2024 00:20:44 -0400 samba3to4 via samba <samba at lists.samba.org> wrote: > Hello Experts, > > I am trying to migrate a Samba 3.6 server to Samba 4.19. > > [...] > > The log file shows that the user can authenticate: > > [2024/10/07 23:27:24.974539, 2] ../../source3/auth/auth.c: > 338(auth_check_ntlm_password) check_ntlm_password:

Hello Experts, I am trying to migrate a Samba 3.6 server to Samba 4.19. The OS of the old server is FreeBSD 10.3 and the new one is FreeBSD 14.1. The client computers are Win 10 Pro. Simple Samba configuration, no need for Active Directory, just a file server with user authentication. On the Windows computer I try to mount the shares from the new server as \\[new server IP address]. The log

HI all, So I'd like to log the user's operations on some shares. As I need to know who made what when. I'd read a previous answer from Andrew about auditing, so I can see loggued operations. Modified smb.conf : > [global] > vfs objects = dfs_samba4, acl_xattr, full_audit > full_audit:success =none > full_audit:failure = none share is : > [journal] > path =

On 11 May 2018 at 10:58, Rowland Penny via samba <samba at lists.samba.org> wrote: > On Fri, 11 May 2018 09:14:24 +0200 > Marco Gaiarin via samba <samba at lists.samba.org> wrote: > > > Mandi! Rowland Penny via samba > > In chel di` si favelave... > > > > > You would replace 'FACILITY' with one of the facilities shown in > > >

On 11 May 2018 at 23:53, Jeremy Allison <jra at samba.org> wrote: > On Fri, May 11, 2018 at 09:33:15PM +0100, Rowland Penny via > samba-technical wrote: > > On Fri, 11 May 2018 13:17:52 -0700 > > Jeremy Allison <jra at samba.org> wrote: > > > > > On Fri, May 11, 2018 at 09:56:47PM +0200, Timur I. Bakeyev via samba > > > wrote: > > >

Hi, I scribbled a simple guestfs based program called guestfs-xfer with following synopsis: Usage: guest-xfer [options] [op] [diskimage] op = [ls|cat|write] options: -d, --guestdevice DEV guest device --blocksize BS blocksize [default: 1048576] -o, --offset OFF offset [default: 0] So eg. `cat /dev/urandom | guest-xfer -d /dev/sda

On 11 May 2018 at 18:21, Rowland Penny via samba-technical < samba-technical at lists.samba.org> wrote: > On Fri, 11 May 2018 17:56:44 +0200 > "Timur I. Bakeyev" <timur at com.bat.ru> wrote: > > > On 11 May 2018 at 17:00, Rowland Penny via samba-technical < > > samba-technical at lists.samba.org> wrote: > > > > > On Fri, 11 May 2018

Forgot to mention that this is on Centos 8. So maybe something different than this: https://www.spinics.net/lists/samba/msg163085.html Regards Christian Am 16.04.20 um 13:45 schrieb Christian Naumer via samba: > Hello alAl, > after update of our test server to 4.12.1 from 4.11 it crashes. If the > vfs module is removed from the config everthing works as before. Logs > from the

On Tue, 2017-09-19 at 17:02 +0200, L.P.H. van Belle via samba wrote: > Hai Mark, > > I see the bugreport for this is still untouched. > https://bugzilla.samba.org/show_bug.cgi?id=11998 I've closed that bug now. Extensive work has been done to add this feature to Samba 4.7, due out this week: https://wiki.samba.org/index.php/Setting_up_Audit_Logging Two new debug classes,

On 06. aug. 2018 16:37, Oleg Cherkasov via samba wrote: > On 06. aug. 2018 15:15, Oleg Cherkasov via samba wrote: >> >> This morning three of our FreeBSD-11.1-p11 servers with Samba 4.7.7 >> installations started to ignore ACL settings and reject user access to >> shares.  All three servers are members of DC running on Windows Server >> 2008R2.  Everything has

On Mon, Aug 20, 2012 at 04:30:13PM -0700, Jakob Stoklund Olesen wrote: > All, > > The code generator operand class, MachineOperand, has an 8-bit TargetFlags field that the individual targets can use as they please. X86 and ARM use it to encode linker magic on symbol operands. > > It has been mentioned a couple of times on this list that it is not safe to use TargetFlags on

Tom, On Aug 21, 2012, at 11:21 AM, Tom Stellard <thomas.stellard at amd.com> wrote: > I've been working on replacing the MachineOperand flags in the R600 > backend with immediate operands, but I can't figure out how to modify > the instruction patterns to make this work. For example, I have the class: > > class R600_1OP <bits<32> inst, string opName,

Hi, I'm hoping somebody can point me in the right direction. My samba version is samba-4.2.10-6.2.el7_2.x86_64. I have lots of daily core dumps (~20 on each machine daily) and I have no clear idea why. I'm including the stack trace below. It looks like the problem is related to "invalid lock_order". Any ideas? Thanks, Sergei #0 0x00007fc5a34945f7 in raise () from