On 20/11/2020 2:19 pm pokeswithastick said...

Hm, that sounds like something else most likely. If you see
that again and can capture logs I can take a look.

Sure will do

Ok it happened again and I've submitted a bug report on github #329. Seems to give up unzipping a .ZIP file

--- ENiGMA 1/2 v0.0.12-beta (linux; arm; 12.19.0)
* Origin: sbb systems ~ https://bbs.sbbsystems.com (21:2/159)

On 06/12/2020 7:00 am NuSkooler said...

Just a warning on 7zip: Some builds result in "volume not found" errors when processing zip files.

Ah yes I read that in the change log

--- ENiGMA 1/2 v0.0.12-beta (linux; arm; 12.19.0)
* Origin: sbb systems ~ https://bbs.sbbsystems.com (21:2/159)

On 26/11/2020 9:16 am pokeswithastick said...

Ok it happened again and I've submitted a bug report on github #329. Seems to give up unzipping a .ZIP file

Interestingly the unzip command PID doesn't have any arguments listed in /proc/(pid)/cmdline.

I've overriden to the config to try and make enigma use 7zip for zip archives and I'll see what that does. Otherwise I'll write a shell script wrapper around unzip to try and capture inputs and outputs and see where it stops (presumably waiting for input as you said)

--- ENiGMA 1/2 v0.0.12-beta (linux; arm; 12.19.0)
* Origin: sbb systems ~ https://bbs.sbbsystems.com (21:2/159)

On Thursday, December 3rd pokeswithastick said...

Interestingly the unzip command PID doesn't have any arguments listed in /proc/(pid)/cmdline.

If you really want (and maybe I should just push a change for trace level logging) archivers.js could just log the thing.

I'm not clear how we'd end up without parameters though -- unless unzip is clearing them (which in Linux you can certainly do).



--

NuSkooler
Xibalba BBS @ xibalba.l33t.codes / 44510(telnet) 44511(ssh)
ENiGMA 1/2 BBS WHQ | Phenom | 67 | iMPURE | ACiDic

--- ENiGMA 1/2 v0.0.12-beta (linux; x64; 12.13.1)
* Origin: Xibalba -+- xibalba.l33t.codes:44510 (21:1/121)

On 03/12/2020 6:51 am NuSkooler said...

If you really want (and maybe I should just push a change for trace level logging) archivers.js could just log the thing.

Thanks but I can probably patch the code locally if I need to. So far though it has been ok with using 7Zip. I think you are probably right that unzip is waiting for user input for some reason. I wonder if because I have 2 containers (binkd & enigma) sharing a mail directory (local fs mounted into each container) that this causes some conflict like the files being partially written by binkd but immediately visible to enigma so the import routine runs but on locked/corrupted files.

If it happens with 7Zip I'll investigate more.

--- ENiGMA 1/2 v0.0.12-beta (linux; arm; 12.19.0)
* Origin: sbb systems ~ https://bbs.sbbsystems.com (21:2/159)

Twas Sunday, December 6th when pokeswithastick said...

If it happens with 7Zip I'll investigate more.

Just a warning on 7zip: Some builds result in "volume not found" errors when processing zip files.



--

NuSkooler
Xibalba BBS @ xibalba.l33t.codes / 44510(telnet) 44511(ssh)
ENiGMA 1/2 BBS WHQ | Phenom | 67 | iMPURE | ACiDic

--- ENiGMA 1/2 v0.0.12-beta (linux; x64; 12.13.1)
* Origin: Xibalba -+- xibalba.l33t.codes:44510 (21:1/121)