naviserver-tracker — SourceForge Tracker Notifications

[naviserver-tracker] [ naviserver-Feature Requests-1120023 ] Allow to start server under root privilges

[SourceForge.net <no...@so...>]

Feature Requests item #1120023, was opened at 2005-02-10 14:30
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=719009&aid=1120023&group_id=130646

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Zoran Vasiljevic (vasiljevic)
Assigned to: Zoran Vasiljevic (vasiljevic)
Summary: Allow to start server under root privilges

Initial Comment:
Before all of you freak out, read please :-) 
 
Currently the server will just complain if you  
attempt to start it as root. However, we do need 
to do this. Our app is actually a backup/archive 
and server-synchronize product and it needs to 
access all files on the server and do something 
with them.  For this to work, I had to manually 
disable checking for user/group of 0/0 during the 
startup.  
 
Now, my idea is to allow compile-time option  
which would control this, like for example 
--enable-rootuser or similar. I think Apache build 
allows you to do this (at least it did when I worked 
with Apache for the last time, about 6 years ago). 
Default would be to *not* allow server to be started 
as root, which is what we have now.  
This can be 
#ifdef ALLOW_ROOT_USER 
#endif 
at one place in the nsmain.c.  
 
Any thoughts? 
 
 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=719009&aid=1120023&group_id=130646

[naviserver-tracker] [ naviserver-Feature Requests-1119365 ] Watchdog/binder process

[SourceForge.net <no...@so...>]

Feature Requests item #1119365, was opened at 2005-02-09 16:43
Message generated for change (Comment added) made by vasiljevic
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=719009&aid=1119365&group_id=130646

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Vlad Seryakov (seryakov)
Assigned to: Nobody/Anonymous (nobody)
Summary: Watchdog/binder process

Initial Comment:
I find current binder and -b command line option not
very usefull and easy to administer. Can we revert back
to 3.x binder and combine it with simple watchdog
process, so on start ns forks watchdog/biner process,
check for exit status and accepts
requests for socket allocation.

----------------------------------------------------------------------

>Comment By: Zoran Vasiljevic (vasiljevic)
Date: 2005-02-10 11:55

Message:
Logged In: YES 
user_id=95086

Eventually, the watchdog/binder combination seems not 
the way to go (privileges issue).  I see. 
 
Concerning binder: I would need an option, (may be even 
compile-time one, don't care) for the server to listen on 
all network interfaces, including loopback. Apart from this,  
I have no immediate nor mid-term needs to modify  
anything there so I suppose I will be perfectly happy with 
any changes you guys need  in this area.  
 
Concerning watchdog: we can't use daemontools nor init. 
Also, we do have windows as platform, remember. 
We have struggled to get *minimum* interface to the rest 
of the system hence our product is easily installable and 
removable from the system. Actually, the only point we  
have in common (config-wise) are entries in the startup 
machinery. Therefore, a control-process from within the  
nsd is ideal for our needs. I have done this with  
--enable-watchdog and it is #ifdef'ed in the code so for 
just about any other user of the server this is pretty 
invisible and obscure (no backward compat problems also). 
 

----------------------------------------------------------------------

Comment By: Vlad Seryakov (seryakov)
Date: 2005-02-09 22:00

Message:
Logged In: YES 
user_id=184124

Here is the new syntax i added to the binder:

addr:port[/protocol]
port[/protocol]
0/icmp[/count]

where protocol can be tcp,udp,unix,icmp is special case of
raw socket, added by count.


----------------------------------------------------------------------

Comment By: Stephen Deasey (sdeasey)
Date: 2005-02-09 21:55

Message:
Logged In: YES 
user_id=87254


Adding support for socket types other than TCP to the binder
sounds like a great idea.


----------------------------------------------------------------------

Comment By: Vlad Seryakov (seryakov)
Date: 2005-02-09 20:55

Message:
Logged In: YES 
user_id=184124

I agree, i use inittab for aolserver myself calling bach
script which parses nsd.tcl for address/port keyworkd and
builds -b options on the fly. In case of inittab, no need in
watchdog as well.
It is not even on my wish list, i just figured if watchdog
is to berunning as root, then it can include binder support.
Let's put aside binder as separate process issue for a
while, but i'd like to add to regular 4.x binder what i did
for supporting UDP/TCP/UNIX/RAW sockets. They still need to
be pre-bound but then can be used from within AS, this is
how snmp and dns modules uses those sockets.


----------------------------------------------------------------------

Comment By: Stephen Deasey (sdeasey)
Date: 2005-02-09 20:52

Message:
Logged In: YES 
user_id=87254


Hmm...  I guess you could split the config into multiple
pieces, let admins manage everything except address and port
to bind to.  But would we mandate that in the defautl
set-up, or just hope people didn't screw up in practice?


----------------------------------------------------------------------

Comment By: Stephen Deasey (sdeasey)
Date: 2005-02-09 20:49

Message:
Logged In: YES 
user_id=87254


I think the issue here is that you need root privs to bind
to port 80.  The address and port are specified in the
config file.  The config file is a Tcl script.

So to allow someone to change your webserver config file you
need to give away root privs on your server.  I'm not super
keen on this :-)

