{5} Assigned, Active Tickets by Owner (Full Description) (31 matches)

I would like to to suggest that TXT records could be added too with manual dns. Atm that record type is missing.

Currently, ispCP uses the Mysql MyISAM engine that don't allow the transactions. For example, we know this issue poses some problems for the database update process now. I think the better is to switch to the INNODB engine for improve the data consistency. I'll try to provide a script for the automation of the migration process for that and also, add a new set of routines for transactions.

It's currently impossible to add NS type records in the custom DNS page. The only options are A AAAA CNAME MX SRV NS records are important for delegating part of a domain to another nameserver for individual management I haven't tried editing the sql db manually and adding a NS type record, I don't want to horribly break something, but the DB format doesn't need to change in order to incorporate this feature.

At the moment this is only useful when using dovecot as the LDA, but someday this have to be done.
At the moment there's a patch to be able to edit quota, but has the hassle that you need to re-type the password.
 http://www.isp-control.net/forum/thread-8483.html

ispCP register the new ISPCP_INPUT chain in front of every previous firewall rule, taking from admin the power to make changes to firewall.

ispCP isnt a complete firewall system, so the rules it add to iptables just allow connection to server, but without protect - as example from invalid or fragmented packets - even in valid ports. Also, it disables any "NEW state" connection treatment.

Isnt a option to use mangle table, since mangle aims change packets, not accept/reject/drop packets - even when it can do this: This kind of rule is filter responsability and inserting direct accept rules BEFORE all another rules can open too much the server and remove ability of sysadmin to control what happens in allowed services.

At present Dual-Core and Quad-Core server systems are running compression jobs (logs and backups) only on one cpu core as bzip2 is not able to do multithreading.

The recomeded replacement pbzip2 scales to all availbile cores on the system and so for compression scales almost linear better decrasing log rotating/backup times.

I would recomend to run pbzip2 with low priority so the rest of the server doesn't get to slow. for example:

edit /etc/ispcp/ispcp.conf

REPLACE:
CMD_BZIP = /bin/bzip2
BY:
CMD_BZIP = /usr/bin/nice -n19 /usr/bin/pbzip2

pbzip2 is included in Debian Lenny 5.0. Btw: The parallell implementation for gzip is called pigz and will be included in Debian Squeeze.

IspCP 1.0.4 has introduced a new layout for domains that are disabled. Some bugs found after 1.0.4 release have been fixed in 1.0.5 but a new problem was found : all subdomains linked to one disabled domain are still active. It's the same for all domain aliasses.

We should review this stuff and take decision on what should be disabled or not when the parent domain is disabled.

If we considere the parent domain as an unique entity (customer account) and then, this domain was been disabled because the customer was not respected him contract, we should disable all objects (subdomain, aliasses) linked to the parent domain.

In a other view, if we considere a domain name as a real domain name where the user account is an separate object, in this case, we should provide API to allow disable of all objects one by one (aliasses, subdomains..) linked to one domain name.

What do you think about this ?

I've created a patch, but for some reason it's HUGE! As such I can't attach it.

However you can download it from

Rather than just change the lines that are required it's replaced the entire files.

However I'm just about to go away for the weekend so might not get time to correct the problem, so will upload the patch here anyway

--- This patch consists of the following.

Allows the GUI frontend to have a custom page title by calling varible "CONTROL_PANEL_TITLE" from ispcp.conf.

Tidies up the breadcrumb trail for the page titles. i.e. all page titles are now consistant.

Fixies minor english grammatical errors ---

-={Q}=-

Omega fails if we do use another auxprop plugin but sasldb (and therefore the sasldb files do not exist) because "ispcp-mbox-mngr" alsways tries to update user/pw data through "sasldb_passwd".

There should be an option to disable the sasdlb method for those who do use another auxprop plugin.

In several subsystem (scripts) who are handling by the main debian maintainer scripts ( postinst, prem... ), I want use the existent ispcp_common_code.php .

The problem is the processing of the database keys generation in main.

Example of subsystem script in which I want use the ispc_common.code.php :

