1 |
Hello Benda, |
2 |
|
3 |
Actually this is not my convention. This is piggybacking on the systemd |
4 |
convention |
5 |
In the current system (openrc) net.eth0 is a symlink to net.lo and the |
6 |
interface is deduced at run-time and appropriate action is taken. |
7 |
In systemd instantiated services work in the same way. Symlink to the |
8 |
original service and the @ part is passed as a parameter and I guess it is |
9 |
supposed to be used the same way too i.e. the @ part is to be seen as an |
10 |
variable. So I thought this would be the best way to represent it in |
11 |
systemd setting. |
12 |
|
13 |
Hope this makes sense. |
14 |
|
15 |
|
16 |
On Sun, Jun 22, 2014 at 11:29 AM, <heroxbd@×××××.com> wrote: |
17 |
|
18 |
> Hey Rabi, |
19 |
> |
20 |
> Rabi Shanker Guha <guha.rabishankar@×××××.com> writes: |
21 |
> |
22 |
> > sudo systemctl restart net@eth0 |
23 |
> > sudo systemctl status net@eth0 |
24 |
> |
25 |
> Just curious how this naming scheme were formed. Intuitively, eth0 is a |
26 |
> subset of net, making "eth0@net" and "net.eth0" more natural. |
27 |
> |
28 |
> Benda |
29 |
> |
30 |
> |
31 |
|
32 |
|
33 |
-- |
34 |
Regards, |
35 |
Rabi |