similar to: pymouth and sysvinit

I have experienced a couple of power failures since installing CentOS 5, both while I was working on the system. The first time, several weeks ago, I thought there was some "feature" that I had never seen before but couldn't really put my finger on it. The power came back on after a few seconds and I never missed a beat. I also shrewdly forgot about the anomaly that I had

CentOS Errata and Bugfix Advisory 2013:1003 Upstream details at : https://rhn.redhat.com/errata/RHBA-2013-1003.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 8b79e3d6537dcdd1e5a3fd7f10499e8b41fad608ece91d828fa5759b192cdc96 sysvinit-tools-2.87-5.dsf.el6.i686.rpm x86_64:

CentOS Errata and Bugfix Advisory 2011:1040 Upstream details at : https://rhn.redhat.com/errata/RHBA-2011-1040.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: cabfe96f060487630e923a3f8a99df2b SysVinit-2.86-17.el5.i386.rpm Source: 5d906d56849fc60bc90d8b432bc29558 SysVinit-2.86-17.el5.src.rpm -- Karanbir Singh CentOS

CentOS Errata and Bugfix Advisory 2011:1040 Upstream details at : https://rhn.redhat.com/errata/RHBA-2011-1040.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: 15944c16e391ca48d2817834ace2d1fe SysVinit-2.86-17.el5.x86_64.rpm Source: 5d906d56849fc60bc90d8b432bc29558 SysVinit-2.86-17.el5.src.rpm -- Karanbir Singh

Hallo I thought that I need to use `--delete' option for that, but it looks like not. Problem explanation: prompt# ls /tmp/dir1/ /tmp/dir2/ /tmp/dir1/: fil1.txt /tmp/dir2/: fil1.txt fil2.txt prompt# rsync --delete /tmp/dir1/* /tmp/dir2/ prompt# ls /tmp/dir1/ /tmp/dir2/ /tmp/dir1/: fil1.txt /tmp/dir2/: fil1.txt fil2.txt # fil2.txt still exists My question is,

hi below is sysvinit script for handling tcng-script .... please excuse my bad bash skils, correct me where i''m doing stupid things :") what is left... many things, if i have time i will implement them too : - start [devices] - and then correct handling of service lock files i.e. per device lock file - stats blah ... - all ideas are welcome !! - test or some such, i mean the

To avoid possibly invoking similarly named executables, all start, stop and reload methods in the sysvinit scripts have been renamed to start_/stop_/reload_[script name]. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- scripts/ovirt | 17 +++++++++++------ scripts/ovirt-awake | 20 +++++++++++++++++++- scripts/ovirt-early | 16 ++++++++++------

Hi, I recently configured dovecot to manage auth for both local and virtual user. When i login as a virtual user (claudio.panetta) I get the following message: dovecot: auth: Error: passwd(claudio.panetta,160.97.62.1,<WLjlnZ9oRACgYT4B>): getpwnam() failed: Illegal seek but login is ok and sending/receiving email is ok, how can, if possible, I suppress this error message? In the

http://bugzilla.mindrot.org/show_bug.cgi?id=173 Summary: sshd does not listen on tcp-socket, though GatewayPorts yes Product: Portable OpenSSH Version: 3.1p1 Platform: UltraSparc OS/Version: SunOS Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo:

> On 30 March 2018 at 15:11 panetta <panetta at mat.unical.it> wrote: > > > Hi, > > I recently configured dovecot to manage auth > for both local and virtual user. > When i login as a virtual user (claudio.panetta) I get the following > message: > > dovecot: auth: Error: > passwd(claudio.panetta,160.97.62.1,<WLjlnZ9oRACgYT4B>): getpwnam() >

Hello there and SFME. Since el6 subversion package doesn't contain traditional SysV demonization script anymore I wonder how it is supposed to run svnserve from now on. 1) Should one write init script to be managed with service(8) on his own? 2) Or launch svnserve on demand via (x)inetd? 3) Or put svnserve command line in some rc-script? 4) Or maybe is ra_svn deployment scheme not supported

Greetings, I've been trying to get LightDM working on FreeBSD, as there is no package for it yet. I've managed to get it compiled from source, but it fails to start. It displays the message, "Failed to get D-Bus connection". D-Bus is running, and LightDM starts the X server fine. Is there anything I need to do to get it to talk to dbus? Right now I have LightDM installed in my

CentOS Errata and Bugfix Advisory 2014:1030 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-1030.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 7568b606796a506f71743a9ecfcf173289d3c585b05ebbeda42226068fd23794 plymouth-0.8.3-27.el6.centos.1.i686.rpm

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

On Tue, Jun 20, 2017 at 7:32 PM, Ludwig Gamache <ludwig at elementai.com> wrote: > All, > > Over the week-end, one of my volume became unavailable. All clients could > not access their mount points. On some of the clients, I had user processes > that we using these mount points. So, I could not do a umount/mount without > killing these processes. > > I also noticed

Sharding is not enabled. Ludwig On Mon, Sep 25, 2017 at 2:34 PM, <lemonnierk at ulrar.net> wrote: > Do you have sharding enabled ? If yes, don't do it. > If no I'll let someone who knows better answer you :) > > On Mon, Sep 25, 2017 at 02:27:13PM -0400, Ludwig Gamache wrote: > > All, > > > > We currently have a Gluster installation which is made of 2

Update me Richie, Meanwhile, I've booted the server in latest kernel, Its still not working for me. 2015-03-17 0:54 GMT+05:30 Thirumalai Nambi <thirumalai.sandy@gmail.com>: > > libtool-2.2.6-15.5.el6.x86_64 > upstart-0.6.5-13.el6_5.3.x86_64 > atmel-firmware-1.3-7.el6.noarch > redhat-rpm-config-9.0.3-42.el6.centos.noarch > plymouth-scripts-0.8.3-27.el6.centos.1.x86_64

Hi, I?m running a special initrd generated for SystemImager with a special dracut module that relies on plyouth scripted theme. It works perfectly on CentOS-6, CentOS-7, OpenSUSE-42.3, Fedora-29 (not tested later) and used to work on CentOS-8.0 Since CentOS-8.1 was released, IT chrashes with the following error: Plymouthd crash 913: ply_event_loop_watch_for_timeout: Assertion `seconds >

I'm trying to set-up a ContOS 7 DomU server. I have used the PXE set-up images like I normally would for earlier versions of CentOS. Here is my config file:- name      = "centos7" memory    = 2048 disk      = ['phy:/dev/xen6/centos7,xvda,w' ] vif = [ 'mac=xx:xx:xx:xx:xx:xx' ] kernel    = "/root/xen/centos7-64/vmlinuz" ramdisk   =

Can you please explain How we ended up in this scenario. I think that will help to understand more about this scenarios and why gluster recommend replica 3 or arbiter volume. Regards Rafi KC On 06/15/2017 10:46 AM, Karthik Subrahmanya wrote: > Hi Ludwig, > > There is no way to resolve gfid split-brains with type mismatch. You > have to do it manually by following the steps in [1].