User Activity

  • Posted a comment on ticket #341 on PeerGuardian

    Qt4 version works (Arch Linux AUR repository) so either Qt5 integration or something else is broken

  • Created ticket #341 on PeerGuardian

    Whitelisting is broken with pglgui (connection type missing etc.)

  • Modified a comment on ticket #337 on PeerGuardian

    Looks pretty much the same old issue that I have analyzed here: PGL not working on Arh/AntergOS Especially this part: PROBLEM 2 HERE: User can bug the "automatic updates" feature in GUI, leading to two existing pglcmd files, for example one in /etc/cron.daily/ folder and another one in /etc/cron.weekly/ folder. Better code logic to handle such situations is needed here.

  • Modified a comment on ticket #336 on PeerGuardian

    I guess this is the same issue I have talked about here: PGL not working on Arh/AntergOS

  • Posted a comment on ticket #336 on PeerGuardian

    I guess this is the same issue I have talked about here: PGL not working on Arh/AntergOS

  • Posted a comment on ticket #337 on PeerGuardian

    Looks pretty much the same old issue that I have analyzed here: PGL not working on Arh/AntergOS Especially this part: PROBLEM 2 HERE: User can bug the "automatic updates" feature in GUI, leading to two existing pglcmd files, for example one in /etc/cron.daily/ folder and another one in /etc/cron.weekly/ folder. Better code logic to handle such situations is needed here.

  • Modified a comment on discussion Help on PeerGuardian

    Yes, it is more an upstream issue of PeerGuardian's cron/automatic update implementation. Visible to user as strange error messages appearing whenever "Applying changes" by executing /tmp/execute-all-pgl-commands.sh If cron is not installed on the system, commands which are generated by PeerGuardian are 1 2 3 4 5#!/bin/sh set -e mv /tmp/pglcmd.conf /etc/pgl/pglcmd.conf mv <arg1> <arg2> /usr/bin/pglcmd reload Where <arg1> <arg2> are cron arguments (for example, mv /etc/cron.daily/pglcmd /etc/cron.weekly/pglcmd)....

  • Modified a comment on discussion Help on PeerGuardian

    Yes, it is more an upstream issue of PeerGuardian's cron/automatic update implementation. Visible to user as strange error messages appearing whenever "Applying changes" by executing /tmp/execute-all-pgl-commands.sh If cron is not installed on the system, commands which are generated by PeerGuardian are 1 2 3 4 5#!/bin/sh set -e mv /tmp/pglcmd.conf /etc/pgl/pglcmd.conf mv <arg1> <arg2> /usr/bin/pglcmd reload Where <arg1> <arg2> are cron arguments (for example, mv /etc/cron.daily/pglcmd /etc/cron.weekly/pglcmd)....

View All

Personal Data

Username:
fincer
Joined:
2017-12-20 00:19:51
Location:
Finland

Projects

  • No projects to display.

Personal Tools