similar to: Hanging SSH in CentOS 7 and Systemd

Hi all, I'm a little bit confused about networking in Centos 7: I've copied my bridge setup from a Centos 6 for KVM networking to Centos 7. I changed the interface name to the new schema and I had expect that it would work. But: The Bridges didn't came up with the following log message: "Error: Device 'br61' is waiting for slaves before proceeding with activation"

Just FYI: I had several problems to install CentOS 7 with 512 MB RAM. No log showed me that problem (I would expect a system check before). With 1 GB RAM everything runs fine. Don't know, what they do with more than 512 MB RAM on a text only system during installation ... Best Regards Oli -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type:

I have multiple VMs that are hanging on boot. Sometimes they'll boot fine after 5 mins and other times it'll take over an hour. The problem seems to be related to journald but I'd like to figure out how I can get more information. The VMs are running CentOS 7.1.1503. systemd and journald are both version 208. We are reluctant to upgrade to the newest CentOS because we found that

Am 14.03.2017 um 15:10 schrieb Nico Kadel-Garcia: > Look into the "autossh" program, which is very good to manage and > maintain such tunnels. > Hi Nico and other ssh users, Systemd restarts the ssh if it terminates. AFAIK this is all that is needed. But maybe I am missing something. Is there a feature of autossh that I don't get with systemd? --

Hi I'm betatesting the new acl features in dovecot 1.2. System: Centos 5.2, dovecot 1.2beta4 built with the spec file from http://dl.atrpms.net/all/dovecot.spec I set up two accounts (sales at domain, oli at domain), I could access them both without problems (testing with Thunderbird) Then I tried to share the sales INBOX as descibed in http://wiki.dovecot.org/SharedMailboxes/Shared: 1

On 6/19/23 20:20, Damien Miller wrote: > > On Fri, 16 Jun 2023, Ronan Pigott wrote: > >> This adds support for systemd socket-based activation in the ssh-agent. >> When using socket activation, the -a flag value must match the socket >> path provided by systemd, as a sanity check. Support for this feature is >> enabled by the --with-systemd configure flag.

On Fri, 16 Jun 2023, Ronan Pigott wrote: > This adds support for systemd socket-based activation in the ssh-agent. > When using socket activation, the -a flag value must match the socket > path provided by systemd, as a sanity check. Support for this feature is > enabled by the --with-systemd configure flag. > > --- > Something tells me upstream would not be interested in

This adds support for systemd socket-based activation in the ssh-agent. When using socket activation, the -a flag value must match the socket path provided by systemd, as a sanity check. Support for this feature is enabled by the --with-systemd configure flag. --- Something tells me upstream would not be interested in this patch, but as it may be useful on linux, I'm submitting it here.

Am 14.03.2017 um 21:43 schrieb Nico Kadel-Garcia: > On Tue, Mar 14, 2017 at 4:20 PM, Thomas G?ttler > <guettliml at thomas-guettler.de> wrote: >> >> >> >> Am 14.03.2017 um 15:10 schrieb Nico Kadel-Garcia: >>> Look into the "autossh" program, which is very good to manage and >>> maintain such tunnels. >>> >> >> Hi

Hi, If I run timemaster from systemd it fails with:- Aug 02 06:07:41 machinename timemaster[19230]: [1494069.352] process 19231 started: /usr/sbin/chronyd -u chrony -n -f /var/run/timemaster/chrony.conf Aug 02 06:07:41 machinename timemaster[19230]: [1494069.352] process 19232 started: /usr/sbin/ptp4l -l 5 -f /var/run/timemaster/ptp4l.0.conf -H -i eno1 Aug 02 06:07:41 machinename

"Oliver Oli" <oliver.oli+0815 at gmail.com> wrote: > Are we sure we know what we are talking about? What is Ogg, what is > Vorbis and what OggPCM? Maybe one of the developers can bring > enlightenment to us :-). As I understood it OggPCM is equivalent to > Vorbis. So it's not Ogg/PCM, but Ogg/OggPCM. Please correct me if I'm > telling utterly crap. Yep,

My icecast server is behind a http proxy server, does anyone know of a program I can use to get icecast to send data to that will forward it to the yp dir? (I'm on linux btw) Oli --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only

Hellos, Yes, I did some tests with "OnFailure" attribute, but the result was the same: system didn't sent any mail. Daemon and script files were: * crond.service: * [Unit] Description=Command Scheduler After=auditd.service systemd-user-sessions.service time-sync.target OnFailure=crond-notify-email.service [Service] EnvironmentFile=/etc/sysconfig/crond

Using the latest snapshot, I'm still getting periodic ssh sessions hanging after they've completed. It used to be very common, but the prior fixes reduced the frequency to about one hung per day (out of thousands). These don't timeout at any point, they'll hang around for days if not killed manually (blocking the scripts from continuing). The commands ssh is hanging on are nothing

On Fri, Oct 19, 2018 at 01:07:46PM +0200, Simon Matter wrote: > That's really an important point, because those who started using Linux > with Linux/systemd will be bound to Linux/systemd with their knowledge, > switching to a *BSD or other Unix will be difficult. For me, I don't like > to be limited in such ways. Having worked with the init systems in a bunch of different

Oliver Stirling wrote: > Oliver Stirling wrote: > >> My icecast server is behind a http proxy server, does anyone know of a >> program I can use to get icecast to send data to that will forward it >> to the yp dir? (I'm on linux btw) >> >> Oli >> >> --- >8 ---- >> List archives: http://www.xiph.org/archives/ >> icecast project

We try to run a reliable ssh tunnel vis systemd. This is the unit configuration file: {{{ [Unit] Description=Tunnel For %i After=network.target [Service] User=autossh ExecStart=/usr/bin/ssh -o "ExitOnForwardFailure yes" -o "ServerAliveInterval 60" -N -R 40443:installserver:40443 -R 8080:installserver:8080 ExecStartPre=-/usr/bin/ssh tunnel@%i "for pid in $$(ps -u

hello spec''ers, i''m in the hunt for guides on testing controllers with rspec, would you guys recommend any? thanks Oliver -- Oliver Azevedo Barnes oli.azevedo.barnes at gmail.com +55 11 9768 0193 http://www.linkedin.com/in/oliverbarnes http://workingwithrails.com/person/4704-oliver-barnes

Gesti? Servidors wrote: > > Hello, > > I'm trying to configure a daemon (I'm doing tests with "crond" daemon) to send me an email after daemon restart. My "crond.service" file is: > # /etc/systemd/system/crond.service > [Unit] > Description=Command Scheduler > After=auditd.service systemd-user-sessions.service time-sync.target >

Hi, it seems there is no difference in "systemctl status crond" :( El 22/11/2019 a las 13:00, centos-request at centos.org<mailto:centos-request at centos.org> escribi?: Message: 3 Date: Thu, 21 Nov 2019 14:41:25 +0100 From: Leon Fauster <leonfauster at googlemail.com><mailto:leonfauster at googlemail.com> To: centos at centos.org<mailto:centos at centos.org>