| 1 |
On Thu, Jan 23, 2014 at 8:55 PM, Mansour Al Akeel |
| 2 |
<mansour.alakeel@×××××.com> wrote: |
| 3 |
> Canek, |
| 4 |
> Thank you. The output is attached. |
| 5 |
> |
| 6 |
> |
| 7 |
> On Thu, Jan 23, 2014 at 8:10 PM, Canek Peláez Valdés <caneko@×××××.com> wrote: |
| 8 |
>> On Thu, Jan 23, 2014 at 6:56 PM, Mansour Al Akeel |
| 9 |
>> <mansour.alakeel@×××××.com> wrote: |
| 10 |
>>> Hello all, |
| 11 |
>>> |
| 12 |
>>> I installed gnome3 few weeks ago, and had to migrate to systemd. |
| 13 |
>>> The network init scripts are working fine. But I am not sure how to |
| 14 |
>>> restart a specific interface. |
| 15 |
>>> For example in the past I used to do: |
| 16 |
>>> |
| 17 |
>>> /etc/init.d/net.eth0 restart |
| 18 |
>>> |
| 19 |
>>> The wlan0 starts through wpa_supplicant under openrc. |
| 20 |
>>> |
| 21 |
>>> I can not remember doing any modification to adopt to systemd. The |
| 22 |
>>> wpa_supplicant is not running under systemd, but wlan0 is working: |
| 23 |
>>> |
| 24 |
>>> neptune ~ # systemctl status wpa_supplicant |
| 25 |
>>> wpa_supplicant.service - WPA supplicant |
| 26 |
>>> Loaded: loaded (/usr/lib/systemd/system/wpa_supplicant.service; disabled) |
| 27 |
>>> Active: inactive (dead) |
| 28 |
>>> |
| 29 |
>>> Jan 23 19:54:20 neptune systemd[1]: Collecting wpa_supplicant.service |
| 30 |
>>> |
| 31 |
>>> |
| 32 |
>>> |
| 33 |
>>> I think it's because of dhcpcd, but not sure. |
| 34 |
>>> my question now, is how to stop wlan0 and start eth0 with systemd ?? |
| 35 |
>> |
| 36 |
>> Are you still using the unpredictable network interface names[1]? Are |
| 37 |
>> you using net.ifnames=0 in your kernel command line? |
| 38 |
>> |
| 39 |
>> Could you please post the whole output of "systemctl --full --all"? We |
| 40 |
>> need to know what services you have enabled. |
| 41 |
>> |
| 42 |
>> Regards. |
| 43 |
>> |
| 44 |
>> [1] http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ |
| 45 |
|
| 46 |
Please don't top post. |
| 47 |
|
| 48 |
Here is the answer: |
| 49 |
|
| 50 |
wpa_supplicant@×××××.service |
| 51 |
loaded active running |
| 52 |
WPA supplicant daemon (interface-specific version) |
| 53 |
|
| 54 |
wpa_supplicant offers a template unit, wpa_supplicant@.service. From |
| 55 |
man:systemd.unit(1) |
| 56 |
|
| 57 |
"Optionally, units may be instantiated from a template file at |
| 58 |
runtime. This allows creation of multiple units from a single |
| 59 |
configuration file. If systemd looks for a unit configuration file, it |
| 60 |
will first search for the literal unit name in the filesystem. If that |
| 61 |
yields no success and the unit name contains an "@" character, systemd |
| 62 |
will look for a unit template that shares the same name but with the |
| 63 |
instance string (i.e. the part between the "@" character and the |
| 64 |
suffix) removed. Example: if a service getty@××××.service is requested |
| 65 |
and no file by that name is found, systemd will look for |
| 66 |
getty@.service and instantiate a service from that configuration file |
| 67 |
if it is found." |
| 68 |
|
| 69 |
Something is starting wpa_supplicant@×××××.service. Could you run: |
| 70 |
|
| 71 |
systemctl list-dependencies --reverse wpa_supplicant@×××××.service |
| 72 |
|
| 73 |
That will tell you what is pulling wpa_supplicant@×××××.service. Also, |
| 74 |
the following: |
| 75 |
|
| 76 |
systemctl is-enabled wpa_supplicant@×××××.service |
| 77 |
|
| 78 |
will tell you if the unit is enabled or not. |
| 79 |
|
| 80 |
Regards. |
| 81 |
-- |
| 82 |
Canek Peláez Valdés |
| 83 |
Posgrado en Ciencia e Ingeniería de la Computación |
| 84 |
Universidad Nacional Autónoma de México |
Archives