search for: procedere

...r inside a firewall and go through the firewall wia a ssh-plug-gateway to one host in our internet section and further do a second server in the internet section. All this including the ssh-agent mechanism. The command is like: hendl at server > ssh -t host_a ssh -t firewall ssh -t host_b This procedere works fine, but on the host firewall I am disabled after an couple of conncetions because of too many unseccesful logins. Unfortunately the lastb command says nothing and in fact I didn't login to that machine, I used it only as an gateway. The syslog.log tells: sshd [xxx] Accepted rsa for hen...

...momento potrete richiederci la sospensione da parte nostra dell'impiego dei vostri dati, ad esclusione delle comunicazioni effettuate in esecuzione di obblighi di legge. Qualora riceveste questo messaggio senza esserne il destinatario Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema ------------------------------------------------------------------------ This e-mail (including attachments) is intended only for the recipient(s) named above. It may contain confidential or privileged information and should no...

...sono da considerarsi strettamente riservate. Il loro utilizzo ? consentito esclusivamente al destinatario del messaggio, per le finalit? indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalit? diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003. ****...

...ile/s allegato/i, sono da considerarsi strettamente riservate. Il loro utilizzo ? consentito esclusivamente al destinatario del messaggio, per le finalit? indicate nel messaggio stesso. Qualora riceveste questo messaggio senza esserne il destinatario, Vi preghiamo di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Costituisce comportamento contrario ai principi dettati dalla Legge il trattenere il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo od utilizzarlo per finalit? diverse.

...'m subscribed to llvm-commits yes (in digest mode if that should make a difference), but the message was not submitted to the list (it seems to be still in the queue waiting for moderator approval). Anyhow, I will submit my little patch via Phabricator then and refer to the Phabricator docs for procedere and finding reviewers. Thanks! BR, Chris > From: llvm-dev <llvm-dev-bounces at lists.llvm.org <mailto:llvm-dev-bounces at lists.llvm.org>> on behalf of Christoph Kindl via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> > Reply-To: Christoph...

...momento potrete richiederci la sospensione da parte nostra dell'impiego dei vostri dati, ad esclusione delle comunicazioni effettuate in esecuzione di obblighi di legge. Qualora riceveste questo messaggio senza esserne il destinatario Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema ------------------------------------------------------------------------ This e-mail (including attachments) is intended only for the recipient(s) named above. It may contain confidential or privileged information and should no...

[please keep the list CC'd. Thanks!] On Wed, Aug 13, 2014 at 9:33 AM, Marcello Vezzelli <mv at 3cx.com> wrote: > I noticed that 2 of Sweex UPS have an identical serial number 20100813, > which looks like a date. > The other one has an empty serial number. > > The blew one had the serial number, so I'm left with two different UPSes > from the serial number point of

On Thu, Aug 14, 2014 at 3:55 AM, Marcello Vezzelli <m.vezzelli at e-works.it> wrote: > I've found another strange issue that prevented me to test this solution. > VMware ESXi is filtering out serial number information, together with > iManufacturer and iProduct. Is it a permissions issue? The NUT udev configuration file changes the ownership and permissions to allow the NUT

Yup, Phabricator is generally preferred for patches. Additionally, are you subscribed to the mailing list? I can't find where I read it now, but I believe your messages are held for moderation if you aren't subscribed. You can subscribe at http://lists.llvm.org/mailman/listinfo/llvm-commits if needed. From: llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of Christoph Kindl

..., si informa che ogni disseminazione, distribuzione o copiatura di questa comunicazione ? strettamente proibita anche ai sensi del decreto legislativo 196/03. Se avete ricevuto questo messaggio per errore, vi preghiamo di notificarcelo immediatamente a mezzo e-mail di risposta e successivamente di procedere alla cancellazione di questa e-mail e relativi allegati dal vostro sistema. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20130621/8f33b0f9/attachment-0001.html> -------------- next part --...

Hi everyone, I installed latest version of Nut on Debian Wheezy 64bit. This is a virtual server hosted by VMware ESXi. It's a Nagios monitoring server. I configured one Sweex UPS in ups.conf and everything is working. ups.conf: [sweex1] driver = blazer_usb port = auto runtimecal = 1100,100,2200,50 Now I want to connect two more identical UPSes to the same server, total of 3

Hi, I've recently submitted a patch to llvm-commits (as requested by https://llvm.org/docs/DeveloperPolicy.html#making-and-submitting-a-patch) and the mailing list answered with a notice that my message is held for moderator approval (with the reason: "Post by non-member to a members-only list"). I'm therefore wondering if I should've submitted my patch via Phabricator

Hi, I am trying to implement something like an "LXC on CentOS 7 HowTo" for internal use. (Might as well get public afterwards.) I am following the HowTo for CentOS 6 (https://wiki.centos.org/HowTos/LXC-on-CentOS6). So, here's what I did so far (Steps 1-6 can easily be omitted, but I am trying to be complete.) 1.) Disable delta RPM's in /etc/yum.conf 2.) Remove LibreOffice

...'m subscribed to llvm-commits yes (in digest mode if that should make a difference), but the message was not submitted to the list (it seems to be still in the queue waiting for moderator approval). Anyhow, I will submit my little patch via Phabricator then and refer to the Phabricator docs for procedere and finding reviewers. Thanks! > > BR, > Chris > >> From: llvm-dev <llvm-dev-bounces at lists.llvm.org <mailto:llvm-dev-bounces at lists.llvm.org>> on behalf of Christoph Kindl via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>>...