[13091] in bugtraq
Re: Groupewise Web Interface
daemon@ATHENA.MIT.EDU (Roy Sigurd Karlsbakk)
Fri Dec 24 13:21:42 1999
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01BF4D91.AF759BD0"
Message-Id: <51313828EB3CD211A49A006097AD457E0EA3CA@infosys.a-team.no>
Date: Thu, 23 Dec 1999 23:04:29 +0100
Reply-To: Randy Mclean <rmclean@NATDOOR.COM>
From: Roy Sigurd Karlsbakk <roy.karlsbakk@A-TEAM.NO>
X-To: Randy Mclean <rmclean@NATDOOR.COM>,
"BUGTRAQ@SECURITYFOCUS.COM" <BUGTRAQ@SECURITYFOCUS.COM>
To: BUGTRAQ@SECURITYFOCUS.COM
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01BF4D91.AF759BD0
Content-Type: text/plain;
charset="windows-1252"
> -----Original Message-----
> From: Randy Mclean
> To: BUGTRAQ@SECURITYFOCUS.COM
> Sent: 22.12.99 22:01
> Subject: Re: Groupewise Web Interface
>
> I just tested it on our server and when i did the "GWWEB.EXE?<very long
> string here>" The server console claimed it had a critical error. It
> seemed
> to work fine, but the server remained in status 1(with <1> by the server
> prompt).
The <1> means the system has been through <1> ABEND (Abnormal End). This is
generally a state that will require a reboot. A server saying <n> in the
command prompt (n can be any positive number indicating number of ABENDs),
is to be considered unstable.
> I didn't notice any problems with system or groupwise, even the
> web access still worked after the error. This dose seem like something
> that dose need to be fixed, but not as critical as something that
> actually causes a server to abend.
The <n> means a module has abended. Check SYS:System\Abend.log to find what
module really messed up.
Roy Sigurd Karlsbakk <roy@karlsbakk.net>
MCSE, MCNE, CLS, ASE
------_=_NextPart_001_01BF4D91.AF759BD0
Content-Type: text/html;
charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dwindows-1252">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2448.0">
<TITLE>RE: Groupewise Web Interface</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>> -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>> From: Randy Mclean</FONT>
<BR><FONT SIZE=3D2>> To: BUGTRAQ@SECURITYFOCUS.COM</FONT>
<BR><FONT SIZE=3D2>> Sent: 22.12.99 22:01</FONT>
<BR><FONT SIZE=3D2>> Subject: Re: Groupewise Web Interface</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> I just tested it on our server and when i did =
the "GWWEB.EXE?<very long</FONT>
<BR><FONT SIZE=3D2>> string here>" The server console =
claimed it had a critical error. It</FONT>
<BR><FONT SIZE=3D2>> seemed</FONT>
<BR><FONT SIZE=3D2>> to work fine, but the server remained in status =
1(with <1> by the server</FONT>
<BR><FONT SIZE=3D2>> prompt). </FONT>
</P>
<P><FONT SIZE=3D2>The <1> means the system has been through =
<1> ABEND (Abnormal End). This is generally a state that will =
require a reboot. A server saying <n> in the command prompt (n =
can be any positive number indicating number of ABENDs), is to be =
considered unstable.</FONT></P>
<P><FONT SIZE=3D2>> I didn't notice any problems with system or =
groupwise, even the</FONT>
<BR><FONT SIZE=3D2>> web access still worked after the error. This =
dose seem like something</FONT>
<BR><FONT SIZE=3D2>> that dose need to be fixed, but not as critical =
as something that </FONT>
<BR><FONT SIZE=3D2>> actually causes a server to abend. </FONT>
</P>
<P><FONT SIZE=3D2>The <n> means a module has abended. Check =
SYS:System\Abend.log to find what module really messed up.</FONT>
</P>
<P><FONT SIZE=3D2>Roy Sigurd Karlsbakk <roy@karlsbakk.net></FONT>
<BR><FONT SIZE=3D2>MCSE, MCNE, CLS, ASE</FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01BF4D91.AF759BD0--
