Thursday, March 12, 2009

How to make Horde3 to start in Administrator mode?

I have had this problem before - don't know why - but this is what I
did to get around it.

You need to run the database define stream that is appropriate for
you DB backend
/horde/scripts/sql/create.whateverdbyouhave

P.S.: I solved with database by running horde/scripts/setup.php

Then insert the default horde sql definition in conf.php

$conf['use_ssl'] = 2;

$conf['server']['name'] = $_SERVER['SERVER_NAME'];

$conf['server']['port'] = $_SERVER['SERVER_PORT'];

$conf['cookie']['domain'] = $_SERVER['SERVER_NAME'];

$conf['cookie']['path'] = '/horde';

$conf['debug_level'] = E_ALL & ~E_NOTICE;
$conf['umask'] = 077;
$conf['compress_pages'] = true;
$conf['session']['name'] = 'Horde';
$conf['session']['cache_limiter'] = 'nocache';
$conf['session']['timeout'] = 0;
$conf['auth']['admins'] = array('Administrator');
$conf['auth']['driver'] = 'auto';
$conf['auth']['params'] = array('username' => 'Administrator');
$conf['prefs']['driver'] = 'session';
$conf['menu']['always'] = false;
$conf['portal']['fixed_blocks'] = array();
$conf['imsp']['enabled'] = false;
$conf['kolab']['enabled'] = false;

$conf['log']['priority'] = PEAR_LOG_NOTICE;
$conf['log']['ident'] = 'HORDE';
$conf['log']['params'] = array();
$conf['log']['name'] = '/var/log/horde/horde3.log';
$conf['log']['params']['append'] = true;
$conf['log']['type'] = 'file';
$conf['log']['enabled'] = true;
$conf['log_accesskeys'] = false;

$conf['sql']['persistent'] = true;
$conf['sql']['username'] = 'horde';
$conf['sql']['password'] = '1_hordeadmin';
$conf['sql']['protocol'] = 'unix';
$conf['sql']['database'] = 'horde';
$conf['sql']['charset'] = 'utf-8';
$conf['sql']['splitread'] = false;
$conf['sql']['phptype'] = 'mysql';

then insert the datatree def in conf.php
$conf['datatree']['params']['driverconfig'] = 'horde';
$conf['datatree']['driver'] = 'sql';

Now you can open the Horde3 in Administrator mode and configure it normaly (this mean you type http://localhost/horde3)

======
When try to logout I got this "This request cannot be completed because the link you followed or the form you submitted was only valid for minutes. Please try again now"

Solved (see this link):

There is a math bug in the horde/lib/Horde.php checkRequestToken, the
paranthesis are missing :

instead of

if ($_SESSION['horde_form_secrets'][$token] +
$GLOBALS['conf']['urls']['token_lifetime'] * 60 < time()) {
return PEAR::raiseError(sprintf(_("This request cannot be
completed because the link you followed or the form you submitted was
only valid for %s minutes"),
$GLOBALS['conf']['urls']['token_lifetime']));
}

it should be

if (($_SESSION['horde_form_secrets'][$token] +
$GLOBALS['conf']['urls']['token_lifetime']) * 60 < time()) {
return PEAR::raiseError(sprintf(_("This request cannot be
completed because the link you followed or the form you submitted was
only valid for %s minutes"),
$GLOBALS['conf']['urls']['token_lifetime']));
}

no matter which setting you chose for token_lifetime - it will always
complain about that the link is no longer valid.
===========
Note:

if you have such message when loging in "Warning: Invalid argument supplied for foreach() in /ingo/lib/Block/overview.php on line 50"
this mean you have not created the database for INGO plughin

To do so, go to "horde/ingo/scripts/sql" and from there run:

# mysql -uroot -p database_passwd horde < ingo.sql



Enjoy.

Wednesday, March 4, 2009

VisualDRC, showing advise when drawing IC layout

Hi there my friend :)

This tool is very useful for layout designers. Why? Good question!
If you are such a designer you know how much it take for you to read and learn specific new technology rules to be able for fast design with optimal distances. It take some time to adapt with new design rules.
Now you can design faster, just follow the advise of this new wonderful tool "VisualDRC".

If you are interested in such tool, please contact the Micrologic Desing Automation or AsicArt


Visual DRC
VisualDRC™ is a EDA tool that check the design rules during the construction of an integrated circuit's layout block in real time mode.
VisualDRC™ is designed to provide advice, check and report violations. It is aimed for a fast, accurate, and efficient reliable verification during the construction of a mask layout database.
VisualDRC™ is equipped with simple-to-use and intuitive graphical interface.


Monday, March 2, 2009

Slow NFS solved on OpenSuse 11.0

Hi there
----------
1. First of all, the Raid 1 has been connected with one (2xhdd) IDE M-S connector, after Raid 1 (2xhdd) connected on different ports IDE also increased performance but still was slow.
----------
2. Then made these:

At the beginning export from NFS server was with these options:

#from /etc/exports
/exported_dir 10.0.0.0/24(rw, no_root_squash, sync, no_wdelay)

After I changed the "sync" to "async" the write speed performance increase was quite large.
P.S: "no_wdelay" with "async" is neglected.

Try "man 5 exports" to see all available options for export

Note: on clients the /etc/fstab mount line is:

#/etc/fstab
nisserv:/exported_dir /mount_path nfs defaults 0 0

The NFS server is on Piii 800MHz :D with 512MB Ram

Note: The man page says that async can be dangerous if the
NFS server daemon crashes as some data may not be committed to disk, but
this is always a risk (in my opinion anyways) since hard drives cache data
before it gets committed to disk anyways...


All the best, enjoy ;)