10:59 p.m.
This is a multi-part message in MIME format.
--------------090603020909070809040005
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
On 06/26/2015 12:51 PM, Tim Macy wrote:
On my configuration the FC device needs to come up after the Ethernet
module is loaded. Using the methods suggested it is trying the load
too early. I need a way to run the modprobe very late in the boot process.
You could create a script that rc.local calls in the background
---rc.local---
/path/to/script &
#!/bin bash
sleep 120 (or however long)
modprobe XXXXX
Thank you, Tim
On Jun 26, 2015 2:57 AM, "Fabian Deutsch" <fdeutsch(a)redhat.com
<mailto:fdeutsch@redhat.com>> wrote:
----- Original Message -----
> I recently added FCOE to my oVirt-node servers and I need a way
for the
> modprobe to persist through reboot.
Hey Tim,
you can try adding the modprobe command to /etc/rc.d/rc.local
And the run
$ chmod a+x /etc/rc.d/rc.local
$ persist /etc/rc.d/rc.local
This might work, but it depends on when the FC device needs to be
accessible.
- fabian
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--------------090603020909070809040005
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 06/26/2015 12:51 PM, Tim Macy
wrote:<br>
</div>
<blockquote
cite="mid:CAKQJrBNMaQxiyw7YSgUF8Fyt5cik+sW3n5+VMsCjhA8yrxUoBQ@mail.gmail.com"
type="cite">
<p dir="ltr">On my configuration the FC device needs to come up
after the Ethernet module is loaded. Using the methods suggested
it is trying the load too early. I need a way to run the
modprobe very late in the boot process.</p>
</blockquote>
<br>
You could create a script that rc.local calls in the background<br>
<br>
---rc.local---<br>
/path/to/script &<br>
<br>
<br>
<br>
#!/bin bash<br>
sleep 120 (or however long)<br>
modprobe XXXXX<br>
<blockquote
cite="mid:CAKQJrBNMaQxiyw7YSgUF8Fyt5cik+sW3n5+VMsCjhA8yrxUoBQ@mail.gmail.com"
type="cite">
<p dir="ltr">Thank you, Tim</p>
<div class="gmail_quote">On Jun 26, 2015 2:57 AM, "Fabian
Deutsch"
<<a moz-do-not-send="true"
href="mailto:fdeutsch@redhat.com">fdeutsch@redhat.com</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">-----
Original Message -----<br>
> I recently added FCOE to my oVirt-node servers and I need
a way for the<br>
> modprobe to persist through reboot.<br>
<br>
Hey Tim,<br>
<br>
you can try adding the modprobe command to /etc/rc.d/rc.local<br>
And the run<br>
<br>
$ chmod a+x /etc/rc.d/rc.local<br>
$ persist /etc/rc.d/rc.local<br>
<br>
This might work, but it depends on when the FC device needs to
be accessible.<br>
<br>
- fabian<br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated"
href="mailto:Users@ovirt.org">Users@ovirt.org</a>
<a class="moz-txt-link-freetext"
href="http://lists.ovirt.org/mailman/listinfo/users">http://...
</pre>
</blockquote>
<br>
</body>
</html>
--------------090603020909070809040005--