$action in /etc/netctl/hooks/*

[joukewitteveen]

$action in /etc/netctl/hooks/*

[joukewitteveen]

The profile and hooks are sourced at each action. When this happens, you'll find the following environment variables set: INTERFACE, SSID, ACTION. Also, the Profile variable is set.

[graywolf]

I don't agree with you sir.

I have executable script /etc/netctl/hooks/test , which IS executed. Content of this file is:

#!/bin/bash
echo $ACTION > /tmp/test
echo $INTERFACE >> /tmp/test
echo $SSID >> /tmp/test
echo $PROFILE >> /tmp/test

It creates file /tmp/test, but this file only contains for blank lines.

Action which executes the hook is:

netctl stop wlp4s0-orchiprg

So this may be a bug? Or am I doing something wrong?

[joukewitteveen]

The variables are only set when the connection actually changes. This means that netctl-auto hands-off the connection to wpa_supplicant, which does its magic (including setting the variables mentioned) whenever the connection changes. Hence the initial starting and stopping are not part of this scheme. You could complement your setup with ExecUpPost and ExecDownPre.

[graywolf]

So if I got it right I need to add this two hooks into EVERY profile I have? Don't take me wrong, netctl is pretty good thing, but this is just stupid.

[joukewitteveen]

You could also specify them in a hook file or an interface file, effectively making it the default for every profile or every profile for a specific interface.

[graywolf]

Hey, that's great ^_^ thanks