integrit-users — mailing list for discussion of issues related to using integrit

Re: [Integrit-users] intel solaris core dump

[Wes B. <fb...@en...>]

With debugging output:

Starting program: /opt/integrit2/sbin/integrit -C
/opt/integrit/conf/integrit.conf
  
Program received signal SIGSEGV, Segmentation fault.
0x8073f6a in _init ()
(gdb) step
Single stepping until exit from function _init,
which has no line number information.
  
Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.


I've tinkered with it some, but haven't gotten any further than this.  Any thoughts?



On Wed, Oct 31, 2001 at 07:56:52AM -0500, Ed L Cashin wrote:
> Wes Byne <fb...@en...> writes:
> 
> > hello,
> > 
> > I installed integrit 2.03 on solaris intel tonight, but when I try to execute integrit, it dumps core. I pulled the core into gdb and it says: 
> > 
> > Core was generated by `/opt/integrit/sbin/integrit -C /opt/integrit/conf/integrit.conf'.
> > Program terminated with signal 11, Segmentation Fault.
> > #0  0x8073d8a in ?? ()
> 
> For production, the build process strips debugging information out of
> the integrit binary.  GDB might be able to tell us more if integrit is
> configured with debugging turned on:
> 
>   ./configure --enable-debug=yes
> 
> > I get the same results if I issue integrit -V
> 
> That's a good sign, believe it or not, since it means that it's
> probably something simple.
> 
> > Anybody had success on intel-solaris?  
> 
> -- 
> --Ed Cashin                   PGP public key:
>   ec...@te...       http://www.terry.uga.edu/~ecashin/pgp/
> 
> 
> _______________________________________________
> Integrit-users mailing list
> Int...@li...
> https://lists.sourceforge.net/lists/listinfo/integrit-users

-- 
*****
Wes Byne                    
Water Research and Consumption
fb...@en...          (voice):706-542-6041  
http://watershed.engr.uga.edu
*****

Re: [Integrit-users] intel solaris core dump

[Ed L C. <ec...@te...>]

Wes Byne <fb...@en...> writes:

> hello,
> 
> I installed integrit 2.03 on solaris intel tonight, but when I try to execute integrit, it dumps core. I pulled the core into gdb and it says: 
> 
> Core was generated by `/opt/integrit/sbin/integrit -C /opt/integrit/conf/integrit.conf'.
> Program terminated with signal 11, Segmentation Fault.
> #0  0x8073d8a in ?? ()

For production, the build process strips debugging information out of
the integrit binary.  GDB might be able to tell us more if integrit is
configured with debugging turned on:

  ./configure --enable-debug=yes

> I get the same results if I issue integrit -V

That's a good sign, believe it or not, since it means that it's
probably something simple.

> Anybody had success on intel-solaris?  

-- 
--Ed Cashin                   PGP public key:
  ec...@te...       http://www.terry.uga.edu/~ecashin/pgp/

[Integrit-users] intel solaris core dump

[Wes B. <fb...@en...>]

hello,

I installed integrit 2.03 on solaris intel tonight, but when I try to execute integrit, it dumps core. I pulled the core into gdb and it says: 