IIRC in 3.x there was a lot of code to make sure that the
config script was evaled in a safe interp, and the
motivation for the binder was code reduction/simplification.

This also impacts the chroot functionality.  Idealy you want
to chroot as the last thing you do before dropping root
privs so that you can open all your fileslink to libraries
etc., and not have to recreate a complete copy of your
environment in the jail.  But you need to know which
directory that is, and that's in the config file, which is a
script...

Personaly, I use daemontools to manage my servers.  You need
to create a simple wrapper script for this to work and I
find that is the ideal place to set some environment
variables for the IP, PORT etc.  I can pass those along on
the command line and extract them from the env in the tcl
config script with [env get IP] and so on.

The binder is a neat solution, but in practice it trips a
lot of people up and it's just a pain.  Giving away root is
not a great solution though...  :-(



----------------------------------------------------------------------

Comment By: Zoran Vasiljevic (vasiljevic)
Date: 2005-02-09 18:23

Message:
Logged In: YES 
user_id=95086

Honestly, I did forget already how 3.x did the binding :-What we do in 4.0 is to bind on all interfaces 
(I modified that in our private version).
But I'm open to all variants. I suppose I should look 
back in 3.x code how that was done... 
Or, you have a crystal-clear picture already in which 
case I will simply believe you ;-)
As soon as we create the sandbox, we can start hacking
this in. 



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=719009&aid=1119365&group_id=130646

[naviserver-tracker] [ naviserver-Feature Requests-1119365 ] Watchdog/binder process

[SourceForge.net <no...@so...>]

Feature Requests item #1119365, was opened at 2005-02-09 15:43
Message generated for change (Comment added) made by seryakov
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=719009&aid=1119365&group_id=130646

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Vlad Seryakov (seryakov)
Assigned to: Nobody/Anonymous (nobody)
Summary: Watchdog/binder process

Initial Comment:
I find current binder and -b command line option not
very usefull and easy to administer. Can we revert back
to 3.x binder and combine it with simple watchdog
process, so on start ns forks watchdog/biner process,
check for exit status and accepts
requests for socket allocation.

----------------------------------------------------------------------

>Comment By: Vlad Seryakov (seryakov)
Date: 2005-02-09 21:00

Message:
Logged In: YES 
user_id=184124

Here is the new syntax i added to the binder:

addr:port[/protocol]
port[/protocol]
0/icmp[/count]

where protocol can be tcp,udp,unix,icmp is special case of
raw socket, added by count.


----------------------------------------------------------------------

Comment By: Stephen Deasey (sdeasey)
Date: 2005-02-09 20:55

Message:
Logged In: YES 
user_id=87254


Adding support for socket types other than TCP to the binder
sounds like a great idea.


----------------------------------------------------------------------

Comment By: Vlad Seryakov (seryakov)
Date: 2005-02-09 19:55

Message:
Logged In: YES 
user_id=184124

I agree, i use inittab for aolserver myself calling bach
script which parses nsd.tcl for address/port keyworkd and
builds -b options on the fly. In case of inittab, no need in
watchdog as well.
It is not even on my wish list, i just figured if watchdog
is to berunning as root, then it can include binder support.
Let's put aside binder as separate process issue for a
while, but i'd like to add to regular 4.x binder what i did
for supporting UDP/TCP/UNIX/RAW sockets. They still need to
be pre-bound but then can be used from within AS, this is
how snmp and dns modules uses those sockets.


