Custom Query (541 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (58 - 60 of 541)

Ticket Resolution Summary Owner Reporter
#53 fixed Sniffwave search for SCN or SCNL somebody stefan
Description
Lynn Dietz wrote:
> Hi Paul,
>
> I've got a gripe with the current sniffwave on an issue that's bitten me
> more than once, and just bit me again.
>
> If you run:
> "sniffwave RING_NAME sta comp net loc y/n"
> then sniffwave will only look for TYPE_TRACEBUF2 messages.
>
> If you run:
> "sniffwave RING_NAME sta comp net y/n"
> then sniffwave will only look for TYPE_TRACEBUF messages.
>
> While this may seem logical, it actually make sniffwave less useful as a
> trouble-shooting tool.
>
> When I originally wrote sniffwave, it would always look for both
> TYPE_TRACEBUF and TYPE_TRACEBUF2 messages all the time, generously
> matching the fields you provided, using wildcard if you ommitted 'loc'.
> Then you could tell if a message was BUF or BUF2 by the logo at the end
> of the line. I think is also formatted S.C.N for BUF and S.C.N.L for BUF2.
>
> It was much easier to troubleshoot SCN vs SCNL issues with this original
> behavior. Like, if you knew you were importing a station code STA, but
> didn't know the format or rest of SCNL, you could run:
> "sniffwave RING_NAME STA wild wild wild n"
> The results would tell you the rest of the SCNL and the format. But with
> the current sniffwave, if you run that command, you won't see any output
> if you are importing SCN data, and you have to be smart enough to
> remember to invoke sniffwave without the last 'wild' to check for
> SCN-only data.
>
> Can you change sniffwave so that it behaves like originally, always
> looks for both BUF & BUF2 regardless of the number of command-line args ?
>
> Thanks,
> Lynn
#55 fixed Update params directory for 7.4 release somebody stefan
Description

make sure that the .d and .desc files in /params are all current and updated from all the src directories (also earthworm.d and earthworm_global.d from the environment directory), so that users can easily find any parameter for a module they wish to use.

#56 fixed Earthworm Standard Relase Procedures somebody stefan
Description

Only to be done after testing is complete and we're ready to bundle:


steps to do for every Earthworm release

First, insure that you can compile cleanly on all platforms.

Run a make clean, make clean bin, make, and then make clean and make clean bin again for all platforms. search for any .o or .obj files remaining, or executables remaining

TRAP the output of the make to a file

Windows

nmake clean_nt

nmake clean_bin_nt

nmake nt > make.notes 2>&1

Solaris

For Solaris, since you use csh or tcsh to compile:

make solaris >& solaris_make.out

Linux

For Linux, since you use bash to compile:

make unix &> linux_make.out

Check for errors in the makes, and resolve them.

grep -i error

Run the memphis test suite on all platforms, and make sure you get the expected numerical results

edit #define VERSION in src/libsrc/util/startstop_unix_generic.c, src\system_control\startstop_nt/startstop.c and src\system_control\startstop_service/startstop_service.c

copy release_notes.working to release_notes.v7.4 (or whatever the version number is ...) Check the new file into CVS. clear release_notes.working of any information no longer relevant

PUT THE RELEASE NOTES WORKING into documentation ewdoc/WEB_DOC/RELEASE and link from index.html!

TAG the release (put actual CVS command type here) ew_M_m_release

where M is major (eg 7) and m is minor (eg 1)

For example:

cvs rtag ew_7_1_release earthworm

do a CVS export rather than a checkout to create the distribution tar.gz or zip so you don't get CVS directories. Or do a checkout and then go and delete the CVS directories (export only works from a tag, so may not work if you've tweaked).

For example:

cvs export -r ew_7_1_release earthworm

or

find . -type d -name CVS | xargs rm -r

Compile all platforms.

Search for and delete all .obj files or .o files to save space in the distribution

Make .zip or .tar.gz files for all platforms with binaries. Make sure it expands to version number directory, ie: "earthworm_7.3"

[this should already be in the environment file you source:] compile Windows with the following flags:

GLOBALFLAGS=/D_WINNT /D_INTEL /D_CRT_SECURE_NO_DEPRECATE /D_USE_32BIT_TIME_T

[this should already be in the environment file you source:] compile Linux with the following flag if you're on a 64 bit system: -m32

make sure that the .d and .desc files in /params are all current and updated from all the src directories (also earthworm.d and earthworm_global.d from the environment directory)

for all builds, make sure all .d and .desc files are UNIX line endings (dos2unix) [NO LONGER NEEDED AS OF v7.2]

clean up the ew_nt.cmd or ew_linux.bash, etc. after you do your compile so you leave good directory paths

make sure adsend binary is in the release [Windows only]

Naming conventions for your bundles is like:

v7.3-linux-32-bin.tar.gz

v7.3-linux-64bit-bin.tar.gz

v7.3-macosx-intel-bin.tar.gz

v7.3-macosx-ppc-bin.tar.gz

v7.3-solaris-intel-bin.tar.gz

v7.3-solaris-sparc-bin.tar.gz

v7.3-win-bin.zip

v7.3-src.tar.gz

v7.3-src.zip

scp your releases to:

istitwoc@…:/home/istitwoc/public_ftp/pub/ew

istitwoc@…:/home/istitwoc/public_ftp/pub/ew

Note: See TracQuery for help on using queries.