Core was generated by `/opt/integrit/sbin/integrit -C /opt/integrit/conf/integrit.conf'.
Program terminated with signal 11, Segmentation Fault.
#0  0x8073d8a in ?? ()

I get the same results if I issue integrit -V

Anybody had success on intel-solaris?  

-Wes

-- 
*****
Wes Byne                    
Water Research and Consumption
fb...@en...          (voice):706-542-6041  
http://watershed.engr.uga.edu
*****

Re: [Integrit-users] [Andrew Gierth <andrew@erlenstar.demon.co.uk>] Re: exit code conventions/standards

[Ed L C. <ec...@te...>]

RD...@ga... (Mr. Ross Druker) writes:

> On Oct 27,  9:35pm, Ed L Cashin wrote:
> > Subject: Re: [Integrit-users] [Andrew Gierth <an...@er...
> > "Gary E. Miller" <ge...@re...> writes:
> >
> > > Yo Ed!
> > >
> > > Uh, that makes 2.  Me and him. :-)
> >
> > Of course!  My mistake.  :)
>
> Well, I'm no guru, but since I started this thread, please count me
> as 3.  :-)

OK, even though you claim not to be a guru, I will count you as a
third guru.

Yes, I agree now.  Many tools that are comparative in nature use the
exit status to indicate simple yes/no information.  Thanks to the
advocates of this change for the helpful discussion.

I just heard of a situation (IRIX 6.5 with automounter) where an
assumption in the file tree walking code doesn't hold, so I'm going to
look into that, and then maybe a new release will come out that uses
the exit code to indicate whether differences have been encountered.

The new release will be version three, a change in the major version
number, to indicate that an incompatible change has occured.  (The new
exit status behavior will break some old scripts.)

-- 
--Ed Cashin                   PGP public key:
  ec...@te...       http://www.terry.uga.edu/~ecashin/pgp/

Re: [Integrit-users] [Andrew Gierth <andrew@erlenstar.demon.co.uk>] Re: exit code conventions/standards

[<RD...@ga...>]

On Oct 27,  9:35pm, Ed L Cashin wrote:
> Subject: Re: [Integrit-users] [Andrew Gierth <an...@er...
> "Gary E. Miller" <ge...@re...> writes:
>
> > Yo Ed!
> >
> > Uh, that makes 2.  Me and him. :-)
>
> Of course!  My mistake.  :)

Well, I'm no guru, but since I started this thread, please count me as 3.  :-)

But anyway, is it something you're going to consider, since it appears it may
fall within the realm of accepted conventions or standards?

-- 
Ross Druker                                      Rohm and Haas Co.
RD...@Ro...                             Philadelphia, PA
(215) 592-3281
The opinions expressed are mine and not those of Rohm and Haas Company.

Re: [Integrit-users] [Andrew Gierth <andrew@erlenstar.demon.co.uk>] Re: exit code conventions/standards

[Ed L C. <ec...@te...>]

"Gary E. Miller" <ge...@re...> writes:

> Yo Ed!
>
> Uh, that makes 2.  Me and him. :-)

Of course!  My mistake.  :)

-- 
--Ed Cashin                   PGP public key:
  ec...@te...       http://www.terry.uga.edu/~ecashin/pgp/

Re: [Integrit-users] [Andrew Gierth <andrew@erlenstar.demon.co.uk>] Re: exit code conventions/standards

[Gary E. M. <ge...@re...>]

Yo Ed!

Uh, that makes 2.  Me and him. :-)


RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 20340 Empire Blvd, Suite E-3, Bend, OR 97701
	ge...@re...  Tel:+1(541)382-8588 Fax: +1(541)382-8676

On 27 Oct 2001, Ed L Cashin wrote:

> One guru votes for using the exit code to indicate difference!
>
>

Re: [Integrit-users] Configure and make worked on Win2K box with Cygwin loaded.

[Ed L C. <ec...@te...>]

"Rodney Lancaster" <rla...@ve...> writes:

> Ed, I did some checking and I think it has to do with the special nature
> of any file that starts with the "aux." for Windows.  I actually created
> the file 'aux.mak.in' but it would not list or show up.  When I deleted
> it I had to overwrite the fact that it was created with "write
> protections".  I checked this by using Windows tools only, outside of
> cygwin.
> 
> Just to check things out I did the following:
> 
> Changed all references in configure, configure.in, config.status,
> utils/Makefile.in, utils/Makefile and (after retrieving the file
> aux.mak.in on a Solaris box) renamed aux.mak.in to utils.mak.in.
> 
> Compile went cleanly.  I hope I did not overstep my bounds.  It's not
> like there were a lot of places to change.

On the contrary, that's a great help.  I wondered if that would be
necessary, but I guessed incorrectly.  I'll change "aux.*" to
"utils.*".

-- 
--Ed Cashin                   PGP public key:
  ec...@te...       http://www.terry.uga.edu/~ecashin/pgp/

RE: [Integrit-users] Configure and make worked on Win2K box with Cygwin loaded.

[Rodney L. <rla...@ve...>]

Ed, I did some checking and I think it has to do with the special nature
of any file that starts with the "aux." for Windows.  I actually created
the file 'aux.mak.in' but it would not list or show up.  When I deleted
it I had to overwrite the fact that it was created with "write
protections".  I checked this by using Windows tools only, outside of
cygwin.

Just to check things out I did the following:

Changed all references in configure, configure.in, config.status,
utils/Makefile.in, utils/Makefile and (after retrieving the file
aux.mak.in on a Solaris box) renamed aux.mak.in to utils.mak.in.

Compile went cleanly.  I hope I did not overstep my bounds.  It's not
like there were a lot of places to change.

Regards

Rodney Lancaster=20
"I want to know God's thoughts. . . The rest are details" Albert
Einstein


Ed Cashin wrote:

> Subject: Re: [Integrit-users] Configure and make worked on Win2K box
with > Cygwin loaded.

> "Rodney Lancaster" writes:

>> A configure and make was run on a Win2k box with Cygwin loaded using
the
>>=20
>> release-2_04_00-beta release tag.
>>=20
>> I ran the configure with only one complaint (after I got all the
files
>> down,=20
>> duh):
>>=20
>>     sed: can't read ./utils/aux.mak.in: Permission denied

> That is kind of weird.  Maybe you could ask some Cygwin users/experts
> why that might happen.

>> Is this required, did I forget to get something, or can I proceed to
>> test=20
>> away?

> The worst that can happen is that the auxiliary tools won't build.
> Just don't "make aux", and it's a non-issue.

>> On the UNIX side I am going to proceed in setting up and testing a
>> Solaris 8=20
>> for x86 box I have and also a Solaris 7 sparc server.

> That should work nicely.  I work on Solaris sometimes, and a while
> back several Solaris hurdles were jumped.

>> Thanks for all your work.

> I really appreciate that!  :) =20

Re: [Integrit-users] exit status

[Ed L C. <ec...@te...>]

"Gary E. Miller" <ge...@re...> writes:

> Yo Ed!
> 
> On 26 Oct 2001, Ed L Cashin wrote:
> 
> > integrit was written in C after the ANSI standard came out.  There are
> > only two defined exit statuses for a C program: zero, EXIT_SUCCESS,
> > and EXIT_FAILURE.  The tools you refer to were developed before the
> > ANSI standard.  They are "grandfathered in".  New programs, however,
> > must respect the conventions of the world we live in now.
> 
> I agree on standards, I disagree that a file mismatch is not a FAILURE.
> It is a failure in that my file system has changed.

Of course that's not a runtime failure.  When a tool successfully does
what you ask it to do, nothing failed.

> > Anyway, analogies like this are not helpful.  gnapster always exits
> > with 1 for no good reason.  That doesn't mean integrit should.
> 
> Gnapster is not part of POSIX, diff and cmp are POSIX standard.  If
> we are talking standards then let us stay with standards.
> 
> As long as we are on standards, how about the GNU standards:
> 
> http://www.gnu.org/manual/glibc-2.2.3/html_node/libc_547.html
> 
> "There are conventions for what sorts of status values certain programs
> should return. The most common convention is simply 0 for success
> and 1 for failure. Programs that perform comparison use a different
> convention: they use status 1 to indicate a mismatch, and status 2 to
> indicate an inability to compare. Your program should follow an existing
> convention if an existing convention makes sense for it."
> 
> Nothing about "grandfathering" in there.

That is a much stronger argument.  Thank you for pointing that out --
I looked for it but couldn't find it.  

> Now we just need to decide whether this "makes sense".  I think
> it does make sense to return 1 on a changes a 2 on an error.  That
> way I can sort my morning reports from CRITICAL (intergit failed),
> to WARNING (integrit found something) and OK (no changes or errors).

Hold on, now.  You can already do that.  Just use "-q" and "-c", and
you know that if integrit generates any output, there were changes.

Let's not forget that we are considering adding an unnecessary feature
to integrit.  That is a big deal, since now that integrit is mature,
one of the most important issues is staying away from feature bloat.

In light of the convention for comparative software, the idea doesn't
seem as bad as I thought.  I think I'll ask the folks in
comp.unix.programmer.  There are some gurus there that should serve as
a good resource.

-- 
--Ed Cashin                   PGP public key:
  ec...@te...       http://www.terry.uga.edu/~ecashin/pgp/

Re: [Integrit-users] exit status

[Gary E. M. <ge...@re...>]

Yo Ed!

On 26 Oct 2001, Ed L Cashin wrote:

> integrit was written in C after the ANSI standard came out.  There are
> only two defined exit statuses for a C program: zero, EXIT_SUCCESS,
> and EXIT_FAILURE.  The tools you refer to were developed before the
> ANSI standard.  They are "grandfathered in".  New programs, however,
> must respect the conventions of the world we live in now.

I agree on standards, I disagree that a file mismatch is not a FAILURE.
It is a failure in that my file system has changed.


> Anyway, analogies like this are not helpful.  gnapster always exits
> with 1 for no good reason.  That doesn't mean integrit should.

Gnapster is not part of POSIX, diff and cmp are POSIX standard.  If
we are talking standards then let us stay with standards.

As long as we are on standards, how about the GNU standards:

http://www.gnu.org/manual/glibc-2.2.3/html_node/libc_547.html

"There are conventions for what sorts of status values certain programs
should return. The most common convention is simply 0 for success
and 1 for failure. Programs that perform comparison use a different
convention: they use status 1 to indicate a mismatch, and status 2 to
indicate an inability to compare. Your program should follow an existing
convention if an existing convention makes sense for it."

Nothing about "grandfathering" in there.

Now we just need to decide whether this "makes sense".  I think
it does make sense to return 1 on a changes a 2 on an error.  That
way I can sort my morning reports from CRITICAL (intergit failed),
to WARNING (integrit found something) and OK (no changes or errors).

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 20340 Empire Blvd, Suite E-3, Bend, OR 97701
	ge...@re...  Tel:+1(541)382-8588 Fax: +1(541)382-8676
> Standards conformance is a better guideline.

Re: [Integrit-users] Configure and make worked on Win2K box with Cygwin loaded.

[Ed L C. <ec...@te...>]

"Rodney Lancaster" <rla...@ve...> writes:

> A configure and make was run on a Win2k box with Cygwin loaded using the
> 
> release-2_04_00-beta release tag.
> 
> I ran the configure with only one complaint (after I got all the files
> down, 
> duh):
> 
>     sed: can't read ./utils/aux.mak.in: Permission denied

That is kind of weird.  Maybe you could ask some Cygwin users/experts
why that might happen.

> Is this required, did I forget to get something, or can I proceed to
> test 
> away?

The worst that can happen is that the auxiliary tools won't build.
Just don't "make aux", and it's a non-issue.

> On the UNIX side I am going to proceed in setting up and testing a
> Solaris 8 
> for x86 box I have and also a Solaris 7 sparc server.

That should work nicely.  I work on Solaris sometimes, and a while
back several Solaris hurdles were jumped.

> Thanks for all your work.

I really appreciate that!  :)  

-- 
--Ed Cashin                   PGP public key:
  ec...@te...       http://www.terry.uga.edu/~ecashin/pgp/

Re: [Integrit-users] exit status

[Ed L C. <ec...@te...>]

"Gary E. Miller" <ge...@re...> writes:

> Yo Ed!

Yo!

> On 26 Oct 2001, Ed L Cashin wrote:
> 
> > Non-zero exit status is only for error conditions.  Errors are
> > problems that prevent the software in question from doing its job and
> > that cannot be overcome by the software itself.
> 
> Not true, This is NOT the UNIX way.  I suggest you check out the
> man pages for "diff", "cmp", etc...
>
> Diff:
>        An exit status of 0 means no  differences  were  found,  1
>        means some differences were found, and 2 means trouble.
>
> cmp:
>      The cmp utility exits with one of the following values:
> 
>      0     The files are identical.
> 
>      1     The files are different; this includes the case where one file is
>            identical to the first part of the other.  In the latter case, if
>            the -s option has not been specified, cmp writes to standard output
>            that EOF was reached in the shorter file (before any differences
>            were found).
> 
>      >1    An error occurred.
> 
> By analogy, integrit should return 0 on success, 1 on difference and 2
> on an error.

From stdlib.h:


  /* We define these the same for all machines.
     Changes from this to the outside world should be done in `_exit'.  */
  #define	EXIT_FAILURE	1	/* Failing exit status.  */
  #define	EXIT_SUCCESS	0	/* Successful exit status.  */
  

