similar to: cron.daily is tossing this strange message about xapian:

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

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

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

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 >

> 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

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.

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

I'd like to announce the availability of the new "itertools" package, which provides a variety of functions used to create iterators, as defined by REvolution Computing's "iterators" package. The package has been uploaded to CRAN and is now available under the GPL-2 license. The "itertools" package is strongly inspired by the Python itertools module, and

I'd like to announce the availability of the new "itertools" package, which provides a variety of functions used to create iterators, as defined by REvolution Computing's "iterators" package. The package has been uploaded to CRAN and is now available under the GPL-2 license. The "itertools" package is strongly inspired by the Python itertools module, and

Verify the returned values of Python Object constructor functions are not NULL before adding them to a collection. This is particularly relevant when constructing Unicode strings in Python 3 as they will return NULL if non UTF-8 characters are present. Signed-off-by: Matteo Cafasso <noxdafox@gmail.com> --- generator/python.ml | 102 ++++++++++++++++++++++++++---------------

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:

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

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

I am having a strange problem. I have been using python + rpy2 on my Mac for quite sometime now. I recently upgraded to OS X 10.8 from 10.6 and that's when the problem began. Now, when I try to load some R packages (like zoo) using robjects.r, python crashes with seg fault 11. Here's an example below: >> import rpy2.robjects as ro >> ro.r(''' library(zoo)

I am having a strange problem. I have been using python + rpy2 on my Mac for quite sometime now. I recently upgraded to OS X 10.8 from 10.6 and that's when the problem began. Now, when I try to load some R packages (like zoo) using robjects.r, python crashes with seg fault 11. Here's an example below: >> import rpy2.robjects as ro >> ro.r(''' library(zoo)

[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

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

I have a project that requires Xapian for a 32 bit arch, but Mac defaults to 64 bit. How can I configure Xapian core and Xapian python bindings to build 32 bit?