Posts by flames

    this happens from time to time when backup job is running on a domain and some file is in the same moment changed by customer (via ftp or some script)
    nothing to worry about, just this same backup is not full, the one file, that was changed, is missed.
    the more customers you have, the more such emails you will get, because the chance of backup and file changing incident grows

    no, it is not possible.


    and why do you want that at all? if you just want run your primary and secondary on one machine, it is not recommended, but possible.


    bind would respond to both resellers zones ip1 ns1.domain.tld as primary, and ip2 ns2.domain.tld as secondary, you dont even need to configure bind for primary/secondary. the only prerequisite are two ips from different nets (which is given in your case)


    your resellers webhosting would still be separated to your both ips by imscp

    too many cooks can spoil the broth, ergo, one administrator can manage multiple servers, one server should not be managed by multiple administrators.


    if you want to allow your user to manipulate imscp templates, you need to give him root access. he could by an accident break your server. even if he doesn't, you could break the server in an administrative conflict that relies in time dilation in your communication with the other admin (and many other options to get rid of your server)


    to make long story short, there is no way to allow your user to fully edit imscp templates, and templates only, while the rest of your server remain secure. there is a way, your resellers can upload their reseller logo. but nothing more w/o to provide anyone but the root with any imscp manipulations.


    best way to provide a user with a custom template, is to let him send the template to you, you review the changes for possible exploits / security hole he might built in, and to upload it your self after all is right ;)


    to provide your user with a template development environment, you can offer him a free vserver, so he can work in an independent system without risc for your productive machines.

    du meinst www. vor dem alias?
    hast du den IN A record für die subdomain oder den wildcard beim registrar bereits angelegt?
    sonst lege www. als subdomain für den alias an (subdomain anlegen, alias auswählen) und ebenfalls forwarding auf die hauptdomain

    ah jetzt schon? gut, deswegen hab ich es nicht empfohlen xD


    wie verhält sich das mit dem upgrade von einer älteren version die noch mountpoint unterstützt auf die neue rc?


    ich habe nämlich noch eine 1.1.0 beta2 drauf mit sehr vielen mountpoints die auf / eingestellt sind. und ich komme einfach nicht dazu das mal zu testen aus zeitlichen gründen.

    MAKE BACKUP FIRST! DON'T BLAME ME, IF IT GOES WRONG :P


    attention: sdb0 is just for example, find out what name your new hdd has and replace sdb0 in every command. sdb0 = first logical partition on second physical sata/scsi drive


    mkfs.ext3 /dev/sdb0
    mkdir /media/sdb0
    mount /dev/sdb0 /media/sdb0


    /etc/initd./apache2 stop
    cp -R /var/www/virtual/* /media/sdb0/
    mv /var/www/virtual /var/www/virtual.old


    umount /media/sdb0
    mkdir /var/www/virtual
    mount /dev/sdb0 /var/www/virtual


    edit /etc/fstab and add following line (this is needed so the hdd will be automatically mounted at reboot)
    /dev/sdb0 /var/www/virtual ext3 rw 0 0


    /etc/init.d/apache2 start
    and see if any errors


    if everything went well, we can clean up after all
    rm -rf /var/www/virtual.old
    rm -rf /media/sdb0


    edit: and remember, this is just a second drive, it has no redundancy