integrit was written in C after the ANSI standard came out.  There are
only two defined exit statuses for a C program: zero, EXIT_SUCCESS,
and EXIT_FAILURE.  The tools you refer to were developed before the
ANSI standard.  They are "grandfathered in".  New programs, however,
must respect the conventions of the world we live in now.

Anyway, analogies like this are not helpful.  gnapster always exits
with 1 for no good reason.  That doesn't mean integrit should.
Standards conformance is a better guideline.

-- 
--Ed Cashin                   PGP public key:
  ec...@te...       http://www.terry.uga.edu/~ecashin/pgp/

[Integrit-users] Configure and make worked on Win2K box with Cygwin loaded.

[Rodney L. <rla...@ve...>]

A configure and make was run on a Win2k box with Cygwin loaded using the

release-2_04_00-beta release tag.

I ran the configure with only one complaint (after I got all the files
down,=20
duh):

    sed: can't read ./utils/aux.mak.in: Permission denied

Is this required, did I forget to get something, or can I proceed to
test=20
away?

On the UNIX side I am going to proceed in setting up and testing a
Solaris 8=20
for x86 box I have and also a Solaris 7 sparc server.

Thanks for all your work.
Regards

Rodney V. Lancaster

Re: [Integrit-users] exit status

[Gary E. M. <ge...@re...>]

