also sprach Brian May <firstname.lastname@example.org> [2008.08.06.2242 -0300]: > Packages that come to mind that want to alter the environment of it > parent are: > > * ssh-agent You have to eval the output, no? > * <http://modules.sourceforge.net/> *horror* ! :) Neither of those affect /etc/dhcp3/dhclient-*-hooks.d though... > I guess you could also write a shell script to a temp file and > then source that. Not sure if this is any cleaner though. The problem is that netconf has no dhclient-script anymore as it parses dhclient REASONS directly and then proceeds to use e.g. IP address and router stuff as if it had been gathered from /e/n/i. Thus, hooks are execvp()'d from netconf directly. If I wanted to allow hooks to modify the environment, I'd have to execvp() sh -c '. the_hook; env | while read line; do echo "ENVIRONMENT:$line' and then parse that stuff out of stdout, which, to put it mildly, is ASS. I'd really rather not. -- .''`. martin f. krafft <email@example.com> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems consciousness: that annoying time between naps.
Description: Digital signature (see http://martin-krafft.net/gpg/)