similar to: TLS between winbind and openldap

On 20/05/2019 18:54, Hendrik Friedel wrote: > Hello, > >> Is btrfs becoming more common ? > In my impression: Yes. Also, this problem seems to affect also zfs and > thus all (?) file systems that support checksums and scrubbing in > linux; consequently all filesystems that are the choice of users who > need this for ensuring data consistency. Not from my experience, but,

Hi Virtualizers, I just setup a CentOS 6 box (at home) to run as a KVM host. It's replacing an absolutely ancient CentOS 5 server that's running Xen. I have one OS drive, and two drives in RAID 1 with LVM on top which is being used as the KVM storage pool. I created a KVM that will run OpenMediaVault (OMV). OMV requires an OS drive (which is really a LVM), and a separate drive(s) to

On Fri, 11 Oct 2024 15:46:23 +0200 "lnj.sam--- via samba" <samba at lists.samba.org> wrote: > Hi, > > We have a NAS server with OpenMediaVault on a Debian system. > > Mainly we work directly with documents from the LibreOffice and > Office tools. > > Sometimes we note at the opening of a LO document that the file is > corrupted and not repairable.

Hi, We have a NAS server with OpenMediaVault on a Debian system. Mainly we work directly with documents from the LibreOffice and Office tools. Sometimes we note at the opening of a LO document that the file is corrupted and not repairable. We know LO documents are a bunch of files embeded in a compressed ZIP archive. The most of time we can repair them in replacing the corrupted elements

On 20/05/2019 19:47, Hendrik Friedel wrote: > Hello, > >>>> You posted this: >>>> I am using Openmediavault (debian based NAS distribution), which is >>>> not actively supporting btrfs >>>> It is this that I was referring to. >>> Ah, yes. >>> OMV intended to move to btrfs as the only choice with the next >>>

Hello, I am try to get my "new" UPS running with NUT on my OpenMediaVault device but only receive error meassages on several configurations I try. Your support is really appreciated for getting it solved. Best Regards, Olaf *lsusb* Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID

Hello, Replaced UPS Kstar Micropower Micro 1200 (managed via blazer_usb) with https://www.njoy.ro/UPS/horus-plus-2000. The latter doesn't seem to be supported. 1. I tried blazer_usb and usbhid-ups. Any other suggestions? 2. What would be needed to get it supported by NUT? ======== HW ======== HP Microserver Gen 8 ======== UPS ======== Working:Kstar Micropower Micro

Hello, No ttyUSB* device under /dev however the new driver has detected the UPS, the nut services are able to start, just "upsc -l ups" sais unknown error and doesn't return any information. Could be due to the driver unable to detect number of battery packs as reported by the nut-driver.service startup? How can I fix that? root at omv:~# systemctl status nut-driver.service●

THIS IS systemctl list-units | grep UPS nut-driver at back-ups.service

> > => many protocols from different clients (Windows 7 and 10 and Debian 9, > 10 and 12) : SMB2_02, SMB2_10, SMB3_11, NT1 A long time ago, we had a problem with oplocks causing system hangs. It COULD be related, and I think we ended up downgrading the kernel to 4.9. https://bugzilla.kernel.org/show_bug.cgi?id=198349#c42 But I've since upgraded to OMV 6+ without any problems.

OS: Openmediavault 7.4.7-1 NUT version: 7.0.4-1 Intalled from OMV plugin installer MY UPS: APC BX1200MI-GR connected through USB all of my UPS data are in this screenshot my problem that i need help with is as follow: so what's happening is if my gaming PC / router / switch are connected and power is down the UPS switches normally without issues from AC to battery and vice versa when the

Thank you Rowland for your help :D We forgot to say the data which are stored in NAS use the filesystem OpenZFS. root at nas:~# modinfo zfs | grep version version:??????? 0.7.13-pve1~bpo1 srcversion:???? 909F99977EB0376A4C4A91C vermagic:?????? 4.15.18-15-pve SMP mod_unload modversions root at nas:~# zdb | egrep "(name|version)" ??? version: 5000 ??? name: 'datastore' ???

On 18/05/2019 14:19, Hendrik Friedel wrote: > Hello > >> No, probably a lack of users using your combination of Samba, btrfs >> and quotas. > I would have thought that btrfs is becoming more mainstream now. And > then, Samba and Quotas should be rather common... >> Is btrfs becoming more common ? > >> Of course, more info may help, what is in your smb.conf

Hello, I had running OpenMediaVault server with NUT 2.4.3 megatec_usb driver. After the OMV upgrade, NUT also upgraded to 2.6.4. I realised that megatec_usb removed in this version. So I have configured to use blazer_usb driver. However NUT behaves incorrectly after switching blazer_usb. System is being halted upon booted up. Is it possible to use megatec_usb driver in the new version? # NUT

This is the first time that i had to use E-mail like forums i'm only hitting reply to mail NOT replay to all mails THIS IS upssched.conf # This file is auto-generated by openmediavault (https://www.openmediavault.org) # WARNING: Do not edit this file, your changes will get lost. CMDSCRIPT /usr/bin/upssched-cmd PIPEFN /run/nut/upssched.pipe LOCKFN /run/nut/upssched.lock AT COMMOK * EXECUTE

Hello, >>>You posted this: >>>I am using Openmediavault (debian based NAS distribution), which is not actively supporting btrfs >>>It is this that I was referring to. >>Ah, yes. >>OMV intended to move to btrfs as the only choice with the next version. In order to pave the way, I intended to be an early adopter. The problem I report here, that there is good

This PowerCOM device (0d9f:0004) is not (or perhaps not yet) supported by usbhid-ups. Please make sure you have an up-to-date version of NUT. If this does not fix the problem, try running the driver with the '-x productid=0004' option. Please report your results to the NUT user's mailing list <nut-upsuser at lists.alioth.debian.org>. No matching HID UPS found Driver failed to

Dear Samba friends, I have setup a samba server 3.5 on FreeBSD 8.1-RELEASE-p2 with openldap-sasl-server-2.4. I have specified ``TLSVerifyClient demand'' in slapd.conf and want to enforce the clients to connect and show a valid certificate to the ldap server. As far as I have understood, Samba will act as a client as well and in order to access the ldap server it will need a client

Hi there, I tried all the driver on the list for this UPS, but they don?t work. Could you help me please? INFO: OMV 2.2.14 (Stone burner) Debian Release 7.11 - Linux nas01 3.2.0-4-amd64 Debian 3.2.93-1 x86_64 GNU/Linux HPE ProLiant Gen8 G1610T 819185-421 4GB RAM MicroServer NUT 2.0 installed from the Plugin Panel of OMV APC Back-UPS 390 Watts / 700 VA, 230V, AVR, IEC Sockets Best regards mikael

On Jun 17, 2013, at 5:32 AM, Yuriy Yurev wrote: > This PowerCOM device (0d9f:0004) is not (or perhaps not yet) supported > by usbhid-ups. Please make sure you have an up-to-date version of NUT. If > this does not fix the problem, try running the driver with the > '-x productid=0004' option. Please report your results to the NUT user's > mailing list <nut-upsuser at