Yo Ed!

On 26 Oct 2001, Ed L Cashin wrote:

> Non-zero exit status is only for error conditions.  Errors are
> problems that prevent the software in question from doing its job and
> that cannot be overcome by the software itself.

Not true, This is NOT the UNIX way.  I suggest you check out the
man pages for "diff", "cmp", etc...

Diff:
       An exit status of 0 means no  differences  were  found,  1
       means some differences were found, and 2 means trouble.

cmp:
     The cmp utility exits with one of the following values:

     0     The files are identical.

     1     The files are different; this includes the case where one file is
           identical to the first part of the other.  In the latter case, if
           the -s option has not been specified, cmp writes to standard output
           that EOF was reached in the shorter file (before any differences
           were found).

     >1    An error occurred.

By analogy, integrit should return 0 on success, 1 on difference and 2
on an error.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 20340 Empire Blvd, Suite E-3, Bend, OR 97701
	ge...@re...  Tel:+1(541)382-8588 Fax: +1(541)382-8676

Re: [Integrit-users] exit status

[Ed L C. <ec...@te...>]

RD...@ga... (Mr. Ross Druker) writes:

> Hmm.  I suppose it's a difference in philosophy.  TripWire, for example (at
> least the free version), returns several exit statuses:
> 
> 1=error, 2=files added, 4=files deleted, and 8=files changed.  This can be OR'd
> together.  E.g., 10=codes 8 and 2.
> 
> Another freeware integrity checker I was looking at, fcheck, uses 1 for
> software errors (e.g., can't find config file), and 2 for database
> inconsistencies.
> 
> I guess I'd put it down as something I'd like to see, but maybe others don't.

Some programs break with convention and overload the exit status even
when there is no error.  Sometimes it's because the developers are not
aware of the convention, and other times it's a deliberate choice.  I
suppose that in the case of tripwire, it was a deliberate choice, and
in that case it certainly is a difference in philosophy.  

Simplicity and consistency go hand in hand.  Feature bloat tugs at the
developer to violate or extend standards.  Integrit was created in
reaction to integrity-verification software that was burdened by an
explosion of features.  It is in keeping with integrit's simplicity to
be consistent with the exit status behavior that (experienced) users
expect instead of adding another feature that provides no new
information (the information is already in the report).  It is in
keeping with tripwire's abundance of features and steep learning curve
that there would be such a complex overloading of exit codes.

-- 
--Ed Cashin                   PGP public key:
  ec...@te...       http://www.terry.uga.edu/~ecashin/pgp/

Re: [Integrit-users] exit status

[<RD...@ga...>]

Hmm.  I suppose it's a difference in philosophy.  TripWire, for example (at
least the free version), returns several exit statuses:

