search for: shutils

Hello, After upgrading to Samba 4.11 (from 4.10) I noticed that python scripts using tempfile.mkstemp fail when run against samba cifs mounts. Before I submit a bug report, could someone else try this out so it's not just my setup? How to reproduce: 1. Mount a Samba 4.11 share using the mount command: mount //server1/share /tmp/share1 2. Run python script that is using mkstemp: import

Can you please post your smb.conf? On Sat, Sep 21, 2019 at 12:45 PM Kacper via samba <samba at lists.samba.org> wrote: > Hello, > > After upgrading to Samba 4.11 (from 4.10) I noticed that python > scripts using tempfile.mkstemp fail when run against samba cifs > mounts. Before I submit a bug report, could someone else try this out > so it's not just my setup? >

On 21/09/2019 17:43, Kacper via samba wrote: > Hello, > > After upgrading to Samba 4.11 (from 4.10) I noticed that python > scripts using tempfile.mkstemp fail when run against samba cifs > mounts. Before I submit a bug report, could someone else try this out > so it's not just my setup? > > How to reproduce: > 1. Mount a Samba 4.11 share using the mount command:

This enables the ability to take the ovirt-node-image iso and deploy it to an iscsi disk. It also provides a sample pxe configuration for booting based on the iscsi root device. Includes support for user/password as well as reverse chap user/password. --- Makefile.am | 1 + livecd-iso-to-iscsi | 201 ++++++++++++++++++++++++++++++++++++++++++++++ ovirt-node-image.spec.in |

Full output: root at iob-master:~# samba-tool domain backup online --server=dc01 --targetdir=/autofs/backup/linux/samba_dom/$(hostname -d) -U administrator Password for [SAMBA\administrator]: INFO 2023-11-20 15:30:05,639 pid:73781 /usr/lib/python3/dist-packages/samba/join.py #1614: workgroup is SAMBA INFO 2023-11-20 15:30:05,640 pid:73781 /usr/lib/python3/dist-packages/samba/join.py #1617: realm

Hello everybody, i tried "samba-tool domain backup online --server=dc01 --targetdir=/autofs/backup/linux/samba_dom/backup.tgz -U administrator" and got this error: ERROR(<class 'OSError'>): uncaught exception - [Errno 39] Directory not empty: 'sam.ldb.d' File "/usr/lib/python3/dist-packages/samba/netcmd/__init__.py", line 185, in _run

Hey, dir exisit.... root at dc01:/autofs/backup# ls -la /autofs/backup/linux/samba_dom/backup.tgz/ insgesamt 12484 drwxr-xr-x 4 root root 4096 20. Nov 14:02 . drwxr-xr-x 3 root root 4096 20. Nov 14:00 .. -rw-r--r-- 1 root root 12765535 20. Nov 14:03 samba-backup-samba.laurenz.ws-2023-11-20T14-02-51.306281.tar.bz2 drwx------ 2 root root 4096 20. Nov 14:00 tmpdz6serc_ drwx------ 7 root

Hi ! I have a python script that create and move .call files to /var/spool/asterisk/outgoing Sometimes...(in this case after 500 successfull calls) Asterisk don?t make the calls and the .call files are in the "outgoing" forever... Any Ideas? I'm using Asterisk 1.4.22 (in 1.4.36 was the same behavior) In my python script I move .call files using ... import shutil

[global] workgroup = example realm = example.test netbios name = server1 server role = active directory domain controller log file = /var/log/samba/smbd.log server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbindd, ntp_signd, kcc, dnsupdate domain logons = Yes wins support = Yes security = user preferred master = auto domain master = yes local master = yes unix extensions = no

On Mon, 20 Nov 2023 15:34:19 +0100 Dirk Laurenz via samba <samba at lists.samba.org> wrote: > Full output: > > root at iob-master:~# samba-tool domain backup online --server=dc01 > --targetdir=/autofs/backup/linux/samba_dom/$(hostname -d) -U > administrator Password for [SAMBA\administrator]: > INFO 2023-11-20 15:30:05,639 pid:73781 >

