Re: Maintaining server names list automatically? Virtual hosting
To my understanding the patch (http://issues.apache.org/jira/browse/JAMES-426) works fine against a jdbc connected VirtualUserTable. Daniel points out that it should also connect to stores as xmlVirtualUserTable and others. I agree to that. But such could be road mapped. However it will not be implemented in any release soon as it isn't on the slate for 2.3.0. or 3.0. Unless, it gets votes (as I understand it). Regards, Pierre Stefano Bagnara wrote: Jerry Malcolm wrote: I host quite a few server names hosted with one James instance. And server names periodically come and go. When I add a new client, I'd really like to have an automated way to add the server name to the list. There is no supported ways to do that. BTW You can look at this submitted patch (thanks to Daniel): http://issues.apache.org/jira/browse/JAMES-426 Stefano I realize the brute force way is to write some sort of Perl or Rexx script that parses the servername section out the config file and re-gen's the config file with an updated list, then bounce the James server so it'll pick up the change. Seems awfully clumsy to have to do that. But is that the only way? Is there a way to store the server list in a database table where James can read it out and check periodically to see if the entries in the table have changed? Or am I doomed to have to write a script to gen the config file? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maintaining server names list automatically?
Jerry Malcolm wrote: I host quite a few server names hosted with one James instance. And server names periodically come and go. When I add a new client, I'd really like to have an automated way to add the server name to the list. There is no supported ways to do that. BTW You can look at this submitted patch (thanks to Daniel): http://issues.apache.org/jira/browse/JAMES-426 Stefano I realize the brute force way is to write some sort of Perl or Rexx script that parses the servername section out the config file and re-gen's the config file with an updated list, then bounce the James server so it'll pick up the change. Seems awfully clumsy to have to do that. But is that the only way? Is there a way to store the server list in a database table where James can read it out and check periodically to see if the entries in the table have changed? Or am I doomed to have to write a script to gen the config file? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maintaining server names list automatically?
Jerry Malcolm wrote: I host quite a few server names hosted with one James instance. And server names periodically come and go. When I add a new client, I'd really like to have an automated way to add the server name to the list. I realize the brute force way is to write some sort of Perl or Rexx script that parses the servername section out the config file and re-gen's the config file with an updated list, then bounce the James server so it'll pick up the change. Seems awfully clumsy to have to do that. But is that the only way? Is there a way to store the server list in a database table where James can read it out and check periodically to see if the entries in the table have changed? Or am I doomed to have to write a script to gen the config file? As far as I know, right now you are doomed! Its the kind of thing JMX would be good for, but there is no ongoing effort in this area. An MBean would update the servernames and trigger a recycle of the affected components. What you could do right now is extract the servernames section out of the main config. file into a servernames.xml file and use an XML include to reference this file from the main config. Then you are left with a trivial edit prior to bouncing James. Look at the fetchmail part of the configuration for an XML include example. -- Steve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maintaining server names list automatically?
Somebody on this list has written code to store the servernames in a MySQL database and have James use the dynamic list so that there is no need to work inside the config. I searched and couldn't find the actual email, but someone on here should remember? Maybe this person submitted it to James? Anyway I would actually like to take a look at that code as well if anyone knows where it can be found. On 1/26/06, Steve Brewin [EMAIL PROTECTED] wrote: Jerry Malcolm wrote: I host quite a few server names hosted with one James instance. And server names periodically come and go. When I add a new client, I'd really like to have an automated way to add the server name to the list. I realize the brute force way is to write some sort of Perl or Rexx script that parses the servername section out the config file and re-gen's the config file with an updated list, then bounce the James server so it'll pick up the change. Seems awfully clumsy to have to do that. But is that the only way? Is there a way to store the server list in a database table where James can read it out and check periodically to see if the entries in the table have changed? Or am I doomed to have to write a script to gen the config file? As far as I know, right now you are doomed! Its the kind of thing JMX would be good for, but there is no ongoing effort in this area. An MBean would update the servernames and trigger a recycle of the affected components. What you could do right now is extract the servernames section out of the main config. file into a servernames.xml file and use an XML include to reference this file from the main config. Then you are left with a trivial edit prior to bouncing James. Look at the fetchmail part of the configuration for an XML include example. -- Steve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Camron Levanger - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maintaining server names list automatically?
I host quite a few server names hosted with one James instance. And server names periodically come and go. When I add a new client, I'd really like to have an automated way to add the server name to the list. I realize the brute force way is to write some sort of Perl or Rexx script that parses the servername section out the config file and re-gen's the config file with an updated list, then bounce the James server so it'll pick up the change. Seems awfully clumsy to have to do that. But is that the only way? Is there a way to store the server list in a database table where James can read it out and check periodically to see if the entries in the table have changed? Or am I doomed to have to write a script to gen the config file? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
