Your message dated Wed, 19 Oct 2016 17:33:27 -0400
with message-id <[email protected]>
and subject line Re: Bug#801224: torsocks: [syscall] Unsupported syscall number
250
has caused the Debian Bug report #801224,
regarding torsocks: [syscall] Unsupported syscall number 250
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
801224: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801224
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: torsocks
Version: 2.1.0-1
Severity: normal
Running polularity-contest with torsocks gives a warning:
"""
torsocks /etc/cron.daily/popularity-contest --crond
[Oct 07 17:11:53] WARNING torsocks[5038]: [syscall] Unsupported syscall number
250. Denying the call (in tsocks_syscall() at syscall.c:465)
"""
This makes cronned polularity-contest submissions via (tosocks'ed)
HTTP rather noisy.
Thanks,
~Niels
--- End Message ---
--- Begin Message ---
intrigeri:
> Version: 2.1.0-2
> Hi,
> Niels Thykier wrote (23 Jun 2016 21:30:52 GMT) :
>> intrigeri:
>>> (I can't reproduce this here with torsocks 2.1.0-2 on sid.)
>> True, the particular system call seem to have been fixed.
> Cool :)
> Now, I see no relevant difference before 2.1.0-1 and 2.1.0-2, so
> I don't understand why this problem has disappeared in the meantime.
> Do you mind if I close this bug report anyway, until someone
> reproduces it again, maybe, some day?
Nobody reproduced this since then, so I'm closing this bug.
--- End Message ---
