[Yves Guerin]

Dear,

Use a variant and put the length you need in the field definition.

Regards,

Yves

[Yves Guerin]

Dear,

To get information about loaded alerts (from the console):

Code:

setsite X
hcicmd -t d -p hcimonitord -c “show enabled”

or

Code:

hcicmd -t d -p hcimonitord -c “show all”

We experienced some trouble with the GUI when we loaded an alert file, it seems to load all .alrt file, so we renamed all alert files with different extension and keep the active alert file with .alrt extension ( run cis5.8 ) .

Regards,

Yves

[Yves Guerin]

Dear,

Nice scripts with expect but using tclcurl seems lineless  😉

Regards,

Yes

[Yves Guerin]

Dear,

Yes, I use sftp or something like that (may be ftps) I have to send two files to an windows sftp server

And more easy than Java class

My code with tclcurl

On top of my tcl file I define a global var

Code:

set gAvoirTclCurl 0

In my tcl proc: get reference to my global var

Code:

upvar #0 gAvoirTclCurl avoirTclCurl

in start state

Code:

# obtenir le pkg TclCurl
           if {[catch {set idPkg [package require TclCurl]} erreur]} {
               # err
               set defAction ERROR

               set  msgErr “$msgErr + ERREUR paquetage TclCurl = $erreur”
           } else {
               # ok
               puts “$module: TclCurl = $idPkg”
               set avoirTclCurl 1
           }

in run state:

Code:

# get parameters from the command line
…

# check if tclcurl is loaded
if {1 == $avoirTclCurl} {
    # have pkg tclcurl loaded
     if {[catch { ::curl::transfer -verbose $verbose
                                            -noprogress $noprogress
                                            -url $url$nomF
                                            -userpwd “$userpwd”
                                            -sslverifypeer $sslverifypeer
                                            -ftpssl $ftpssl
                                            -sslverifyhost $sslverifyhost
                                            -infile $fichier
                                            -upload $upload
                                            -errorbuffer erreur
                                            -postquote [list “rnfr $nomF” “rnto $nomFStrm$ext”]
                  } erreur]} {
                                   # error handler
                                  } else {
                                       # sftp transfert is ok
                                  }
} else {
       # error handler for not having tclcurl loaded
}

hope that help

Regards,

Yves

[Yves Guerin]

Dear,

to send file to ftp server I used tclCurl (bundle in cloverleaf) from my tcl script, works great and more easy than using expect.

Regards,

Yves

[Yves Guerin]

Dear,

To check the tcl procs I use tclCheck <a href="http://catless.ncl.ac.uk/Programs/tclCheck/&#8221; class=”bbcode_url”>http://catless.ncl.ac.uk/Programs/tclCheck/

Regards,

Yves[/url]

[Yves Guerin]

Dear,

Use Firefox, Opera or Chrome and dished the IE nightmare…

Regards,

Yves

[Yves Guerin]

Dear,

On Linux use the do2unix utility (man dos2unix) to convert from windows to Linux (end of line)

Regards,

Yves

[Yves Guerin]

Dear,

We still running cis.5.8

Regards,

Yves

[Yves Guerin]

Dear,

We do a cycling of the data for every inbound interfaces and some time outbound too.  We keep in the engine around 3 months of data (in separate directories) and we perfomed a backup every month of the data to dvd (around 3.5 G disk space for messages: .idx and .msg files).  I am wondering about the space that the db file will take on disk ?  Will we able to purge or save the db file as we did with the flat data file (.idx and .msg) and keep only 3 months on the engine and backup the rest (older than 3 months) to dvd ?

Regards,

Yves

[Yves Guerin]

Dear,

We have so many scripts to handle the smart flat file that going to db file will be for us a big trouble. We will have to convert every script to handle the new format.  If you provide tools to do the extract as the same format as smart flat file (.idx, .msg) it should be manageable but we prefer to keep the smart flat file format.

Regards,

Yves

[Yves Guerin]

Hello,

Rob Abbott wrote:

What Jim C. says about GDBM is very true – this is not recommended as it’s been deprecated and is no longer shipped with Cloverleaf.

[Yves Guerin]

Dear,

Yes, the client needs to get this response before sending another one.

Regards,

Yves

[Yves Guerin]

Dear,

Yes, because I need to send back the message as a reply to the client through the inbound connexion (server)

client — request –> ConnexionIn — xlate —> connexionOut

ConnexionOut — reply –> connexionIn — reponse —> client

Regards,

Yves

[Yves Guerin]

Dear,

Ooops, not supported 😯 , ok I will stick with my tcl + tclX or shell script to parse the NetConfig.  

Regards,

Yves

[Author]

Replies