| View previous topic :: View next topic |
| Author |
Message |
melinux
n00b
Joined: 25 May 2006
Posts: 57
Location: Malta
|
 Posted: Sat Feb 14, 2009 5:28 pm Post subject: |
 |
|
| flybynite wrote: | | I seem to remember fixing this a while ago, I guess it might be changing again? What version of replicator and portage are you running? |
portage version 2.1.6.4
and http-replicator version 3.0-r1 (~x86)
Thanks,
melinux |
|
| Back to top |
|
 |
flybynite
l33t
Joined: 06 Dec 2002
Posts: 618
|
| Posted: Fri Feb 20, 2009 1:18 am Post subject: |
|
|
| melinux wrote: |
portage version 2.1.6.4
|
Portage switched from portage_manifest to portage.manifest in version 2.2-r6 or greater and repcacheman is fixed for that version. Now the change seems to have been backported to at least your portage version 2.1.6.4
Could you check to see if the current fix works for you to confirm this?
Just cp the file /usr/portage/net-proxy/http-replicator/files/http-replicator-3.0-repcacheman-0.44-r1 somewhere and run it instead of the system version.
Here is some code if you need it.
| Code: |
mkdir /root/repcachemantest
cd /root/repcachemantest
cp /usr/portage/net-proxy/http-replicator/files/http-replicator-3.0-repcacheman-0.44-r1 .
./http-replicator-3.0-repcacheman-0.44-r1
|
|
|
| Back to top |
|
|
jongeek
Tux's lil' helper
Joined: 13 Jul 2007
Posts: 135
Location: The Humid, Festering Swamps of Florida
|
| Posted: Fri Mar 13, 2009 5:32 pm Post subject: same thing here |
|
|
| flybynite wrote: |
Could you check to see if the current fix works for you to confirm this?
Just cp the file /usr/portage/net-proxy/http-replicator/files/http-replicator-3.0-repcacheman-0.44-r1 somewhere and run it instead of the system version.
|
I was having the same warnings with portage 2.1.6.7. I ran the repcacheman script as you described, and then it did not display the warnings. |
|
| Back to top |
|
|
melinux
n00b
Joined: 25 May 2006
Posts: 57
Location: Malta
|
| Posted: Fri Mar 13, 2009 6:34 pm Post subject: Re: same thing here |
|
|
| jongeek wrote: | | flybynite wrote: |
Could you check to see if the current fix works for you to confirm this?
Just cp the file /usr/portage/net-proxy/http-replicator/files/http-replicator-3.0-repcacheman-0.44-r1 somewhere and run it instead of the system version.
|
I was having the same warnings with portage 2.1.6.7. I ran the repcacheman script as you described, and then it did not display the warnings. |
At present I can't test that pc as its not working (hardware - overheating problems) right now...
I installed the current http-replicator and I have no problems as yet, on another machine. Thanks anyway. |
|
| Back to top |
|
|
Onkl
n00b
Joined: 01 Dec 2009
Posts: 2
|
| Posted: Tue Dec 01, 2009 9:24 am Post subject: |
|
|
I have set up http-replicator to also serve as PORTAGE_BINHOST. Works as advertised.
However, when I use
| Code: |
quickpkg --include-config=y <package>
|
to make a package with my adapted settings to my LAN, the package gets permissions of 600, which http-replicator will not serve. Changing the permissions to 644 solves this, but it is a hassle that I forget to do most of the time.
Is there a way to make http-replicator also serve those files, or make quickpkg to set the correct permissions? |
|
| Back to top |
|
|
flybynite
l33t
Joined: 06 Dec 2002
Posts: 618
|
| Posted: Fri Dec 04, 2009 3:09 am Post subject: |
|
|
| Onkl wrote: | | Is there a way to make http-replicator also serve those files, or make quickpkg to set the correct permissions? |
| Code: | h2 ~ # quickpkg --help
--umask=UMASK umask used during package creation (default is 0077)
|
Quickpkg's default umask of 0077 denies all users except root from even reading the file. I can't explain why it does that. Replicator can't change or work around such drastic file permissions.
There must be many others who feel that default umask is too drastic because Quickpkg does give you the option to change the umask to a more normal 022.
Try
| Code: |
h2 ~ # quickpkg --umask=022 nano
h2 ~ # ls -l /var/tmp/packages/All/nano*
-rw-r--r-- 1 root root 202145 2009-12-03 20:53 /var/tmp/packages/All/nano-2.1.10.tbz2
|
Now replicator can read the file and serve it to others.
You can make this easy by putting
| Code: | | alias quickpkg='quickpkg --umask=022' |
in your ~/.bashrc |
|
| Back to top |
|
|
Onkl
n00b
Joined: 01 Dec 2009
Posts: 2
|
| Posted: Fri Dec 04, 2009 8:46 am Post subject: |
|
|
Thanks a lot.
And since an "emerge -b" builds the package with 644 it is indeed strange that quickpkg is so restrictive. |
|
| Back to top |
|
|
sam_i_am
Tux's lil' helper
Joined: 19 Sep 2003
Posts: 120
|
| Posted: Sun Jun 20, 2010 10:31 pm Post subject: service doesn't start on one host |
|
|
Hi,
Thanks for this great program. I'm using at home and at work without any issues except:
On one host (x86), the http-replicator doesn't start. It says "failed to start service". Log says "HttpReplicator started", but it seems to die. I enabled debug option, but no other error messages. However, on a different host (x86_64) on the same network, it works with the exact same config parameters.
Any tips on how to go about finding out why?
Other than the being x86, the failing host also runs apache on port 80 and 443, but port 8080 is clear.
Sam
_________________
Sam |
|
| Back to top |
|
|
knight77
n00b
Joined: 29 Jun 2009
Posts: 21
|
|
| Back to top |
|
|
|
Documentation, Tips & Tricks
