Acct-Input-Gigawords in Exec-Program env
Hi list, I'm having trouble identifying the Acct-Input-Gigawords field in the shell environment of Exec-Program. Does anyone know how to ensure that it is being exported? I have a shell script (test-exec.sh) which according to examples in docs goes like so: #!/bin/sh /usr/bin/printenv > /tmp/env.txt Then in my acct_users, again by example: DEFAULT Acct-Status-Type == Stop Exec-Program = "/opt/bin/test-exec.sh" This correctly prints out all the env variables to the file as expected. The problem is however that with ADSL traffic regularly exceeding the Gigawords boundaries of Acct-Input-Octets, we rely on the Acct-Input-Gigawords for the overflow. This is unfortunately not showing up in the list of env variables. Anyway to resolve this? Thanks -Rob
Rob Hartzenberg wrote:
I'm having trouble identifying the Acct-Input-Gigawords field in the shell environment of Exec-Program. Does anyone know how to ensure that it is being exported?
Read the output of debugging mode. If it's in the packet, it will be exported to any shell program. See doc/variables.txt for documentation on how this happens.
This correctly prints out all the env variables to the file as expected. The problem is however that with ADSL traffic regularly exceeding the Gigawords boundaries of Acct-Input-Octets, we rely on the Acct-Input-Gigawords for the overflow. This is unfortunately not showing up in the list of env variables.
Anyway to resolve this?
Make the NAS send the attribute. If the NAS isn't sending the attribute, how do you expect the server to log it? What value do you expect the server to use? Does it invent the attribute out of thin air? Alan DeKok.
participants (2)
-
Alan DeKok -
Rob Hartzenberg