similar to: was code added to detect or die on sighup recently?

Hi, I''ve created snapper packages for Ubuntu, available on https://launchpad.net/~snapper/+archive/stable. For those new to snapper, it''s a tool for managing btrfs snapshots (http://en.opensuse.org/Portal:Snapper). It depends on libblocxx available from https://launchpad.net/~bjoern-esser-n/+archive/blocxx , and currently uses git source up to commit 50dec40. I''ve done

sorry forgot to follow the protocol, now included RFC in the subject. Hi, Appears that no one is working on the auto-snapshot feature for btrfs, so here I am implementing the same. Below is a draft on the feature list. Any comments / questions / suggestions are welcome, please do let me know. btrfs auto snapshot feature will include: Initially: - configurable timely

is this module still maintained and working? https://www.samba.org/samba/docs/current/man-html/vfs_snapper.8.html starting to set up the pieces, I have snapshots in btrfs with snapper itself but so far nothing visible on the windows explorer side. As always I rtfm all over ;-) I assume I have to do some extra magic to allow the winbind users/groups in ... in the related snapper-config I

My setup is Samba/smbclient version 3.0.1 on linux RedHat 9. \\snapper\dfs is a dfs share on snapper, a Win2k3 Active Directory server. My smb.conf contains: [global] realm = ciswinnet.cis.uab.edu workgroup=CISWINNET security = ADS encrypt passwords = yes password server = snapper.cis.uab.edu client use spnego = yes I am trying to run the following command: smbclient \\\\snapper\\dfs

Am 20.06.24 um 17:32 schrieb Stefan G. Weichinger via samba: > Am 19.06.24 um 14:21 schrieb Stefan G. Weichinger via samba: > >> opened a ticket at https://github.com/openSUSE/snapper/issues/917 as well > > Did some debugging with their devs, now I found this samba-bug: > > https://bugzilla.samba.org/show_bug.cgi?id=14896 > > comment 2 might point out the actual

Am 20.06.24 um 17:51 schrieb Stefan G. Weichinger via samba: > So my alternative might be dropping snapper and do the btrfs-snapshots > plus the rotation etc with self-written (=copied) scripts and timers. > > vfs_shadow_copy2 worked in my tests, I only switched to vfs_snapper > because it looked promising to have all the rotation and cleanup of > snapshots done by snapper

Am 19.06.24 um 14:21 schrieb Stefan G. Weichinger via samba: > opened a ticket at https://github.com/openSUSE/snapper/issues/917 as well Did some debugging with their devs, now I found this samba-bug: https://bugzilla.samba.org/show_bug.cgi?id=14896 comment 2 might point out the actual issue with the code, I don't know

Hello, We''re a team of 4 final year computer science students and are working on generating a diff between file system snapshots using the send receive code. The output of our utility looks like this- (I''ve tested it on a small subvol with minimal changes just to give an idea) root@nafisa-M-6319:/mnt/btrfs# btrfs sub diff -p /mnt/btrfs/snap1 /mnt/btrfs/snap2

Sorry Hughes, got some questions. I have the feeling that I do a lot wrong. Today I sent a mailing post at fedora where it is also about btrfs under fedora. In time when i write the mail i forward it my patch for fedora 25 pretransaction & snapper.yp, with the hope of feedback. https://lists.fedoraproject.org/archives/list/devel at lists.fedoraproject

Am 19.06.24 um 12:36 schrieb Rowland Penny via samba: >> ALLOW_GROUPS="domain\ admins" > ^^^^^^^^^^^^^^^^ > Where are you getting this from ? :-) > If I run this in a terminal: > > ALLOW_GROUPS="domain\ admins" ; echo "$ALLOW_GROUPS" > > I get this: > > domain\ admins > > Note that the

Hallo Hughes, thanks to let me know. It is good that you have a focus on LTS 4.9. Unfortunately it is so that the new graphics cards from amd to today are not served in the opensource. That's why I'm experimenting with the latest stable versions and what is so. My laptop has done the linux-firmware update well, it is nevertheless one of the newest. The kernel and appropriate

(Samba 3.0.1, RedHat 9, share is a w2k3, security = ADS) Here is a snippet of debug level 3 output of an smbclient tar operation, with error at the end. Command is: # smbclient \\\\snapper\\dfs <password> -U Administrator -E -W CISWINNET -D home -d3 -Tqca /tmp/test.tar [2004/01/14 15:05:10, 3] lib/util.c:dos_clean_name(549) dos_clean_name

On Wed, 19 Jun 2024 11:59:41 +0200 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > Am 19.06.24 um 11:35 schrieb Stefan G. Weichinger via samba: > > Am 17.06.24 um 16:06 schrieb Rowland Penny via samba: > > > >>> The user is member of "domain admins", isn't that enough? > >> > >> No, because they would

Hi, guys. I'm new to all of this and need some help with a problem I've been banging my head against for a while. (Tried troubleshooting, checking logs, and lots of Googling for a few weeks now, but just keep hitting dead ends.) SYMPTOM: Missing file `/usr/lib/x86_64-linux-gnu/samba/vfs/glusterfs.so`, as evidenced by error messages like these: [2018/11/18 07:56:42.551587, 0]

Am 19.06.24 um 12:46 schrieb Stefan G. Weichinger via samba: > Am 19.06.24 um 12:36 schrieb Rowland Penny via samba: > >>> ALLOW_GROUPS="domain\ admins" >> ??????????????? ^^^^^^^^^^^^^^^^ >> ??????????????? Where are you getting this from ? > > :-) > >> If I run this in a terminal: >> >> ALLOW_GROUPS="domain\ admins" ;

Hello list, following the guidance from here (https://wiki.samba.org/index.php/Setting_up_a_Share_Using_Windows_ACLs) I have set up a file server which is member of a Samba 4.6.9 AD domain. I have created ACLs using a Windows client with a domain admin account. While I have no issues with some folders, the server denies access to others to users that should have access by means of group

Hi all, Just out of curiosity: is there anything we can do, on the samba side, to counter the recent ransomware attacks? (or limit the damage done) I'm thinking like: limit the number of files per second a client (workstation) is allowed to edit, or some other smart tricks..? It would be nice if samba could be an extra layer of defense. Something perhaps a vfs module could help with..?

Am 19.06.24 um 11:35 schrieb Stefan G. Weichinger via samba: > Am 17.06.24 um 16:06 schrieb Rowland Penny via samba: > >>> The user is member of "domain admins", isn't that enough? >> >> No, because they would be classed as 'others'. >> >>> >>> Or does "SYNC_ACL" not yet work OK, because we miss the steps in

Hi, i upgrade to sles sp1 with sernet packages and get the following error after upgrade. Its looks like that port 135 will not reached. Anyone who have an information about that or a solution? Thanks Sven orion:~ # samba-tool drs showrepl Failed to connect host 192.168.24.2 on port 135 - NT_STATUS_CONNECTION_REFUSED Failed to connect host 192.168.24.2 (orion.domain.local) on port 135 -

Hi guys, After having received strong advice from the people in this list to upgrade my kernel to the latest one, I have installed 3.8.0-14-generic #24-Ubuntu SMP x86_64 on several (4) machines. In the hope of improving systems speed I had also removed all snapshots then defragged the FSes - the snapshots have been recreated since, as I use the excellent SuSE "Snapper" tool. But well,