Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Posthook command line parameters

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Posthook command line parameters


Chronological Thread 
  • From: Aaron Brown <>
  • To: Gaetano Vocca <>
  • Cc: "" <>
  • Subject: Re: [perfsonar-user] Posthook command line parameters
  • Date: Tue, 13 Jan 2015 16:49:35 +0000
  • Accept-language: en-US
  • Authentication-results: sesanv.com; dkim=none (message not signed) header.d=none;sesanv.com; dmarc=none action=none header.from=internet2.edu;

Hey Gaetano,

If you’re asking if there’s a syntax problem with having a posthook like “/path/to/posthook -i -w 1024”, then no, there isn’t. The “syntax error” thing is a poor error message. bwctld tries to execute the script with the “—validate” flag when it starts up, and since it doesn’t support the parameters, it’s bombing out and printing out a syntax error message.

Cheers,
Aaron

On Jan 13, 2015, at 9:34 AM, Gaetano Vocca <> wrote:

Thank you Aaron.
Do you know if any of the bwctld.conf options foresee a blank separated list of values? In this case any change to support the command line parameters would impact this functionality.

 

Cheers
Gaetano

 

Da: Aaron Brown [mailto:] 
Inviato: martedì 13 gennaio 2015 14:15
A: Gaetano Vocca
Cc: 
Oggetto: Re: [perfsonar-user] Posthook command line parameters

 

Hey Gaetano, 

 

The posthook currently doesn’t support command-line parameters, unfortunately. It’d probably be straight-forward to add, though.

 

Cheers,
Aaron

 

On Jan 12, 2015, at 11:12 AM, Gaetano Vocca <> wrote:

 

Hi all,
is it possible to use command line parameters in a posthook definition?
Currently, if I add any, I get

 

/usr/local/bin/bwctld -c /etc/bwctld -R /var/run
/etc/bwctld/bwctld.conf:233 Problem parsing config file
/etc/init.d/bwctld start: bwctld could not be started

 

When restarting bwctld. Is it as expected?

 

Thank you
Gaetano




Archive powered by MHonArc 2.6.16.

Top of Page