#! /bin/sh
# 
# $Id$
#
# Configure Bind 9 for ispCP Omega
# Laurent Declercq (ispCP Omega for Debian)


set -e

if [ $(id -u) != 0 ] ; then
    echo "You must be root to run this, please enter passwd"
    exec su -c "$0 $1"
fi

case "$1" in
    configure-files)
	cp -a /etc/bind/named.conf /etc/bind/named.conf.ispcp-new
	hostname=$(perl -e'require "/var/www/ispcp/engine/ispcp_common_code.pl"; print "$main::cfg{'SERVER_HOSTNAME'}\n";')
	ip_address=$(perl -e'require "/var/www/ispcp/engine/ispcp_common_code.pl"; print "$main::cfg{'BASE_SERVER_IP'}\n";')

....

I suggest replace the following code ( in ispcp_common_code.p ) :

if ($main::db_pass_key eq '{KEY}' || $main::db_pass_iv eq '{IV}') {

	print STDOUT "\tGenerating database keys, it may take some time, please wait...\n";
	print STDOUT "\tIf it takes to long, please check http://www.isp-control.net/documentation/frequently_asked_questions/what_does_generating_database_keys_it_may_take_some_time_please_wait..._on_setup_mean\n";

	$rs = sys_command("perl $main::cfg{'ROOT_DIR'}/keys/rpl.pl $main::cfg{'GUI_ROOT_DIR'}/include/ispcp-db-keys.php $main::cfg{'ROOT_DIR'}/engine/ispcp-db-keys.pl $main::cfg{'ROOT_DIR'}/engine/messager/ispcp-db-keys.pl");

	return $rs if ($rs != 0);

	do 'ispcp-db-keys.pl';
	get_conf();
}

by:

# $main::skip_db_pass is ugly hack to permit the reusability of
# commons subroutines in another specific subsystem scripting.
# With this, the $skip_db_pass variable can be defined in
# another script to disable the db pass generation process.
if (!defined($main::skip_db_pass) && ($main::db_pass_key eq '{KEY}' || $main::db_pass_iv eq '{IV}')) {

	print STDOUT "\tGenerating database keys, it may take some time, please wait...\n";
	print STDOUT "\tIf it takes to long, please check http://www.isp-control.net/documentation/frequently_asked_questions/what_does_generating_database_keys_it_may_take_some_time_please_wait..._on_setup_mean\n";

	$rs = sys_command("perl $main::cfg{'ROOT_DIR'}/keys/rpl.pl $main::cfg{'GUI_ROOT_DIR'}/include/ispcp-db-keys.php $main::cfg{'ROOT_DIR'}/engine/ispcp-db-keys.pl $main::cfg{'ROOT_DIR'}/engine/messager/ispcp-db-keys.pl");

	return $rs if ($rs != 0);

	do 'ispcp-db-keys.pl';
	get_conf();
}

After, I can make :

domain_name=$(perl -e' $main::skip_db_pass='_on_'; require "ispcp_common_code.pl"; print "$main::cfg{'SERVER_HOSTNAME'}\n";')

In plesk there use to be some attributes part of the domain_alias that ispcp at the moment doesn't have, they where the following:

  `dns` enum('false','true') NOT NULL default 'false',
  `mail` enum('false','true') NOT NULL default 'false',
  `web` enum('false','true') NOT NULL default 'false',
  `tomcat` enum('false','true') NOT NULL default 'false',

I don't care about tomcat, but having the information to allow/deny a service like dns or mail for a domain alias would be very important.
I was thinking of doing mail delivery only if the alias domain has mail enabled. This is trivial in dovecot with database backend and really useful.

Add the option "Check maximal number of labels for domain names and subdomains" for enable or disable in admin's GUI.

Debian package of ispCP Omega requires the respect of FHS.

See  http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.1

The IP can't be changed on a existing domain.

If we create a domain "X" on a ip, and we add a new IP to the resseler, and we would like to change this new IP to the domain XX, we can't.

instaling ssl certificates by the vhcs gui