search for: matchine

Hi, is it possible to have several ocfs2 clusters in the same machine? We have webserver1 and webserver2 that should belong to cluster1 and cluster2 "workgroup". Cluster1 should be made of webserver1, webserver2 and application_server1 Cluster2 should be made of webserver1, webserver2 and application_server2 Is this possible? Thanks, Nuno Fernandes

Hi all. I'm under Ubuntu 7.10 server I use a SALICRU UPS Advance I install nut and nut-usb, write some config files, but i cannot connect to UPS. At ups.conf i wrote: [salicru] driver = newhidups port = auto desc = "Desc" But if try to make "sudo upsdrvctl start" it said: No matchin HID UPS found If i write "lsusb" appears: Bus 001: Device 007: Id

Hi list Does anyone has experience in setting up dovecot or any other mail system with user auth against a Samba4 AD ? If yes could I get some advice on that Topic or even a link to a ressource where I can get some Information. Googled a lot but didn't find something yet. Thankx in advance. -- Mit freundlichem Gru? Carsten Laun-De Lellis Hauptstrasse 13 D-67705 Trippstadt Phone: +49

Hello, when deploying drivers via Point-and-Print recent Windows (tested with Windows 10 1607) asks the user to confirm the driver installation. An appropriate Policy [1] is set up so that no user interaction should be required for the driver installation. There are similar reports [2,3] that identify updates KB3163912, KB3172985 and KB3170455 causing these issues. However, Windows 10 1607

I'm trying to clarify contexts and their uses. I do have a good general understanding of them. My question is about "undeclared" and "non-existant" contexts. If I have a block somewhere (in sip.conf, for example), and it has no "context=thiscontext" field, does it just automatically use the "default" context? Or is this settable? (I see there is an

My keys are secured with a passphrase. That's good for security, but having to type the passphrase either at every login or at every invocation of ssh(1) is annoying. I know I could invoke ssh-add(1) just before invoking ssh(1), if I keep track of whether I invoked it already, or write some hacky scripts; but the rest of OpenSSH is wonderfully usable without any hacks. Hence, this patch.