On Thu, Feb 12, 2015 at 7:28 PM, Keller, Jacob E
wrote:
> On Thu, 2015-02-12 at 18:51 +0100, Lennart Poettering wrote:
>> On Thu, 12.02.15 17:48, Keller, Jacob E (jacob.e.kel...@intel.com) wrote:
>>
>> > Ok, I'll try with latest Git first, and if it still fails I'll try
>> > reverting the patch Le
On Thu, 2015-02-12 at 18:51 +0100, Lennart Poettering wrote:
> On Thu, 12.02.15 17:48, Keller, Jacob E (jacob.e.kel...@intel.com) wrote:
>
> > Ok, I'll try with latest Git first, and if it still fails I'll try
> > reverting the patch Lennart suggested.
>
> git already has that patch reverted now.
On Thu, 12.02.15 17:48, Keller, Jacob E (jacob.e.kel...@intel.com) wrote:
> Ok, I'll try with latest Git first, and if it still fails I'll try
> reverting the patch Lennart suggested.
git already has that patch reverted now.
Lennart
--
Lennart Poettering, Red Hat
__
On Thu, 2015-02-12 at 14:23 +0100, Tom Gundersen wrote:
> On Thu, Feb 12, 2015 at 11:45 AM, Lennart Poettering
> wrote:
> > On Wed, 11.02.15 22:28, Keller, Jacob E (jacob.e.kel...@intel.com) wrote:
> >
> >> On Wed, 2015-02-11 at 21:46 +0100, Lennart Poettering wrote:
> >> > On Wed, 11.02.15 20:36,
On Wed, Feb 11, 2015 at 09:32:00PM +0100, Lennart Poettering wrote:
> On Wed, 11.02.15 20:22, Keller, Jacob E (jacob.e.kel...@intel.com) wrote:
>
> > > > I actually see the same behavior now again, so the removal of
> > > > biosdevname does not solve this problem! :(
> > > >
> > > > Is there any
On Thu, Feb 12, 2015 at 11:45 AM, Lennart Poettering
wrote:
> On Wed, 11.02.15 22:28, Keller, Jacob E (jacob.e.kel...@intel.com) wrote:
>
>> On Wed, 2015-02-11 at 21:46 +0100, Lennart Poettering wrote:
>> > On Wed, 11.02.15 20:36, Keller, Jacob E (jacob.e.kel...@intel.com) wrote:
>> >
>> > > > > Y
On Wed, 11.02.15 22:28, Keller, Jacob E (jacob.e.kel...@intel.com) wrote:
> On Wed, 2015-02-11 at 21:46 +0100, Lennart Poettering wrote:
> > On Wed, 11.02.15 20:36, Keller, Jacob E (jacob.e.kel...@intel.com) wrote:
> >
> > > > > Yes. I believe that possibly the netlink messages are occurring too
On Wed, 2015-02-11 at 21:46 +0100, Lennart Poettering wrote:
> On Wed, 11.02.15 20:36, Keller, Jacob E (jacob.e.kel...@intel.com) wrote:
>
> > > > Yes. I believe that possibly the netlink messages are occurring too
> > > > early before networkd has started. Thus, when I restart the service
> > > >
On Wed, 11.02.15 20:36, Keller, Jacob E (jacob.e.kel...@intel.com) wrote:
> > > Yes. I believe that possibly the netlink messages are occurring too
> > > early before networkd has started. Thus, when I restart the service
> > > after startup it works fine.
> >
> > Well, the first thing after subs
On Wed, 2015-02-11 at 21:32 +0100, Lennart Poettering wrote:
> On Wed, 11.02.15 20:22, Keller, Jacob E (jacob.e.kel...@intel.com) wrote:
>
> > > > I actually see the same behavior now again, so the removal of
> > > > biosdevname does not solve this problem! :(
> > > >
> > > > Is there any more in
On Wed, 11.02.15 20:22, Keller, Jacob E (jacob.e.kel...@intel.com) wrote:
> > > I actually see the same behavior now again, so the removal of
> > > biosdevname does not solve this problem! :(
> > >
> > > Is there any more information I can provide?
> >
> > Hmm, it appears as if networkd complete
On Wed, 2015-02-11 at 19:39 +0100, Lennart Poettering wrote:
> On Wed, 04.02.15 21:58, Keller, Jacob E (jacob.e.kel...@intel.com) wrote:
>
> > Hi again,
> >
> > On Tue, 2015-02-03 at 19:00 +, Keller, Jacob E wrote:
> > > Hey,
> > >
> > > I've recently been using systemd-networkd to great suc
On Wed, 04.02.15 21:58, Keller, Jacob E (jacob.e.kel...@intel.com) wrote:
> Hi again,
>
> On Tue, 2015-02-03 at 19:00 +, Keller, Jacob E wrote:
> > Hey,
> >
> > I've recently been using systemd-networkd to great success on a few of
> > my machines here. However I ran into an interesting prob
Hi again,
On Tue, 2015-02-03 at 19:00 +, Keller, Jacob E wrote:
> Hey,
>
> I've recently been using systemd-networkd to great success on a few of
> my machines here. However I ran into an interesting problem on at least
> 2 machines so far. I've included the output of journal for
> systemd-ne
On Tue, 2015-02-03 at 19:00 +, Keller, Jacob E wrote:
> Hey,
>
> I've recently been using systemd-networkd to great success on a few of
> my machines here. However I ran into an interesting problem on at least
> 2 machines so far. I've included the output of journal for
> systemd-networkd with
Hey,
I've recently been using systemd-networkd to great success on a few of
my machines here. However I ran into an interesting problem on at least
2 machines so far. I've included the output of journal for
systemd-networkd with Environment=SYSTEMD_LOG_LEVEL=debug as was
suggested on another post.
16 matches
Mail list logo