1=error, 2=files added, 4=files deleted, and 8=files changed.  This can be OR'd
together.  E.g., 10=codes 8 and 2.

Another freeware integrity checker I was looking at, fcheck, uses 1 for
software errors (e.g., can't find config file), and 2 for database
inconsistencies.

I guess I'd put it down as something I'd like to see, but maybe others don't.

Ross


On Oct 26, 11:02am, Ed L Cashin wrote:
> Subject: Re: [Integrit-users] exit status
> RD...@ga... (Mr. Ross Druker) writes:
>
> > It appears that integrit exits with a status of 0 when it finds a
discrepancy
> > between the known and current db's.
> >
> > Would it be a problem to change it to a non-zero value to make it easier to
> > flag the change?
>
> Non-zero exit status is only for error conditions.  Errors are
> problems that prevent the software in question from doing its job and
> that cannot be overcome by the software itself.  For example, if you
> invoke integrit and tell it to do a check but you don't say where the
> configuration file is, then integrit can't do its job, and it can't
> solve the problem itself, so it uses an exit status of EXIT_FAILURE
> (defined in stdlib.h) to indicate the error condition.  Then the user
> knows that integrit wasn't able to do what they wanted.
>
> When integrit finds that files have changed, it's just doing its job,
> and when it finishes successfully, after finding changes, it uses
> EXIT_SUCCESS to let the user know that it was able to do what the user
> asked it to: detect any changes.  Integrit only uses an EXIT_FAILURE
> to indicate that it could not do its job.
>
> So it would be a problem for integrit to use a non-zero value when no
> error existed, since it would incorrectly suggest that integrit had
> failed for some reason.
>
> It is possible to use the -q switch, and that way if you get any
> output at all (or more than two lines of output if you're also doing
> an update) you know that something has changed.  For example, you can
> send the report to a file on a remote host; then on the remote host,
> you can do:
>
>   if [ "`wc -l $filename | awk '{ print $1 }'`" -gt 0 ]; then
>     (printf "To: sys...@my...\nSubject: fs changes\n\n"
>      cat $filename) | /usr/lib/sendmail -t
>   fi
>
> ... or something so that you only get mail if there's been a change.
> It isn't as safe to do that on the host you're checking.
>
> --
> --Ed Cashin                   PGP public key:
>   ec...@te...       http://www.terry.uga.edu/~ecashin/pgp/
>-- End of excerpt from Ed L Cashin



-- 
Ross Druker                                      Rohm and Haas Co.
RD...@Ro...                             Philadelphia, PA
(215) 592-3281
The opinions expressed are mine and not those of Rohm and Haas Company.

Re: [Integrit-users] exit status

[Ed L C. <ec...@te...>]

RD...@ga... (Mr. Ross Druker) writes:

> It appears that integrit exits with a status of 0 when it finds a discrepancy
> between the known and current db's.
> 
> Would it be a problem to change it to a non-zero value to make it easier to
> flag the change?

Non-zero exit status is only for error conditions.  Errors are
problems that prevent the software in question from doing its job and
that cannot be overcome by the software itself.  For example, if you
invoke integrit and tell it to do a check but you don't say where the
configuration file is, then integrit can't do its job, and it can't
solve the problem itself, so it uses an exit status of EXIT_FAILURE
(defined in stdlib.h) to indicate the error condition.  Then the user
knows that integrit wasn't able to do what they wanted.

When integrit finds that files have changed, it's just doing its job,
and when it finishes successfully, after finding changes, it uses
EXIT_SUCCESS to let the user know that it was able to do what the user
asked it to: detect any changes.  Integrit only uses an EXIT_FAILURE
to indicate that it could not do its job.

So it would be a problem for integrit to use a non-zero value when no
error existed, since it would incorrectly suggest that integrit had
failed for some reason.  

It is possible to use the -q switch, and that way if you get any
output at all (or more than two lines of output if you're also doing
an update) you know that something has changed.  For example, you can
send the report to a file on a remote host; then on the remote host,
you can do:

  if [ "`wc -l $filename | awk '{ print $1 }'`" -gt 0 ]; then 
    (printf "To: sys...@my...\nSubject: fs changes\n\n"
     cat $filename) | /usr/lib/sendmail -t
  fi

... or something so that you only get mail if there's been a change.
It isn't as safe to do that on the host you're checking.

-- 
--Ed Cashin                   PGP public key:
  ec...@te...       http://www.terry.uga.edu/~ecashin/pgp/

[Integrit-users] exit status

[<RD...@ga...>]

It appears that integrit exits with a status of 0 when it finds a discrepancy
between the known and current db's.

Would it be a problem to change it to a non-zero value to make it easier to
flag the change?

Ross

-- 
Ross Druker                                      Rohm and Haas Co.
RD...@Ro...                             Philadelphia, PA
(215) 592-3281
The opinions expressed are mine and not those of Rohm and Haas Company.

[Integrit-users] CVS version without aux

[Ed L C. <ec...@te...>]

Hi, folks.  If anyone was waiting on an "aux"-less version of
integrit, the pre-2.04 version that's now in CVS is it.  :)

Here's a link to the sourceforge page that has instructions for doing
anonymous CVS: 

  http://sourceforge.net/cvs/?group_id=15369

Thanks to all who helped point out the "aux" thing.

-- 
--Ed Cashin                   PGP public key:
  ec...@te...       http://www.terry.uga.edu/~ecashin/pgp/

[Integrit-users] Re: Windows 2K port?

[Rodney L. <rla...@ve...>]

The directory name "auxiliary" should work fine.  I agree, it is a shame
to have to baby-sit Windows.

Rodney V. Lancaster

Re: [Integrit-users] Windows 2K port?

[Ed L C. <ec...@te...>]

"Cott Lang" <co...@in...> writes:

> AUX is a device, like under DOS.  You can't create files or directories
> named that AFAIK.

Sigh.  I thought that W2k was supposed to be based on NT, meaning that
it would not be shackled by these anachronistic DOS-isms.  "aux" isn't
even "AUX", if you're paying attention to case, which I would hope NT
had learned to do.  

Anyway, I will try to look into this and will consider changing the
name of the "aux" directory, although it hurts me to have to babysit
Windows when "aux" is a perfectly good name.

Maybe I should change the name to "NUL" or "PRN".  ;)

