| 1 |
On 02/11/2015 03:20 PM, Rich Freeman wrote: |
| 2 |
> On Wed, Feb 11, 2015 at 5:37 PM, walt <w41ter@×××××.com> wrote: |
| 3 |
>> |
| 4 |
>> Yes, thank you! Did you use systemctl to make all the symlinks? I just did it |
| 5 |
>> all manually and it works, but I'm not sure how I would have done it using systemctl. |
| 6 |
>> |
| 7 |
> |
| 8 |
> systemctl enable <service> |
| 9 |
> |
| 10 |
> That looks in the unit's install section to see what target it should |
| 11 |
> be associated with. This is actually a nice feature - with openrc it |
| 12 |
> wasn't always obvious when things should go in the boot vs default |
| 13 |
> runlevel, etc. But, all that command does is create the symlinks in |
| 14 |
> the target.wants directory, so you can just create those yourself if |
| 15 |
> you want to. That actually works for anything - you can effectively |
| 16 |
> add a dependency to a unit by creating a directory of the appropriate |
| 17 |
> name and symlinking the dependency inside. |
| 18 |
|
| 19 |
The symlink that was puzzling me is this one: |
| 20 |
|
| 21 |
wpa_supplicant@×××××.service -> /usr/lib64/systemd/system/wpa_supplicant@.service |
| 22 |
|
| 23 |
The name of the symlink is not the same as the .service file it points to. |
| 24 |
Is there a systemctl command that would do that for me? |
Archives