Package Details: pacserve 2021-1

Git Clone URL: https://aur.archlinux.org/pacserve.git (read-only, click to copy)
Package Base: pacserve
Description: Easily share Pacman packages between computers. A replacement for PkgD.
Upstream URL: https://xyne.archlinux.ca/projects/pacserve
Keywords: arch_linux pacman server
Licenses: GPL
Conflicts: pacredir
Submitter: Xyne
Maintainer: Xyne
Last Packager: Xyne
Votes: 103
Popularity: 0.39
First Submitted: 2011-04-17 00:30
Last Updated: 2021-02-11 12:51

Latest Comments

« First ‹ Previous ... 5 6 7 8 9 10 11 12 13 Next › Last »

Xyne commented on 2013-03-25 18:17

@KerrickStaley
Run "systemctl status pacserve.service" on both systems and check for errors. If there are no errors then look for the messaging "adding: ... to server pool". If you don't see that then try restarting pacserve on each system, one at a time, and recheck the status each time on both systems to see if either detects the other. Each time pacserve starts it should send out a multicast query. After that it should send out multicast queries ever 5 minutes by default (or maybe 10, I don't remember right now).

That it still doesn't work, try manually querying each pacserve server locally and from the other system:

curl http://localhost:15678/search/core/x86_64/foo-1-1.pkg.tar.xz
curl http://10.42.0.1:15678/search/core/x86_64/foo-1-1.pkg.tar.xz
curl http://10.42.0.46:15678/search/core/x86_64/foo-1-1.pkg.tar.xz

It will print a list of the host aliases that it has queried. You should see both servers in the output.

I have had problems with ad-hoc wifi networks before. It may be a forwarding or firewall issue depending on your setup, but I'm grasping at straws here.

KerrickStaley commented on 2013-03-25 07:49

pacsrv doesn't seem to detect the pacserve instance running on my other computer. The two computers are directly connected via an ad-hoc WiFi network; the computer with the up-to-date pacman cache is acting as the "router" (its IP is 10.42.0.1) and the computer running pacsrv is acting as a "client" (IP 10.42.0.46). Both computers have the pacserve Systemd service running.

Xyne commented on 2012-12-04 20:04

I originally wrote the multicast code mostly as a learning experience. The current code works as intended and it is not complicated. I see no reason to add avahi and all of its dependencies just to remove about 30 lines of existing code.

eworm commented on 2012-12-04 06:46

Ok, just another idea. I have not taken a look at it yet, so I can not tell what complicated it is.

If I understand this correctly pacserve has its own multicast implementation. How about using avahi for that? You would not have to care about the open udp port, multicast interval and the like.

Xyne commented on 2012-11-27 23:06

@eworm
The service wasn't using /etc/conf.d/pacserved because I thought it would be easier to create a custom service file (in both cases the user would just be editing a text file in /etc).

I liked your suggestions and have implemented them with some modifications. The global configuration file is now /etc/conf.d/pacserve. It manages runtime options, netfilter rules and the PID file for all services and scripts.

I have also included /etc/pacman.d/pacserve and updated the pacsrv wrapper script to use that instead.

Thanks for making me aware of the systemd.exec options. ;)

eworm commented on 2012-11-26 08:27

The systemd unit file does not read the config file. You should replace

ExecStart=/usr/bin/pacserve --multicast

with

EnvironmentFile=/etc/conf.d/pacserved
ExecStart=/usr/bin/pacserve $PACSERVED_ARGS

eworm commented on 2012-11-26 08:27

The systemd unit file does not read the config file. You should replace

ExecStart=/usr/bin/pacserve --multicast

with

EnvironmentFile=/etc/conf.d/pacserved
ExecStart=/usr/bin/pacserve --multicast $PACSERVED_ARGS

eworm commented on 2012-11-25 14:57

You could install a file /etc/pacman.d/pacserve containing the "Server = ..." line and include that in every repository with "Include = ...".

Xyne commented on 2012-11-25 09:25

The package now contains a service named "pacserve-ports". When enabled, it should open and close the standard pacserve ports when the pacserve service is started or stopped, respectively.

Let me know if there are any issues.

olebowle commented on 2012-10-24 08:53

The .sig file is missing.