-- 
--Ed Cashin                   PGP public key:
  ec...@te...       http://www.terry.uga.edu/~ecashin/pgp/

Re: [Integrit-users] Windows 2K port?

[Cott L. <co...@in...>]

AUX is a device, like under DOS.  You can't create files or directories
named that AFAIK.


----- Original Message -----
From: "Ed L Cashin" <ec...@te...>
To: "Cott Lang" <co...@in...>
Cc: <int...@li...>
Sent: Tuesday, October 16, 2001 9:32 AM
Subject: Re: [Integrit-users] Windows 2K port?


> "Cott Lang" <co...@in...> writes:
>
> > :o = "urn:schemas-microsoft-com:office:office" xmlns:w =
> > "urn:schemas-microsoft-com:office:word">
> > AUX is a device. :)
>
> OK, it sounds like Rodney Lancaster is suggesting that the problem is
> that in Windows 2000, it is impossible for the user to create a
> directory called "aux".  (BTW, thanks, Rodney for sending the report.)
>
> You're saying that AUX is a device.  Do you mean like in DOS, where
> AUX is some port?  I'm going to take Rodney's advice and try to create
> a directory named "aux" the next time I'm near a Windows 2000 box.
>
> --
> --Ed Cashin                   PGP public key:
>   ec...@te...       http://www.terry.uga.edu/~ecashin/pgp/
>
>
> _______________________________________________
> Integrit-users mailing list
> Int...@li...
> https://lists.sourceforge.net/lists/listinfo/integrit-users
>

