Re: [Resin-interest] Watchdog Manager

2008-03-20 Thread Scott Ferguson


On Mar 19, 2008, at 1:36 PM, Mktg. Incorporate Fast wrote:


Hello,

1.)  When using the watchdog manager in an ISP environment, what  
does the


/resin/conf/resin.conf, file need to contain?


This is the configuration for the user's Resin instance.  It will have  
the normal , , etc.


The only thing it will be missing is the  and .

That file will be readable by the user, by the way, unlike the  
watchdog's conf.


The default resin.conf has items like watchdog, etc, but I would  
assume that some of these config tags are not necessary.


Right.  In an ISP setting, you're splitting the resin.conf into two  
files.  One for the watchdog and one for the Resin instance.  So the  
watchdog configuration tags don't belong in the user's resin.conf.


Or would the watchdog.conf, call resin.conf and hence start a second/ 
new watchdog.conf…? If that made sense.


Yes, but the second conf is a resin.conf, not watchdog.


2.) For an ISP the , is this simply the document root,  
or is this a full resin install?


resin-root is the root-directory at the  environment.  So it's  
something like /var/www.


resin-home is the directory of the Resin installation.



3.) For an ISP the  tag has been implemented in the most  
recent snapshot.

Are there any docs on this yet?


No, and it hasn't been fully tested yet (although the implementation  
call is pretty simple).


I read the brief notes in Mantis regarding this.  Is it the   
tag within the  as suggested in the bug comments. http://bugs.caucho.com/view.php?id=2426 
.  As commented does this need to have: full resin, full jdk,  
resolv.conf, within the chroot directory and I assumed owned by the  
user noted in the watchdog.conf?


It would be in the , because each user gets his own chroot.

And, yes, you need everything that the application might need to run.   
(Actually, that's the reason it hasn't been tested yet.  Configuring  
that might be a pain.)  You might need stuff like /bin/sh as well.


-- Scott




http://caucho.com/ns/resin";>


  




  
-Xmx256m
-J-d32
  

  
resin
other

/resin/conf/resin.conf
/resin/webapps/domain


  






___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest


[Resin-interest] Watchdog Manager

2008-03-19 Thread Mktg. Incorporate Fast
Hello,

 

1.)  When using the watchdog manager in an ISP environment, what does the 

 

/resin/conf/resin.conf, file need to contain?  The
default resin.conf has items like watchdog, etc, but I would assume that
some of these config tags are not necessary. Or would the watchdog.conf,
call resin.conf and hence start a second/new watchdog.conf.? If that made
sense. 

 

2.) For an ISP the , is this simply the document root, or is
this a full resin install?

 

3.) For an ISP the  tag has been implemented in the most recent
snapshot.  Are there any docs on this yet?  I read the brief notes in Mantis
regarding this.  Is it the  tag within the  as
suggested in the bug comments. http://bugs.caucho.com/view.php?id=2426.  As
commented does this need to have: full resin, full jdk, resolv.conf, within
the chroot directory and I assumed owned by the user noted in the
watchdog.conf?

 

http://caucho.com/ns/resin";>

 



  



 



 

  

-Xmx256m

-J-d32

  

 

  

resin

other

 

/resin/conf/resin.conf

/resin/webapps/domain

 



  

 



 



 

 

___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest