Hello ! Are all possible Shorewall error messages to be found in a single place ? Background for the question: to eventually ''translate'' to user device context any error messages. Context in which, for instance, the user does not know about shorewall specifics. The idea is to keep the interface with shorewall simple. Ah, are there different system error codes returned for each specific error ? Thanks ! ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
On 7/24/10 11:29 AM, lanas wrote:> Hello ! > > Are all possible Shorewall error messages to be found in a single > place ?No.> > Background for the question: to eventually ''translate'' to user device > context any error messages. Context in which, for instance, the user > does not know about shorewall specifics. The idea is to keep the > interface with shorewall simple. Ah, are there different system error > codes returned for each specific error ?No. Sorry, -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________ ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
On Sat, 24 Jul 2010 11:59:09 -0700, Tom Eastep <teastep@shorewall.net> wrote :>> Are all possible Shorewall error messages to be found in a single >> place ? > > No.Thanks. If I were to validate user data entry to create Shorewall config files, is there a description of what Shorewall accepts/rejects as strings, zone names, host names, ..., eg. what is permitted or not in the config files for Shorewall to process its config files ? ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
On 7/24/10 12:56 PM, lanas wrote:> On Sat, 24 Jul 2010 11:59:09 -0700, > Tom Eastep <teastep@shorewall.net> wrote : > >>> Are all possible Shorewall error messages to be found in a single >>> place ? >> >> No. > > Thanks. If I were to validate user data entry to create Shorewall > config files, is there a description of what Shorewall accepts/rejects > as strings, zone names, host names, ..., eg. what is permitted or not in > the config files for Shorewall to process its config files ?I''ve added a section covering naming at http://www.shorewall.net/configuration_file_basics.htm#Names. -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________ ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
On Sat, 24 Jul 2010 11:59:09 -0700, Tom Eastep <teastep@shorewall.net> a wrote :> On 7/24/10 11:29 AM, lanas wrote: > > Hello ! > > > > Are all possible Shorewall error messages to be found in a single > > place ? > > No.Are all error messages formatted in the following way: ERROR: <Message> : <Shorewall specifics eg. file, data path, line number, etc..> Eg.: ERROR: Unknown Interface (fe-3-2) : I would like to rely on the presence of the two '':'' to post-process those strings. OTOH, warning messages seems to differ - are they all in the same format with the six asterisk characters? Eg.: WARNING: *** wan is an EMPTY ZONE *** Thanks ! ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
On 7/25/10 3:28 PM, lanas wrote:> On Sat, 24 Jul 2010 11:59:09 -0700, > Tom Eastep <teastep@shorewall.net> a wrote : > >> On 7/24/10 11:29 AM, lanas wrote: >>> Hello ! >>> >>> Are all possible Shorewall error messages to be found in a single >>> place ? >> >> No. > > Are all error messages formatted in the following way: > > ERROR: <Message> : <Shorewall specifics eg. file, data path, line > number, etc..> > > Eg.: > > ERROR: Unknown Interface (fe-3-2) : > > I would like to rely on the presence of the two '':'' to post-process > those strings. >The second colon (":") is present only if the compiler can attribute the error to a particular file and line number. All fatal errors detected by the compiler product a message beginning with "ERROR: ".> OTOH, warning messages seems to differ - are they all in the same > format with the six asterisk characters? > > Eg.: > > WARNING: *** wan is an EMPTY ZONE *** >The only distinguishing feature of warning messages is that they start with "WARNING: ". -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________ ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first