I see many tests that are prefixed with "requires: shell". A quick search over the codebase shows 101 tests that contain this directive. This basically means there are 101 tests that say "I don't support running on Windows". I would like to get this number to 0. Ironically, many of these tests can be made to run on Windows simply by removing the requires: shell line.

Hello List, now i try to use the backup command for the first time and it fails: It claims sam.ldb.d is not empty but there should be all domain db's right? Samba Version: root at dc01:/var/lib/samba/private/sam.ldb.d# <mailto:root at dc01:/var/lib/samba/private/sam.ldb.d#> samba -V Version 4.11.8-Debian root at dc01:/backup/linux/samba-dom# samba-tool domain backup

> several people already asked what are the concrete benefits of breaking support for end-of-life python versions? Generally I think the only compelling argument is "for a given level of maintenance effort, you either sacrifice support for old-dead versions, or new versions", and obviously new versions should be preferred. The question is how much does it cost to interoperate. On

Hi, here are the versions: dc01: Raspberry Pi 3 Model B Rev 1.2 root at dc01:~# cat /etc/debian_version 11.8 root at dc01:~# samba -V Version 4.17.12-Debian root at dc01:~# uname -a Linux dc01 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux Dc02: Raspberry Pi 3 Model B Rev 1.2 root at dc02:~# cat /etc/debian_version 11.8 root at dc02:~# samba -V Version

Hello List, offline fails also.. root at dc01:~# samba-tool domain backup offline --targetdir=/backup/linux/samba-dom-dc01-offline Creating targetdir /backup/linux/samba-dom-dc01-offline... running backup on dirs: /var/lib/samba/private /var/lib/samba /etc/samba Starting transaction on /var/lib/samba/private/secrets Starting transaction on /var/lib/samba/private/sam.ldb backing up

On 12/04/2012 12:28 AM, Sean Silva wrote: > On Mon, Dec 3, 2012 at 6:56 AM, Tobias Grosser<tobias at grosser.es> wrote: >> The gcc compile farm currently only has python 2.4 and 2.5. I know Duncan is >> using it quiet extensively, especially all dragonegg buildbots run on it. >> >> I very much agree we should ensure our python scripts are valid python 2.7 >>

On Tue, Dec 4, 2012, at 03:23 AM, Sean Silva wrote: > > several people already asked what are the concrete benefits of breaking support for end-of-life python versions? > > Generally I think the only compelling argument is "for a given level > of maintenance effort, you either sacrifice support for old-dead > versions, or new versions", and obviously new versions

Signed-off-by: Matteo Cafasso <noxdafox@gmail.com> --- python/t/test830RHBZ1406906.py | 55 ++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 55 insertions(+) create mode 100644 python/t/test830RHBZ1406906.py diff --git a/python/t/test830RHBZ1406906.py b/python/t/test830RHBZ1406906.py new file mode 100644 index 000000000..62caf8ce1 --- /dev/null +++

/etc/cron.daily/apt: Traceback (most recent call last): File "/usr/sbin/update-apt-xapian-index", line 581, in <module> import os.path, re, imp, glob, xapian, textwrap, shutil, fcntl, errno, itertools, time File "/usr/lib/python2.6/dist-packages/xapian.py", line 6, in <module> import _xapian ImportError: /usr/lib/python2.6/dist-packages/_xapian.so:

--- scripts/install.py | 247 ++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 247 insertions(+), 0 deletions(-) create mode 100755 scripts/install.py diff --git a/scripts/install.py b/scripts/install.py new file mode 100755 index 0000000..ddffb53 --- /dev/null +++ b/scripts/install.py @@ -0,0 +1,247 @@ +#!/usr/bin/python +# +# install.py - configure local boot/root disk