similar to: HELP -- upgrade to 1.9.18p8 causing print/disk trouble ...

Hello Jim, I've installed samba-1.9.18p8 some months ago. Everything worked find till yesterday. My PCs went in a similar problem as yours. If I want to connect to a Networkprinter (my samba is the printserver for the PC) it takes a verly long time (10 Minutes) till I get any response from my printer. If I want to print it takes a very long time too to get the dialog with the right printer.

Hi guys i need some help to build choropleth. Basically i am trying to colour regions on the map by population. I possess the shape file of the country, and also the population data, however, i am having trouble to create the plot, below is my code: population=read.csv("nz2.csv") population names(population) nz=readShapeSpatial((sprintf('nz-geodetic-marks',tmp_dir)))

I have a problem with new version (1.9.18p8) of SAMBA and username mapping. Configuration: WindowsNT 4.0 Workstation + SP1 WindowsNT domain - NTEP01 is PDC Digital UNIX 3.2C Username on NT: Babor Username on UNIX: baborl In SMB.CONF I have following lines: [global] security = server password server = NTEP01 username map = /usr/local/samba/lib/username.map username.map: baborl = babor

The Samba-Team is pleased to make known that binary packages for samba-1.9.18p8 are now available for: Red Hat Linux 4.2, 5.0 and 5.1 (Intel) Red Hat Linux 5.1 (alpha) Caldera Open Linux 1.2 (Intel) Sun Solaris x86 2.6 SCO Open Server 5.04 Slackware Linux 3.4 Digital Alpha Unix 4.0d (OSF1) We are hoping that others will contribute binary files for the remaining major platforms will be available

I've recently installed Version 1.9.18p8 on a V2.6 Solaris x86 box. This system has an 8GB disk that I'm sharing out using Samba. After I map this share to a drive letter on my V4 NTWS, the properties for this drive reports that it is only 4GB. Is this a known "bug"? Other than the bogus information, will it have any adverse affects after the disk fills up to exceed 4GB used?

Ronny Blomme <Ronny.Blomme@elis.rug.ac.be> writes: > The default configuration for smbclient in samba-1.9.18p8 is to send > verbose output to stdout. The output sent to tape is a mix of this > verbose output and the tar-file => corrupt tar file on tape The attached patch for SAMBA fixes this problem, preventing log messages from being printed to stdout if the tar-file is

Hi all, I'm extremely puzzled by the behaviour of one of my Samba servers. It's been working fine for yonks, and this morning (abuout 11:32) it just stopped. (mostly) Connecting to shares still works. Navigating the tree till works. Changing (DOS) attributes still works. But actually opening files and reading the contents doesn't work. The client just times out (Win 3.11, and

I'm running Samba 1.9.18p8 on a RedHat5.1 system. Shares are going cleanly, but domain logons are not. I have an NT box, but as it is for a dedicated app, not for servers, I simply shut it down while testing samba's PDC functionality. I'll turn PDC off on the NT box as soon as I get samba doing domain controlling. I recently posted this problem with subject line: Samba 1.9.18p7-2

Since we're no longer only inspecting LUKS devices, use a more generic name. This rewrite also makes the function clearer. --- options/decrypt.c | 34 +++++++++++++++------------------- 1 file changed, 15 insertions(+), 19 deletions(-) diff --git a/options/decrypt.c b/options/decrypt.c index d868f70..58f8df9 100644 --- a/options/decrypt.c +++ b/options/decrypt.c @@ -28,6 +28,7 @@ #include

Hello Samba Gurus, I am running FreeBSD 2.2.6-STABLE and Samba 1.9.18p8. I am unsucessful in logging into the server (from Windows or UNIX using smbclient). I turned the logging to level 10. Here is my info: When I start samba 1.9.18p8: su-2.01# more /var/log/samba.log lp_file_list_changed() file /usr/local/samba/lib/smb.conf -> /usr/local/samba/lib/smb.conf last mod_time: Mon Jun 29

The following patch attempts to implement sparsification of LUKS-encrypted partitions. It uses lsblk to pair the underlying LUKS block device with its mapped name. Also, --allow-discards was added by default to luks_open(). There are several potential issues that I can think of: 1) If and entire device is encrypted (not just one of more partitions), the lsblk trick might not work. 2) The

For links to the original patch series, see: https://bugzilla.redhat.com/show_bug.cgi?id=1808977#c8 The original feedback was that ignoring errors from guestfs_luks_uuid would ignore legitimate errors from non-BitLocker disks, so I have modified this series so that errors are only ignored in the BitLocker case. As noted in the 4th patch there is no actual error in the BitLocker case, cryptsetup

Support transparent decryption/inspection of Windows guests encrypted with BitLocker encryption. This won't make much sense without the associated libguestfs patches which I will post momentarily. (Submodules, ho hum) Rich.

Original version linked from here: https://bugzilla.redhat.com/show_bug.cgi?id=1808977#c8 There is no change in the code in this series, but feedback from the original series was we shouldn't lose the error message in patch 7. When I tested this just now in fact we don't lose the error if debugging is enabled, but I have updated the commit message to note what the error message is in the

These commits, along with the associated changes to common: https://www.redhat.com/archives/libguestfs/2020-March/msg00286.html support the transparent decryption and inspection of Windows guests encrypted with BitLocker encryption. To do the BitLocker decryption requires cryptsetup 2.3.0 (although cryptsetup 2.3 is not required for existing LUKS use). It also requires a new-ish Linux kernel, I

On Mon, Sep 07, 2020 at 10:41:20AM +0100, Richard W.M. Jones wrote: >For BitLocker disks cryptsetup does not (yet? ever?) support reading >UUIDs and this function will fail. This does not matter here so just >ignore the error. > >Note there is no error message, cryptsetup simply returns with a bad >exit code: > >><rescue> cryptsetup luksUUID /dev/sda2

--- mltools/tools_utils-c.c | 8 ++++---- mltools/tools_utils.ml | 6 +++--- mltools/tools_utils.mli | 8 ++++++-- options/decrypt.c | 5 +++-- options/inspect.c | 2 +- options/options.h | 2 +- 6 files changed, 18 insertions(+), 13 deletions(-) diff --git a/mltools/tools_utils-c.c b/mltools/tools_utils-c.c index 6c43b8d..1dcebc4 100644 --- a/mltools/tools_utils-c.c +++

As discussed in the emails today, this is the third version addressing most points from the v1/v2 review. You will need to pair this with the changes in libguestfs-common from this series: https://www.redhat.com/archives/libguestfs/2020-September/msg00050.html Rich.

Hello, in my log.nmb I regularly see these messages: process_local_master_announce: Server GUTENBERG at IP 192.168.35.90 is announcing itself as a local master browser for workgroup PIEZO and we think we are master. Forcing election. 1998/08/10 12:57:03 ***** Samba name server FAURE has stopped being a local master browser for workgroup PIEZO on subnet 192.168.32.1 ***** 1998/08/10

Hi, this series refactors some guestfish code (not much), and exposes it via Common_utils, so it is possible to decrypt LUKS partitions when using virt-customize, virt-get-kernel, virt-sparsify, and virt-sysprep. This brings them closer in features with C tools. Most probably a couple more of other OCaml-based tools (virt-v2v to convert encrypted guests, and virt-builder to use encrypted