----------------------------------------------------------------------

Comment By: Stephen Deasey (sdeasey)
Date: 2005-02-09 19:52

Message:
Logged In: YES 
user_id=87254


Hmm...  I guess you could split the config into multiple
pieces, let admins manage everything except address and port
to bind to.  But would we mandate that in the defautl
set-up, or just hope people didn't screw up in practice?


----------------------------------------------------------------------

Comment By: Stephen Deasey (sdeasey)
Date: 2005-02-09 19:49

Message:
Logged In: YES 
user_id=87254


I think the issue here is that you need root privs to bind
to port 80.  The address and port are specified in the
config file.  The config file is a Tcl script.

So to allow someone to change your webserver config file you
need to give away root privs on your server.  I'm not super
keen on this :-)

IIRC in 3.x there was a lot of code to make sure that the
config script was evaled in a safe interp, and the
motivation for the binder was code reduction/simplification.

This also impacts the chroot functionality.  Idealy you want
to chroot as the last thing you do before dropping root
privs so that you can open all your fileslink to libraries
etc., and not have to recreate a complete copy of your
environment in the jail.  But you need to know which
directory that is, and that's in the config file, which is a
script...

Personaly, I use daemontools to manage my servers.  You need
to create a simple wrapper script for this to work and I
find that is the ideal place to set some environment
variables for the IP, PORT etc.  I can pass those along on
the command line and extract them from the env in the tcl
config script with [env get IP] and so on.

The binder is a neat solution, but in practice it trips a
lot of people up and it's just a pain.  Giving away root is
not a great solution though...  :-(



----------------------------------------------------------------------

Comment By: Zoran Vasiljevic (vasiljevic)
Date: 2005-02-09 17:23

Message:
Logged In: YES 
user_id=95086

Honestly, I did forget already how 3.x did the binding :-What we do in 4.0 is to bind on all interfaces 
(I modified that in our private version).
But I'm open to all variants. I suppose I should look 
back in 3.x code how that was done... 
Or, you have a crystal-clear picture already in which 
case I will simply believe you ;-)
As soon as we create the sandbox, we can start hacking
this in. 



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=719009&aid=1119365&group_id=130646

[naviserver-tracker] [ naviserver-Feature Requests-1119365 ] Watchdog/binder process

[SourceForge.net <no...@so...>]

Feature Requests item #1119365, was opened at 2005-02-09 08:43
Message generated for change (Comment added) made by sdeasey
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=719009&aid=1119365&group_id=130646

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Vlad Seryakov (seryakov)
Assigned to: Nobody/Anonymous (nobody)
Summary: Watchdog/binder process

Initial Comment:
I find current binder and -b command line option not
very usefull and easy to administer. Can we revert back
to 3.x binder and combine it with simple watchdog
process, so on start ns forks watchdog/biner process,
check for exit status and accepts
requests for socket allocation.

----------------------------------------------------------------------

>Comment By: Stephen Deasey (sdeasey)
Date: 2005-02-09 13:55

Message:
Logged In: YES 
user_id=87254


Adding support for socket types other than TCP to the binder
sounds like a great idea.


----------------------------------------------------------------------

Comment By: Vlad Seryakov (seryakov)
Date: 2005-02-09 12:55

Message:
Logged In: YES 
user_id=184124

I agree, i use inittab for aolserver myself calling bach
script which parses nsd.tcl for address/port keyworkd and
builds -b options on the fly. In case of inittab, no need in
watchdog as well.
It is not even on my wish list, i just figured if watchdog
is to berunning as root, then it can include binder support.
Let's put aside binder as separate process issue for a
while, but i'd like to add to regular 4.x binder what i did
for supporting UDP/TCP/UNIX/RAW sockets. They still need to
be pre-bound but then can be used from within AS, this is
how snmp and dns modules uses those sockets.


----------------------------------------------------------------------

Comment By: Stephen Deasey (sdeasey)
Date: 2005-02-09 12:52

Message:
Logged In: YES 
user_id=87254


