> I have to admit I'm having a little difficulty chasing this one down, so
Of course I am not awake yet. "trailer" is the pointer that's
misaligned.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> Well, I see this in build logs on 64bit platforms:
> zziplib/zzip-io.c:65: warning: initialization from incompatible pointer type
There also appear to be unsigned char/signed char warnings.
> But oddly, it doesn't SIGBUS here (amd64) with those files.
I'd bet that amd64 isn't as picky about al
forwarded 322396 [EMAIL PROTECTED]
tags 322396 +upstream
thanks
This one time, at band camp, Clint Adams said:
> > I see now that you did, and my mailserver rejected it for being
> > Worm.Mydoom.M infected :( Sorry about that - I have grabbed the copy in
> > the BTS.
>
> Ha, I knew I should have
> I see now that you did, and my mailserver rejected it for being
> Worm.Mydoom.M infected :( Sorry about that - I have grabbed the copy in
> the BTS.
Ha, I knew I should have obfuscated it.
> One last thing, as I am not that familiar with Sun hardware - is yours
> sparc32 or sparc64?
sparc64.
This one time, at band camp, Clint Adams said:
> > Still, it would be helpful to have the tarball (or a link to it) in
> > order to do some debugging.
>
> I could have sworn that I sent it immediately after the mail missing the
> attachment.
I see now that you did, and my mailserver rejected it f
> Still, it would be helpful to have the tarball (or a link to it) in
> order to do some debugging.
I could have sworn that I sent it immediately after the mail missing the
attachment.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECT
This one time, at band camp, Clint Adams said:
> > Er, I see no tarball.
>
> It appears that it'll bus error on any .zip file.
Still, it would be helpful to have the tarball (or a link to it) in
order to do some debugging.
Thanks,
--
> Er, I see no tarball.
It appears that it'll bus error on any .zip file.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
This one time, at band camp, Clint Adams said:
> > Ah, I see, another zip file problem. There have been several reports of
> > this sort of thing. Do you by any chance have the zip file that caused
> > this? That would be very helpful for debugging.
>
> Attached is a tarball of a problematic me
Built -5 with 'noopt' and 'nostrip'; here is the backtrace.
#0 __zzip_find_disk_trailer (fd=9, filesize=29427, trailer=0xefc16eda,
io=0x70088748) at zziplib/zzip-zip.c:289
#1 0x70047048 in zzip_dir_fdopen_ext_io (fd=Variable "fd" is not available.
) at zziplib/zzip-zip.c:633
#2 0x7003ece8 in c
> Ah, I see, another zip file problem. There have been several reports of
> this sort of thing. Do you by any chance have the zip file that caused
> this? That would be very helpful for debugging.
Attached is a tarball of a problematic message and the corresponding
log.
The bus error would ind
> Ah, I see, another zip file problem. There have been several reports of
> this sort of thing. Do you by any chance have the zip file that caused
> this? That would be very helpful for debugging.
No, it got bounced. I've modified the script to save the files in the
event of an unexpected retu
This one time, at band camp, Clint Adams said:
> > So, it's been a few days. You should (hopefully) have at least a few
> > logfiles of the form log.$PID laying around from clamscan's that have
> > gone awry. If so, would you mind sending a few my way?
>
> I have no hung clamscan processes, and
> So, it's been a few days. You should (hopefully) have at least a few
> logfiles of the form log.$PID laying around from clamscan's that have
> gone awry. If so, would you mind sending a few my way?
I have no hung clamscan processes, and no log.$PID files.
I do have a clamscan core dump from 3
This one time, at band camp, Stephen Gran said:
> So, we're using it on the assumption that something will come along and
> kill it, yes. But it will be slightly different, and will need a more
> watchful eye to see which one is dead, as most mail will continue
> normally.
So, it's been a few day
This one time, at band camp, Clint Adams said:
> > Change this to "/usr/bin/clamscan --debug"
> >
> > Your load will go up for a while, but we'll get a chance to see what th
> > eproblem is. then send me the last several logs after a crash/lockup.
>
> Is clamscan supposed to choke and hang then?
> Change this to "/usr/bin/clamscan --debug"
>
> Your load will go up for a while, but we'll get a chance to see what th
> eproblem is. then send me the last several logs after a crash/lockup.
Is clamscan supposed to choke and hang then?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a su
This one time, at band camp, Clint Adams said:
> > some background information would be helpful:
> > I see you're running it on a sparc of some sort, can you supply
> > information about the environment clam is running in (RAM/CPU, etc)?
>
> 1G RAM, single UltraSparc IIi
Shouldn't be a resources
> some background information would be helpful:
> I see you're running it on a sparc of some sort, can you supply
> information about the environment clam is running in (RAM/CPU, etc)?
1G RAM, single UltraSparc IIi
> Can I see the config file for clamd? How are you calling clamd? I see
Attache
This one time, at band camp, Clint Adams said:
> > Log output, for a start. Then I would suggest running clamd for a while
> > the various debugging options (LogClean LogVerbose, etc) turned on, to
> > see if you can capture anyhting useful. finally of course, running an
> > unstripped copy under
> Log output, for a start. Then I would suggest running clamd for a while
> the various debugging options (LogClean LogVerbose, etc) turned on, to
> see if you can capture anyhting useful. finally of course, running an
> unstripped copy under gdb if nothing else works.
LogVerbose and LogClean on
> Log output, for a start. Then I would suggest running clamd for a while
> the various debugging options (LogClean LogVerbose, etc) turned on, to
> see if you can capture anyhting useful. finally of course, running an
> unstripped copy under gdb if nothing else works.
Here's clamav.log. The la
This one time, at band camp, Clint Adams said:
> Package: clamav-daemon
> Version: 0.86.2-1
>
> Since upgrading from 0.85.1-2, clamd has begun to choke; I discover a
> defunct clamd process and a backed-up mail queue.
>
> What information would be helpful?
Log output, for a start. Then I would
Package: clamav-daemon
Version: 0.86.2-1
Since upgrading from 0.85.1-2, clamd has begun to choke; I discover a
defunct clamd process and a backed-up mail queue.
What information would be helpful?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [E
24 matches
Mail list logo