aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: Amuleweb support for xinetd  (Read 5457 times)

Crakem

  • Full Member
  • ***
  • Karma: 2
  • Offline Offline
  • Posts: 103
Amuleweb support for xinetd
« on: March 06, 2008, 05:11:38 PM »

Please, anymore thinks it will be beautiful if amuleweb could be shut up and shut down for xinetd? It will be spend less resources because it only run when somebody is accessing it.

Today I'm using it with a script called from xinetd which only give you 5 minutes for completing your task  ::)

Thanks!
Logged

lfroen

  • Guest
Re: Amuleweb support for xinetd
« Reply #1 on: March 07, 2008, 01:14:29 PM »

Good idea, I'll check it
Logged

Crakem

  • Full Member
  • ***
  • Karma: 2
  • Offline Offline
  • Posts: 103
Re: Amuleweb support for xinetd
« Reply #2 on: March 07, 2008, 04:35:27 PM »

Logged

Crakem

  • Full Member
  • ***
  • Karma: 2
  • Offline Offline
  • Posts: 103
Re: Amuleweb support for xinetd
« Reply #3 on: March 08, 2008, 02:38:53 PM »

There is a small gain in resource savings (and a recycle of the amuleweb thread in case it hungs...) , but the initial access will be definitely slower.
You always could load amuleweb from amule if you want not to wait a little more. xinetd support is optional for loading amuleweb, as you know my friend. In my pc, amuleweb spend 12% memory and sometimes it crash so I have to reload amuled entirely. Xinetd support save this too, as you say.
Logged

lfroen

  • Guest
Re: Amuleweb support for xinetd
« Reply #4 on: March 09, 2008, 06:16:06 AM »

Generating backtrace and/or coredump and talking here would may have those crashes fixed. On my machine amuleweb doesn't crash, so I think it worth debugging.
On the other hand, it doesn't take here 12% memory either. May be you simply run out of memory?
Logged

lfroen

  • Guest
Re: Amuleweb support for xinetd
« Reply #5 on: March 09, 2008, 09:47:28 AM »

Actually, after giving a second thought - launching amuleweb on every request from xined would be bad idea. The problem is that amuleweb maintain sort of mirror of core database. This database is being incrementally updated for each request. Restarting amuleweb every time will cause full status reload on every request. Result - waste of cpu time and bandwidth.
Logged

Crakem

  • Full Member
  • ***
  • Karma: 2
  • Offline Offline
  • Posts: 103
Re: Amuleweb support for xinetd
« Reply #6 on: March 09, 2008, 03:32:38 PM »

... May be you simply run out of memory?
Maybe I have only 64MB
Quote
launching amuleweb on every request from xined would be bad idea
with xinetd you have two modes of operation, wait and nowait as you know. I'm running amuleweb throught xinetd now, Its a little dirty but works well. With instances=1 worked fine
Thanks for replies
NOTE: maybe it will be fine if I learn howto send backtraces, I want to learn it and I'll do it when I found a way of sending them automatically on each crash. I think I'll do it finally. Remember I'm running I a (very) low resource computer where recompiling its a pain  :'(
Thanks for replies.
« Last Edit: March 09, 2008, 03:36:30 PM by Crakem »
Logged

lfroen

  • Guest
Re: Amuleweb support for xinetd
« Reply #7 on: March 10, 2008, 05:25:26 AM »

64Mb? Is it some kind of embedded system? Did you checked your kernel log for "out of memory, killing process XXX"?
Anyway, if you running only 1 instance, why mess with xinetd in first place?
Logged

Crakem

  • Full Member
  • ***
  • Karma: 2
  • Offline Offline
  • Posts: 103
Re: Amuleweb support for xinetd
« Reply #8 on: March 10, 2008, 10:43:41 PM »

64Mb? Is it some kind of embedded system? Did you checked your kernel log for "out of memory, killing process XXX"?
Anyway, if you running only 1 instance, why mess with xinetd in first place?
It's a K6-II PC system but is similar to lacie ethernet minidisk (64mb too, i saw in this forum somebody working with it) I'm using xinetd for launching amuleweb because it spend over 10% memory and there is no reason for spending that all time, let's spend 10% memory only when somebody are working with downloads :)
I increased my download rate when launched amuleweb from xinetd.

No I don't see "out of memory" message at all. Computer have only samba, amule and a firewall  :D Works well!!

Thanks for replies
Logged

lfroen

  • Guest
Re: Amuleweb support for xinetd
« Reply #9 on: March 11, 2008, 02:54:26 PM »

If you want to save memory, I have better idea:
http://forum.amule.org/index.php?topic=14610.0
Logged

Crakem

  • Full Member
  • ***
  • Karma: 2
  • Offline Offline
  • Posts: 103
Re: Amuleweb support for xinetd
« Reply #10 on: March 12, 2008, 12:18:20 AM »

If you want to save memory, I have better idea:
http://forum.amule.org/index.php?topic=14610.0
Thanks you very much, I never seen such option while compiling. But I only spend a little more of your time, How could I reset amuleweb if it have crashed? In that case I have to do a amuled restart?
Thanks for replies.
EDIT: I saw you post in feature request, please lfroen if you want to save CPU and memory, why you don't run on clients amulegui? (leaving amuled only in server) That's my point of view, I would need amuleweb for clients who currently can't connect with amulegui from WinXP. When amulegui stabilize I'm using amuleweb only for by passing clients out of my LAN (with another computer) adding a ssl wrapper (but amuleweb will never run anymore in amuled server because encryption spend too much CPU!)
« Last Edit: March 12, 2008, 12:28:14 AM by Crakem »
Logged

lfroen

  • Guest
Re: Amuleweb support for xinetd
« Reply #11 on: March 12, 2008, 09:24:40 AM »

Quote
Thanks you very much, I never seen such option while compiling
Well, that's because it's planned feature.

Quote
How could I reset amuleweb if it have crashed?
Just start it again.

Quote
In that case I have to do a amuled restart?
No.

Quote
if you want to save CPU and memory, why you don't run on clients amulegui
I do, but because of implementation details, this waste (some) memory too. That's why I'm evaluating monolithic approach.

Logged