Hmm...  I guess you could split the config into multiple
pieces, let admins manage everything except address and port
to bind to.  But would we mandate that in the defautl
set-up, or just hope people didn't screw up in practice?


----------------------------------------------------------------------

Comment By: Stephen Deasey (sdeasey)
Date: 2005-02-09 12:49

Message:
Logged In: YES 
user_id=87254


I think the issue here is that you need root privs to bind
to port 80.  The address and port are specified in the
config file.  The config file is a Tcl script.

So to allow someone to change your webserver config file you
need to give away root privs on your server.  I'm not super
keen on this :-)

IIRC in 3.x there was a lot of code to make sure that the
config script was evaled in a safe interp, and the
motivation for the binder was code reduction/simplification.

This also impacts the chroot functionality.  Idealy you want
to chroot as the last thing you do before dropping root
privs so that you can open all your fileslink to libraries
etc., and not have to recreate a complete copy of your
environment in the jail.  But you need to know which
directory that is, and that's in the config file, which is a
script...

Personaly, I use daemontools to manage my servers.  You need
to create a simple wrapper script for this to work and I
find that is the ideal place to set some environment
variables for the IP, PORT etc.  I can pass those along on
the command line and extract them from the env in the tcl
config script with [env get IP] and so on.

The binder is a neat solution, but in practice it trips a
lot of people up and it's just a pain.  Giving away root is
not a great solution though...  :-(



----------------------------------------------------------------------

Comment By: Zoran Vasiljevic (vasiljevic)
Date: 2005-02-09 10:23

Message:
Logged In: YES 
user_id=95086

Honestly, I did forget already how 3.x did the binding :-What we do in 4.0 is to bind on all interfaces 
(I modified that in our private version).
But I'm open to all variants. I suppose I should look 
back in 3.x code how that was done... 
Or, you have a crystal-clear picture already in which 
case I will simply believe you ;-)
As soon as we create the sandbox, we can start hacking
this in. 



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=719009&aid=1119365&group_id=130646

[naviserver-tracker] [ naviserver-Feature Requests-1119365 ] Watchdog/binder process

[SourceForge.net <no...@so...>]

Feature Requests item #1119365, was opened at 2005-02-09 15:43
Message generated for change (Comment added) made by seryakov
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=719009&aid=1119365&group_id=130646

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Vlad Seryakov (seryakov)
Assigned to: Nobody/Anonymous (nobody)
Summary: Watchdog/binder process

Initial Comment:
I find current binder and -b command line option not
very usefull and easy to administer. Can we revert back
to 3.x binder and combine it with simple watchdog
process, so on start ns forks watchdog/biner process,
check for exit status and accepts
requests for socket allocation.

----------------------------------------------------------------------

>Comment By: Vlad Seryakov (seryakov)
Date: 2005-02-09 19:55

Message:
Logged In: YES 
user_id=184124

I agree, i use inittab for aolserver myself calling bach
script which parses nsd.tcl for address/port keyworkd and
builds -b options on the fly. In case of inittab, no need in
watchdog as well.
It is not even on my wish list, i just figured if watchdog
is to berunning as root, then it can include binder support.
Let's put aside binder as separate process issue for a
while, but i'd like to add to regular 4.x binder what i did
for supporting UDP/TCP/UNIX/RAW sockets. They still need to
be pre-bound but then can be used from within AS, this is
how snmp and dns modules uses those sockets.


----------------------------------------------------------------------

Comment By: Stephen Deasey (sdeasey)
Date: 2005-02-09 19:52

Message:
Logged In: YES 
user_id=87254


Hmm...  I guess you could split the config into multiple
pieces, let admins manage everything except address and port
to bind to.  But would we mandate that in the defautl
set-up, or just hope people didn't screw up in practice?


----------------------------------------------------------------------

Comment By: Stephen Deasey (sdeasey)
Date: 2005-02-09 19:49

Message:
Logged In: YES 
user_id=87254


I think the issue here is that you need root privs to bind
to port 80.  The address and port are specified in the
config file.  The config file is a Tcl script.

So to allow someone to change your webserver config file you
need to give away root privs on your server.  I'm not super
keen on this :-)

