Submitted by helpmin on Fri, 07/15/2011 - 21:57
For new domains you create, you can have Virtualmin automatically generate alias domains like this by going into System Settings -> Server Templates -> Default -> Virtual Server Creation -> Automatically create alias domain.
For example: mydomain.com
would create mydomain.com.otherdomain.com
That works pretty well. If you now create a subserver as well, then Virtualmin creates two folders in the domains folder:
subserver.mydomain.com
and
subserver.mydomain.com.otherdomain.com
Why would virtualmin create two folders? Could this be a bug?
Status:
Closed (fixed)
Comments
Submitted by JamieCameron on Sat, 07/16/2011 - 00:19 Comment #1
Actually that is expected .. each domain typically has a directory under
domains
, so for your sub-domain an equivalent alias domain is also created.Submitted by Locutus on Sat, 07/16/2011 - 05:16 Comment #2
Alias domains get a home directory folder? I'm not sure if this is really intended. :)
Submitted by helpmin on Sat, 07/16/2011 - 11:45 Comment #3
Yes, I also asked mself why a
ServerAlias
needs a home directory.Submitted by JamieCameron on Sat, 07/16/2011 - 12:15 Comment #4
It is potentially needed as you can have an alias domain with email aliases, one of which could be an auto-responder, and the text file for that responder needs to be saved in the alias domain's directory.
Submitted by helpmin on Sat, 07/16/2011 - 12:29 Comment #5
Thanks for the explanation!
Submitted by JamieCameron on Sat, 07/16/2011 - 16:54 Comment #6
I took another look at the code, and in fact the alias domain directory isn't needed most of the time, because by default aliase domains can't have extra email aliases. I will fix this in the next Virtualmin release (3.88).
Submitted by helpmin on Sat, 07/16/2011 - 17:06 Comment #7
Ok, great. So it is safe to delete those folders, right?
Submitted by JamieCameron on Sat, 07/16/2011 - 17:52 Comment #8
No .. don't delete them, as Virtualmin currently expects them to exist.
Submitted by Issues on Sat, 07/30/2011 - 18:21 Comment #9
Automatically closed -- issue fixed for 2 weeks with no activity.