similar to: Starting service as non root user with puppet

Hello! Try to use libvirt with lxc. I use latest centos6 amd64 as a libvirt host (libvirt from xen4 repo) libvirt-daemon-1.2.15-3.el6.x86_64 In container I also use latest centos6 amd64. Container starts with /sbin/init. CentOS 6 came with upstart as default init. My problem is that I could not shutdown container correctly with libvirt. virsh -c lxc:/// shutdown test Domain test is being

Puppet 2.7.17 is a maintenance release for Puppet in the 2.7.x series. It contains a fix for the ubuntu service regression in 2.7.16 (#15027, #15028, #15029). Downloads are available at: * Source https://downloads.puppetlabs.com/puppet/puppet-2.7.17.tar.gz Windows package is available at https://downloads.puppetlabs.com/windows/puppet-2.7.17.msi RPMs are available at

I'm moving some server configurations from Ubuntu Server 12.04 to CentOS 6.6. Now I'm working on `/etc/init` script that should be handled by `upstart` at both OS as far as I know. The files on both server are the same and I mean the same at content level and also at path level and permissions level, is the exactly copy from Ubuntu to CentOS. I'm having some issues with upstart at

Hi, I just upgraded in Ubuntu from the ubuntu-package samba 4.1.6 do a self-compiled version 4.1.12. If anybody else happens to have the same task (pdc, not ad), this is how it worked: # do all following as root sudo su - # remove ubuntu samba 4.1.6 aptitude remove samba # install samba 4.1.12 from source aptitude install build-essential libacl1-dev libattr1-dev \ libblkid-dev

Hi everyone, I''m trying to start up domU on xen for ARM (Cortex-A15 Fast models). I follow the instructions to build xen-tools with this link: http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/CrossCompiling. But there seems to be something wrong when I start up domU. First, I get errors in create domU with xl: root@(none):/home/xiaogw# xl create domU-config xc: error:

On 2015-04-04, Bill Maltby (C4B) <centos4bill at gmail.com> wrote: > On Sat, 2015-04-04 at 11:12 +0100, Nux! wrote: >> 100% with Digimer here. <snip> > >> All this energy should be put into contributing towards to the >> project, testing, helping out community. > > Well, I used to agree. But when a bug report filed in December goes > untouched entering

On Fri, Nov 20, 2015 at 04:19:59PM +0300, Boris Savelev wrote: > Hello! > > Try to use libvirt with lxc. > I use latest centos6 amd64 as a libvirt host (libvirt from xen4 repo) > libvirt-daemon-1.2.15-3.el6.x86_64 > In container I also use latest centos6 amd64. Container starts with > /sbin/init. CentOS 6 came with upstart as default init. > > My problem is that I

Postfix on CentOS-6.2 evidently does not use upstart style configurations. The author evidently has no plans on altering Postfix's structure to accommodate upstart any time soon, if ever (http://tech.groups.yahoo.com/group/postfix-users/message/274670). Thus Postfix starts and stops using a sysvinit style script. Nonetheless, I have an upstart configuration that I wish to be dependent upon

On Wed, Apr 08, 2015 at 10:36:05AM +0000, Liam O'Toole wrote: > Thanks for drawing my attention to that bug. I encountered it the other > day after switching from runlevel 5 to 3 (and back again) on a CentOS > 6.6 machine. > > The purpose of the runlevel switch was to restart gdm. Is there a better > way? Since CentOS 6 uses Upstart as its init system, and GDM is run from

On 2015-04-08, Leon Fauster <leonfauster at googlemail.com> wrote: > Am 08.04.2015 um 16:22 schrieb Liam O'Toole > <liam.p.otoole at gmail.com>: >> On 2015-04-08, David Both >> <dboth at millennium-technology.com> >> wrote: >>> The easy way to restart gdm is when you are on the login screen >>> itself or the desktop simply press

On Tue, Nov 26, 2013 at 01:06:58PM +0100, Gonzalo Aguilar Delgado wrote: > Starting /init script ... > initctl: Unable to connect to Upstart: Failed to connect to socket > /com/ubuntu/upstart: Connection refused > /etc/init.d/udev: 290: /etc/init.d/udev: > /lib/udev/create_static_nodes: not found > * Starting the hotplug events dispatcher udevd > ...done. >

I cannot find any good example of a unicorn upstart task that works properly for the following: * Upstart will restart if unicorn dies * Can send USR2 signal to unicorn to do a no downtime deploys * Able to stop upstart job, even after a deploy I have tried the following: expect fork respawn setuid www-data chdir /var/www/app/current exec bundle exec unicorn_rails -E production -c

hi there, first, kudos to Scott. You guy rock with this revolutionizing (and so logic) idea ;-) next, a personal point of view about the lack of upstream adoption of upstart: I wanted to provide an upstart script for NUT for some time, but never found enough matching example to do so. the embedded scripts only address inittab, and the replacement-initscripts are unreachable (see below) and far

Hi all, I need some help by solving a strange problem: Situation: I wrote a scrip that uses rsync to send backups to another server. It does something like: /usr/bin/rsync -azi --numeric-ids --exclude tmp --exclude var/spool/ --delete -e ssh root at 10.0.0.65:/ /storage/volumes/65 The script has a source file that dictates which servers to backup. E.g. several ip address are visited to

Here is my output: Console: colour dummy device 80x25 console [tty0] console [hvc0] installing Xen timer for CPU 0 Detected 1806.840 MHz processor Calibrating delay loop (skipped), value calculated using timer frequency.. 3613.68 BogoMIPS (lpj=7227360) Mount-cache hash table entries: 256 CPU: L1 I Cache: 64K (64 bytes/line) Apic siabled by BIOS Grant table initialized NET: Registering protocol

?Hi, I was wondering if anyone has managed to get the preload_app and SIGUSR2 combination working well with upstart? My issue currently is that when I perform a SIGUSR2 against the master, check everything''s working and close off the old master, upstart then attempts to restart it because the original PID/binary are no longer running. What is the correct way of handling this? In my

Guys, I have a source code here, that produces RPM packages for CentOS 6, that includes an Upstart Job and a ugly and minimal Init Script. Now, I have it running on CentOS 7, via systemd, looks good! However, my RPM package for CentOS 7 still includes the useless Upstart and Init Scripts... So, here is the question: How are you guys managing this? I mean, I would like to have 1 single

Hi all, Trying to test libvirt 1.1.3 with virtlockd locking my qcow2 images on a NFS storage between two kvm hosts. ./configure ... --with-init-script=upstart Libvirtd upstart script is actually well generated but I can't see nothing about virtlockd... or am I blind ? :) Nevertheless, running virtlockd -d && service libvirtd restart works fine. Am I wrong thinking that editing

OK, not exactly a samba issue but maybe the Ubuntu maintainer reads this list and can provide some input. Problem: Ubuntu doesn't daemonize smbd. System: Ubuntu Lucid where a recent update moved many startup scripts into the "upstart" system. Now smbd is started and runs as "smbd -F". If I edit the upstart script (/etc/init/smbd.conf) so that it runs as "smbd

Hi Eric, Here is my try to write a quick upstart script for virtlockd. It should be named /etc/init/virtlockd.conf, then : ln -s /lib/init/upstart-job /etc/init.d/virtlockd It seems to work for me : # virtlockd - Locking daemon for libvirt description "virtlockd" start on filesystem and runlevel [2345] stop on starting rc RUNLEVEL=[016] pre-start script test -x