IIRC in 3.x there was a lot of code to make sure that the
config script was evaled in a safe interp, and the
motivation for the binder was code reduction/simplification.

This also impacts the chroot functionality.  Idealy you want
to chroot as the last thing you do before dropping root
privs so that you can open all your fileslink to libraries
etc., and not have to recreate a complete copy of your
environment in the jail.  But you need to know which
directory that is, and that's in the config file, which is a
script...

Personaly, I use daemontools to manage my servers.  You need
to create a simple wrapper script for this to work and I
find that is the ideal place to set some environment
variables for the IP, PORT etc.  I can pass those along on
the command line and extract them from the env in the tcl
config script with [env get IP] and so on.

The binder is a neat solution, but in practice it trips a
lot of people up and it's just a pain.  Giving away root is
not a great solution though...  :-(



----------------------------------------------------------------------

Comment By: Zoran Vasiljevic (vasiljevic)
Date: 2005-02-09 17:23

Message:
Logged In: YES 
user_id=95086

Honestly, I did forget already how 3.x did the binding :-What we do in 4.0 is to bind on all interfaces 
(I modified that in our private version).
But I'm open to all variants. I suppose I should look 
back in 3.x code how that was done... 
Or, you have a crystal-clear picture already in which 
case I will simply believe you ;-)
As soon as we create the sandbox, we can start hacking
this in. 



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=719009&aid=1119365&group_id=130646

[naviserver-tracker] [ naviserver-Feature Requests-1119365 ] Watchdog/binder process

[SourceForge.net <no...@so...>]

Feature Requests item #1119365, was opened at 2005-02-09 08:43
Message generated for change (Comment added) made by sdeasey
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=719009&aid=1119365&group_id=130646

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Vlad Seryakov (seryakov)
Assigned to: Nobody/Anonymous (nobody)
Summary: Watchdog/binder process

Initial Comment:
I find current binder and -b command line option not
very usefull and easy to administer. Can we revert back
to 3.x binder and combine it with simple watchdog
process, so on start ns forks watchdog/biner process,
check for exit status and accepts
requests for socket allocation.

----------------------------------------------------------------------

>Comment By: Stephen Deasey (sdeasey)
Date: 2005-02-09 12:52

Message:
Logged In: YES 
user_id=87254


Hmm...  I guess you could split the config into multiple
pieces, let admins manage everything except address and port
to bind to.  But would we mandate that in the defautl
set-up, or just hope people didn't screw up in practice?


----------------------------------------------------------------------

Comment By: Stephen Deasey (sdeasey)
Date: 2005-02-09 12:49

Message:
Logged In: YES 
user_id=87254


I think the issue here is that you need root privs to bind
to port 80.  The address and port are specified in the
config file.  The config file is a Tcl script.

So to allow someone to change your webserver config file you
need to give away root privs on your server.  I'm not super
keen on this :-)

IIRC in 3.x there was a lot of code to make sure that the
config script was evaled in a safe interp, and the
motivation for the binder was code reduction/simplification.

This also impacts the chroot functionality.  Idealy you want
to chroot as the last thing you do before dropping root
privs so that you can open all your fileslink to libraries
etc., and not have to recreate a complete copy of your
environment in the jail.  But you need to know which
directory that is, and that's in the config file, which is a
script...

Personaly, I use daemontools to manage my servers.  You need
to create a simple wrapper script for this to work and I
find that is the ideal place to set some environment
variables for the IP, PORT etc.  I can pass those along on
the command line and extract them from the env in the tcl
config script with [env get IP] and so on.

The binder is a neat solution, but in practice it trips a
lot of people up and it's just a pain.  Giving away root is
not a great solution though...  :-(



----------------------------------------------------------------------

Comment By: Zoran Vasiljevic (vasiljevic)
Date: 2005-02-09 10:23

Message:
Logged In: YES 
user_id=95086

Honestly, I did forget already how 3.x did the binding :-What we do in 4.0 is to bind on all interfaces 
(I modified that in our private version).
But I'm open to all variants. I suppose I should look 
back in 3.x code how that was done... 
Or, you have a crystal-clear picture already in which 
case I will simply believe you ;-)
As soon as we create the sandbox, we can start hacking
this in. 



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=719009&aid=1119365&group_id=130646

