Package Details: pgl 2.3.1-1

Git Clone URL: https://aur.archlinux.org/pgl.git (read-only)
Package Base: pgl
Description: A privacy oriented firewall application (GUI).
Upstream URL: http://sourceforge.net/projects/peerguardian/
Licenses: GPL3
Conflicts: pgl-cli, pgl-git
Submitter: Gilrain
Maintainer: Gilrain
Last Packager: Gilrain
Votes: 36
Popularity: 0.000012
First Submitted: 2011-08-25 13:05
Last Updated: 2016-01-14 14:40

Required by (0)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

willemw commented on 2014-06-16 13:57

> My preference would be to ship with Requisite and let the users add a Requires if they need/wish it.

How will people know they need/wish this?

Why the softer directive?
Say I reboot once everyday and at reboot pgl-update starts before the network is ready, then pgl will never get updated.

jre commented on 2014-06-16 13:46

I fully agree to use "Requisite".

I added you (gilrain) to the pgl project at sourceforge. So you can add this directly to the master branch (or any other if you want to) of the git repository).

If you don't do it, I will do it sometime/soon.

Gilrain commented on 2014-06-16 13:20

> you can implement something like "Requires: network" in pgl-update.service, so that the update only happens when the local network is up.

The «Requires» directive would automatically initiate a full network connection,
whereas the softer «Requisite» only starts the service if the network is already up.
My preference would be to ship with Requisite and let the users add a Requires if they need/wish it.

jre commented on 2014-06-16 11:02

That is/was correct and normal pgl behavior: whenever pgl is not available to retrieve the site defined in TESTHOST (whether the local network is down or the remote site is down doesn't matter) it will emit error 171.

I had no look in the new systemd pgl[-update].service, yet (but I will, soon, especially since my system Debian now also moves there). But probably you can implement something like "Requires: network" in pgl-update.service, so that the update only happens when the local network is up.

Are there any experiences with the systemd stuff and pglgui, yet?
- I strongly assume the Start and Upgrade stuff in the pglgui Configure tab don't work.
- What about manually stopping pgl in pglgui after it was started automatically by systemd --> does the system restart pgl automatically, because it thinks pgl crashed?

Keep on your good work!

willemw commented on 2014-06-16 10:45

pgl-update fails if there is no network (status=171/n/a; E_NETWORK_DOWN="171").

Gilrain commented on 2014-06-07 09:15

Now that Arch migrated to systemd timer, I thought it was time to make the jump with pgl:

Cron is no longer a dependency, the pgl-update timer being enabled when pgl.service is itself enabled.
Upgrading requires reenabling pgl.service to load the timer and a system reboot or manually starting pgl-update.timer.

Gilrain commented on 2013-10-23 13:12

Don't worry about upgrading systemd, its package only touch the files it installed, not the ones added by other packages. /etc is used as a 2nd source of service files (copied, included or altere.d) to replace, complement or override properties found in the files distributed by packages in /usr.

In short, /usr is the standard base upon which a sysadmin might customize, in /etc, the behavior of a service to suit his needs (see <https://wiki.archlinux.org/index.php/Systemd#Editing_provided_unit_files> for further info and justifications).

msx commented on 2013-10-23 04:08

@Gilrain: I think that the service unit should be placed inside /etc/systemd/system instead /usr/lib/systemd/system as this last directory is trampled on every systemd update.
If I'm not mistaken the official place to put user's service units is in /etc/systemd/system as it also takes precedent over /usr/lib/systemd/system.

Cheers!

msx commented on 2013-07-13 04:20

Just stopping by to thank you for actively maintaining pgl, thanks to your work we can enjoy it in Chakra too.
Cheers.

Gilrain commented on 2013-06-13 07:14

* 2.2.2-7 :
definitely solves the initial blocklists download problem (TimeoutStartSec=0),
iptables and shorewall added to firewalls list.