-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/20/2012 09:53 AM, Daniel P. Berrange wrote:
> On Tue, Nov 20, 2012 at 09:50:39AM -0500, Daniel J Walsh wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>
>> On 11/20/2012 09:36 AM, Daniel P. Berrange wrote:
>>> On Tue, Nov 20, 2012 at 08
On Tue, 20.11.12 08:52, Daniel J Walsh (dwa...@redhat.com) wrote:
> > Hmm, there is currently no option for that.
> >
> > A semi-dirty trick might be to over-bind-mount /etc/rc.d with something
> > empty?
> >
> > Lennart
> >
> What run levels would get executed? I would prefer to mount over t
On Tue, Nov 20, 2012 at 09:50:39AM -0500, Daniel J Walsh wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 11/20/2012 09:36 AM, Daniel P. Berrange wrote:
> > On Tue, Nov 20, 2012 at 08:52:51AM -0500, Daniel J Walsh wrote:
> >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
> >>
> >>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/20/2012 09:36 AM, Daniel P. Berrange wrote:
> On Tue, Nov 20, 2012 at 08:52:51AM -0500, Daniel J Walsh wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1
>>
>> On 11/19/2012 07:41 PM, Lennart Poettering wrote:
>>> On Fri, 16.11.12 15:06, Da
On Tue, Nov 20, 2012 at 08:52:51AM -0500, Daniel J Walsh wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 11/19/2012 07:41 PM, Lennart Poettering wrote:
> > On Fri, 16.11.12 15:06, Daniel J Walsh (dwa...@redhat.com) wrote:
> >
> >> Isn't there a way to shut off systemV init scripts
On 11/20/2012 01:52 PM, Daniel J Walsh wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/19/2012 07:41 PM, Lennart Poettering wrote:
On Fri, 16.11.12 15:06, Daniel J Walsh (dwa...@redhat.com) wrote:
Isn't there a way to shut off systemV init scripts altogether, it just
so happens tha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/19/2012 07:41 PM, Lennart Poettering wrote:
> On Fri, 16.11.12 15:06, Daniel J Walsh (dwa...@redhat.com) wrote:
>
>> Isn't there a way to shut off systemV init scripts altogether, it just
>> so happens that we hit one on my machine. But in the
On 11/20/2012 12:41 AM, Lennart Poettering wrote:
On Fri, 16.11.12 15:06, Daniel J Walsh (dwa...@redhat.com) wrote:
>Isn't there a way to shut off systemV init scripts altogether, it just so
>happens that we hit one on my machine. But in the field a customer could have
>an init script and then
On Fri, 16.11.12 15:06, Daniel J Walsh (dwa...@redhat.com) wrote:
> Isn't there a way to shut off systemV init scripts altogether, it just so
> happens that we hit one on my machine. But in the field a customer could have
> an init script and then setup containers and systemd will attempt to star
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/16/2012 02:56 PM, Lennart Poettering wrote:
> On Fri, 16.11.12 09:23, Daniel J Walsh (dwa...@redhat.com) wrote:
>
>> The only problem I see is that now sysV init scripts are firing off
>> within the container. (iSCSI daemon). What can I do to s
On Fri, 16.11.12 09:23, Daniel J Walsh (dwa...@redhat.com) wrote:
> The only problem I see is that now sysV init scripts are firing off within the
> container. (iSCSI daemon). What can I do to stop this within the container?
Services such as the iscsi daemon which one can sort in the "driver"
ca
On Fri, 2012-11-16 at 09:23 -0500, Daniel J Walsh wrote:
> The only problem I see is that now sysV init scripts are firing off within the
> container. (iSCSI daemon). What can I do to stop this within the container?
ConditionVirtualization=!lxc-libvirt ?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The only problem I see is that now sysV init scripts are firing off within the
container. (iSCSI daemon). What can I do to stop this within the container?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with unde
13 matches
Mail list logo