Re: [Integrit-users] Windows 2K port?

[Ed L C. <ec...@te...>]

"Cott Lang" <co...@in...> writes:

> :o = "urn:schemas-microsoft-com:office:office" xmlns:w =
> "urn:schemas-microsoft-com:office:word">
> AUX is a device. :)

OK, it sounds like Rodney Lancaster is suggesting that the problem is
that in Windows 2000, it is impossible for the user to create a
directory called "aux".  (BTW, thanks, Rodney for sending the report.) 

You're saying that AUX is a device.  Do you mean like in DOS, where
AUX is some port?  I'm going to take Rodney's advice and try to create
a directory named "aux" the next time I'm near a Windows 2000 box.

-- 
--Ed Cashin                   PGP public key:
  ec...@te...       http://www.terry.uga.edu/~ecashin/pgp/

[Integrit-users] Windows 2K port?

[Rodney L. <rla...@ve...>]

My first try was not in text format.  Her we go again.

I have done a quick attempt to see if Integrit will work on Win2000
using Cygwin to give me the GNU compiler and POSIX compliance.
Surprisingly the only problem (which is a show stopper) has nothing to
do with Integrit or Cygwin.  The problem is that MS has a "special" file
called "aux" in every directory that does not show up even when you ask
for Hidden and System files.  Just try to create a directory on a Win2K
box named "aux".  Extracting the the files from the tar file fails when
it hits the creation of the directory "aux". I get the message "A file
with the name specified already exists.  Specify a different filename. I
tried this on 3 different machines running win2k.  2 without cygwin
loaded and using WinZip to extract.  The same error occurs.=20

The place I work would not mind me using Integrit if there can be a port
for Win2K (ugh).  We are primarily a Solaris and Windows Shop.

Would it be too hard to rename the "aux" directory to "auxiliary" or
something else?  If not I'll be glad to go through the code and make the
changes to check it out.  It would be interesting to have a GPL
integrity checker that at least partway works on a Win2K environment.
(Oh, I can't believe I am saying this).

I again apologize for the first message not being in 'text' form.

Rodney V. Lancaster