Re: restarting services if config files were changed

> On Mon, 28 Sep 2009 21:29:44 +0200, Andreas Schuldei > said: > i am in the process to create infrastructure for restarting > services which configuration files changed in the current > softupdate run. > currently i plan to set a flag (in an environment variable like

Re: setup-storage: set vgname to hostname

Thomas Neumann a écrit : You can write a hook that replaces $HOSTNAME with the current hostname. This is the easiest way. As a bonus: It even works! ;) tschüß thomas do you know wich variable we could use in a way that is supported by FAI . I mean using a variable like $HOSTNAME or

Re: setup-storage: set vgname to hostname

hiya > Thomas Neumann a écrit : >>> You can write a hook that replaces $HOSTNAME with the current >>> hostname. This is the easiest way. >> As a bonus: It even works! > do you know wich variable we could use in a way that is supported by FAI > . I mean using a variable like $HOSTNAME or whatever

Re: setup-storage: set vgname to hostname

I prefer using my own variables in my own namespace and initialize them from a "known good" source - like $HOSTNAME. This may not be the most obvious solution, but this way you can guarantee that "your" variable has a valid value. And if $HOSTNAME turns out to be unrealiable - or undesired - the

Re: restarting services if config files were changed

On 09/29/2009 01:38 PM, Thomas Lange wrote: >> On Mon, 28 Sep 2009 21:29:44 +0200, Andreas Schuldei >> said: > > > i am in the process to create infrastructure for restarting > > services which configuration files changed in the current > > softupdate run. > > > currentl

Re: setup-storage: set vgname to hostname

On 09/30/2009 12:11 AM, Jean Spirat wrote: > >> I prefer using my own variables in my own namespace and initialize >> them from a "known good" source - like $HOSTNAME. This may not be >> the most obvious solution, but this way you can guarantee that >> "your" variable has a valid value. And if $HO

problems with PATTERN/LINE in ainsl(1)

Hi! I have something like this: #! /bin/sh ainsl -a $target/etc/sudoers "%adm ALL = NOPASSWD: /bin/su -[mp]" exit 0 Got the expected output (in /etc/sudoers without LINE): %adm ALL = NOPASSWD: /bin/su -[mp] Running again (now containing LINE) leads to: %adm ALL = NOPASSWD: /bin/su -[mp]

Re: problems with PATTERN/LINE in ainsl(1)

On 30.09.2009 02:32, Darshaka Pathirana wrote: > Hi! > > I have something like this: > > > #! /bin/sh > ainsl -a $target/etc/sudoers "%adm ALL = NOPASSWD: /bin/su -[mp]" > exit 0 > > > Got the expected output (in /etc/sudoers without LINE): > > %adm ALL = NOPASSWD: /bin/su -[mp] > > Runnin

Re: problems with PATTERN/LINE in ainsl(1)

On 30.09.2009 02:40, Darshaka Pathirana wrote: > On 30.09.2009 02:32, Darshaka Pathirana wrote: >> Hi! >> >> I have something like this: >> >> >> #! /bin/sh >> ainsl -a $target/etc/sudoers "%adm ALL = NOPASSWD: /bin/su -[mp]" >> exit 0 >> >> >> Got the expected output (in /etc/sudoers without LIN