[naviserver-tracker] [ naviserver-Feature Requests-1119365 ] Watchdog/binder process

[SourceForge.net <no...@so...>]

Feature Requests item #1119365, was opened at 2005-02-09 08:43
Message generated for change (Comment added) made by sdeasey
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=719009&aid=1119365&group_id=130646

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Vlad Seryakov (seryakov)
Assigned to: Nobody/Anonymous (nobody)
Summary: Watchdog/binder process

Initial Comment:
I find current binder and -b command line option not
very usefull and easy to administer. Can we revert back
to 3.x binder and combine it with simple watchdog
process, so on start ns forks watchdog/biner process,
check for exit status and accepts
requests for socket allocation.

----------------------------------------------------------------------

>Comment By: Stephen Deasey (sdeasey)
Date: 2005-02-09 12:49

Message:
Logged In: YES 
user_id=87254


I think the issue here is that you need root privs to bind
to port 80.  The address and port are specified in the
config file.  The config file is a Tcl script.

So to allow someone to change your webserver config file you
need to give away root privs on your server.  I'm not super
keen on this :-)

IIRC in 3.x there was a lot of code to make sure that the
config script was evaled in a safe interp, and the
motivation for the binder was code reduction/simplification.

This also impacts the chroot functionality.  Idealy you want
to chroot as the last thing you do before dropping root
privs so that you can open all your fileslink to libraries
etc., and not have to recreate a complete copy of your
environment in the jail.  But you need to know which
directory that is, and that's in the config file, which is a
script...

Personaly, I use daemontools to manage my servers.  You need
to create a simple wrapper script for this to work and I
find that is the ideal place to set some environment
variables for the IP, PORT etc.  I can pass those along on
the command line and extract them from the env in the tcl
config script with [env get IP] and so on.

The binder is a neat solution, but in practice it trips a
lot of people up and it's just a pain.  Giving away root is
not a great solution though...  :-(



----------------------------------------------------------------------

Comment By: Zoran Vasiljevic (vasiljevic)
Date: 2005-02-09 10:23

Message:
Logged In: YES 
user_id=95086

Honestly, I did forget already how 3.x did the binding :-What we do in 4.0 is to bind on all interfaces 
(I modified that in our private version).
But I'm open to all variants. I suppose I should look 
back in 3.x code how that was done... 
Or, you have a crystal-clear picture already in which 
case I will simply believe you ;-)
As soon as we create the sandbox, we can start hacking
this in. 



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=719009&aid=1119365&group_id=130646

[naviserver-tracker] [ naviserver-Feature Requests-1119257 ] Better interface to cache facility

[SourceForge.net <no...@so...>]

Feature Requests item #1119257, was opened at 2005-02-09 13:32
Message generated for change (Comment added) made by vasiljevic
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=719009&aid=1119257&group_id=130646

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Zoran Vasiljevic (vasiljevic)
Assigned to: Nobody/Anonymous (nobody)
Summary: Better interface to cache facility

Initial Comment:
Those commands are in the server itself:
ns_cache_flush 
ns_cache_stats 
ns_cache_size 
ns_cache_names 
ns_cache_keys

I would not touch them for the compatibility reasons.
However, they are pretty limited
(introspection/management).
What is missing is type of functionality added by the 
nscache module which I believe should have be done
long time ago already.
Suggestion: Include nscache into the core Tcl commands.
Stephen, you mentioned you've benn working on alternate
cache implementation. Can we use this and add better
Tcl interface?


----------------------------------------------------------------------

>Comment By: Zoran Vasiljevic (vasiljevic)
Date: 2005-02-09 18:25

Message:
Logged In: YES 
user_id=95086

We can synthesize your changes and Stephens rewrite 
of the cache guts. I see no problem there.  

----------------------------------------------------------------------

Comment By: Vlad Seryakov (seryakov)
Date: 2005-02-09 18:20

Message:
Logged In: YES 
user_id=184124

I added ns_cache incr command aslo some time ago, i think it
is inthe CVS version of nscache.
Also i used to play with core cache to add more prices size
calculation incuding overhead.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=719009&aid=1119257&group_id=130646

[naviserver-tracker] [ naviserver-Feature Requests-1119365 ] Watchdog/binder process

