>>> just set the HOSTNAME variable in ~/.tmda/config that will fix your >>> problem... and then setup the HOSTNAME var in the skel file so that it >>> gets autoinstalled. >> >> Will that work if you're using tmda-cgi to create the initial >> ~/.tmda/config? I would guess no if you're using virtual domains. >> >> I was also curious why not take it from what the user supplied at login >> time? >> > > well you could setup a different tmda-cgi for every domain that you > have. Edit the config in each skel dir and make the HOSTNAME variable > set to the domain. You could probably setup a script to dynamically add > the HOSTNAME variable when they clicked install, but I have not done > that. I have 2 domains so that when users login to > http://thierdomain.com/tmda it points them to the right tmda-cgi dir on > my server.
I'm skeptical. While there's no reason that wouldn't work, it'd be nice if tmda-cgi just kept track of the user's domain name. I'd rather avoid the administrative overhead of keeping my script in sync with later releases of tmda-cgi. Though if it became necessary, it would work as a solution. I'm ok with waiting for the next release, especially since Gre7g commented in a previous message that its fixed in the cvs version. Plus I have a hunch the next release will be soon, since it seems to happen right around tmda releases. Aside from the hostname being displayed incorrectly, everything seems to behave properly. Regards, -- Dave Steinberg http://www.geekisp.com _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
