I believe that "Just one profile" is in fact about static profiles and "Multiple profiles" is in fact about profiles managed dynamically with respect to whether NIC's are connected or not. This is misleading, and should be corrected. What do you think? Doru001 (talk) 09:16, 13 July 2013 (UTC)
- I've updated the section, let me know if there are more things to clarify. -- Lahwaacz (talk) 16:15, 25 July 2013 (UTC)
Altering a currently enabled profile
Concerning this note:
- If there is ever a need to alter a currently enabled profile, execute
netctl reenable <profile>to apply the changes.
- interface is hardware minus, e.g firstname.lastname@example.org or email@example.com
I find the second line in this note confusing, and the first line may be unnecessary. I found myself having to reboot my system to get any wireless profile changes to take effect. Through trial and error, I finally figured out the command
systemctl restart netctl-auto@<interface>.service allows the changes to take effect without requiring a reboot. Further, it appears that the command
netctl reenable <profile> is not necessary to achieve these results; although, some profile modifications did require that I issue the
systemctl restart netctl-auto@<interface>.service command twice before my wireless Internet connection would come back up. Has anyone else observed this?
Mc33 (talk) 04:59, 17 July 2013 (UTC)
- From netctl(1):
reenable [PROFILE] Reenable the systemd unit for the profile specified. This is effectively a combination of ‘disable’ and ‘enable’.
- So I'd say the first line of the note is absolutely incorrect. I think your command
systemctl restart netctl-auto@<interface>.serviceshould be listed instead, and we should probably add simple
netctl restart <profile>too in case people don't use
netctl-auto@.service. -- Lahwaacz (talk) 07:45, 17 July 2013 (UTC)
- Regarding the second line, I have absolutely no idea of what does interface is hardware minus mean... -- Lahwaacz (talk) 07:45, 17 July 2013 (UTC)