[SourceForge.net <no...@so...>]

Feature Requests item #1119365, was opened at 2005-02-09 16:43
Message generated for change (Comment added) made by vasiljevic
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=719009&aid=1119365&group_id=130646

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Vlad Seryakov (seryakov)
Assigned to: Nobody/Anonymous (nobody)
Summary: Watchdog/binder process

Initial Comment:
I find current binder and -b command line option not
very usefull and easy to administer. Can we revert back
to 3.x binder and combine it with simple watchdog
process, so on start ns forks watchdog/biner process,
check for exit status and accepts
requests for socket allocation.

----------------------------------------------------------------------

>Comment By: Zoran Vasiljevic (vasiljevic)
Date: 2005-02-09 18:23

Message:
Logged In: YES 
user_id=95086

Honestly, I did forget already how 3.x did the binding :-What we do in 4.0 is to bind on all interfaces 
(I modified that in our private version).
But I'm open to all variants. I suppose I should look 
back in 3.x code how that was done... 
Or, you have a crystal-clear picture already in which 
case I will simply believe you ;-)
As soon as we create the sandbox, we can start hacking
this in. 



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=719009&aid=1119365&group_id=130646

[naviserver-tracker] [ naviserver-Feature Requests-1119257 ] Better interface to cache facility

[SourceForge.net <no...@so...>]

Feature Requests item #1119257, was opened at 2005-02-09 12:32
Message generated for change (Comment added) made by seryakov
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=719009&aid=1119257&group_id=130646

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Zoran Vasiljevic (vasiljevic)
Assigned to: Nobody/Anonymous (nobody)
Summary: Better interface to cache facility

Initial Comment:
Those commands are in the server itself:
ns_cache_flush 
ns_cache_stats 
ns_cache_size 
ns_cache_names 
ns_cache_keys

I would not touch them for the compatibility reasons.
However, they are pretty limited
(introspection/management).
What is missing is type of functionality added by the 
nscache module which I believe should have be done
long time ago already.
Suggestion: Include nscache into the core Tcl commands.
Stephen, you mentioned you've benn working on alternate
cache implementation. Can we use this and add better
Tcl interface?


----------------------------------------------------------------------

>Comment By: Vlad Seryakov (seryakov)
Date: 2005-02-09 17:20

Message:
Logged In: YES 
user_id=184124

I added ns_cache incr command aslo some time ago, i think it
is inthe CVS version of nscache.
Also i used to play with core cache to add more prices size
calculation incuding overhead.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=719009&aid=1119257&group_id=130646

[naviserver-tracker] [ naviserver-Feature Requests-1119365 ] Watchdog/binder process

[SourceForge.net <no...@so...>]

Feature Requests item #1119365, was opened at 2005-02-09 15:43
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=719009&aid=1119365&group_id=130646

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Vlad Seryakov (seryakov)
Assigned to: Nobody/Anonymous (nobody)
Summary: Watchdog/binder process

Initial Comment:
I find current binder and -b command line option not
very usefull and easy to administer. Can we revert back
to 3.x binder and combine it with simple watchdog
process, so on start ns forks watchdog/biner process,
check for exit status and accepts
requests for socket allocation.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=719009&aid=1119365&group_id=130646

[naviserver-tracker] [ naviserver-Feature Requests-1119257 ] Better interface to cache facility

[SourceForge.net <no...@so...>]

Feature Requests item #1119257, was opened at 2005-02-09 13:32
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=719009&aid=1119257&group_id=130646

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Zoran Vasiljevic (vasiljevic)
Assigned to: Nobody/Anonymous (nobody)
Summary: Better interface to cache facility

Initial Comment:
Those commands are in the server itself:
ns_cache_flush 
ns_cache_stats 
ns_cache_size 
ns_cache_names 
ns_cache_keys

I would not touch them for the compatibility reasons.
However, they are pretty limited
(introspection/management).
What is missing is type of functionality added by the 
nscache module which I believe should have be done
long time ago already.
Suggestion: Include nscache into the core Tcl commands.
Stephen, you mentioned you've benn working on alternate
cache implementation. Can we use this and add better
Tcl interface?


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=719009&aid=1119257&group_id=130646