On Wed, Apr 20, 2016 at 05:34:49AM +0900, Greg KH wrote:
> On Tue, Apr 19, 2016 at 05:25:09PM -0300, Flavio Leitner wrote:
> >
> > Hello,
> >
> > I have a service that needs to start after all the devices (network
> > cards at least) have been properly process
Hello,
I have a service that needs to start after all the devices (network
cards at least) have been properly processed by udev. Pretty much
like the old 'network' sysv script.
Any suggestion?
Thanks,
--
fbl
___
systemd-devel mailing list
On Thu, 24 Mar 2016 20:01:23 +0200
Mantas Mikulėnas <graw...@gmail.com> wrote:
> On Thu, Mar 24, 2016 at 6:21 PM, Flavio Leitner <f...@sysclose.org> wrote:
>
> >
> > Hi,
> >
> > I am trying to create services and timers per user but on a recent
> >
Hi,
I am trying to create services and timers per user but on a recent
CentOS minimal installation it doesn't work out of the box:
$ ssh
server$ systemctl --user daemon-reload
Failed to get D-Bus connection: No such file or directory
I found some websites talking about creating a session with
would unbind eth0 from the previous
driver (if needed) and bind the device to vfio-pci driver.
fbl
> --
> Mantas Mikulėnas
> On Sep 28, 2015 21:48, "Flavio Leitner" <f...@sysclose.org> wrote:
>
> > On Mon, Sep 28, 2015 at 08:06:50PM +0200, Kay Sievers wrote
On Mon, Sep 28, 2015 at 08:06:50PM +0200, Kay Sievers wrote:
> On Sun, Sep 27, 2015 at 11:37 PM, Flavio Leitner <f...@sysclose.org> wrote:
> > I am looking for guidance on how to properly resolve driver binding
> > with systemd (which seems to me the best place to do t
Hello,
I am looking for guidance on how to properly resolve driver binding
with systemd (which seems to me the best place to do that).
Today we have 2 or more kernel drivers for the same device. For
instance, we can use the standard NIC driver, or UIO driver or even
VFIO driver.
Since all
On Tue, Nov 25, 2014 at 10:42:12AM +, Richard Maw wrote:
On Tue, Nov 25, 2014 at 12:09:07AM -0200, Flavio Leitner wrote:
Hello,
The Open vSwitch is comprised by two daemons. One is a database and
another is the switch itself.
Currently we have the openvswitch.service which
Hello,
The Open vSwitch is comprised by two daemons. One is a database and
another is the switch itself.
Currently we have the openvswitch.service which start/stop/reload the
service (both daemons) just fine.
However, we need to support hot-upgrade which means to stop the
vswitch daemon first,
