My surviving in debian (blog)

@myself:

i have the problem that the php-cgi never dies. A workaround is here:
http://www.directadmin.com/forum/showthread.php?p=120452#post120452

Does this not affect the directadmin skins ? As far as im aware the paths are hardcoded into the skins.
No, the software installations are free to customise. I either dont believe paths of php are hardcoded, but if it is it should not be a problem because you reinstall php after the deletion process!

hiya dwm

vm-pop3d is running but imapd not, do i need to start the service manually?

does this work on debian, but then init.d? :
-> http://help.directadmin.com/item.php?id=18

3) Make sure xinetd has the proper settings:
RedHat: /etc/xinetd.d/imap

Code:
# default: on
# description: imapd
service imap
{
   disable = no
   socket_type = stream
   wait = no
   user = root
   server = /usr/sbin/imapd
   log_on_success += DURATION USERID
   log_on_failure += USERID
   nice = 10
}
It should work too, the inetd.d answer. But what i see is your only problem that your imapd is not running. port 110 is pop3, and that should work if you (can) switch squirrelmail to pop3 access. For using imapd it has to be installed ofcourse. Your can check this with 'updatedb' and then 'locate imapd'. If no results, it is not installed *duh*. For installing i used before on CentOS just some package downloaded from the Internet. For Debian i use dovecot, so i dont really know how you can fix this. Maybe john knows a quick fix for this ([email protected]).


Hey dwm,

Als eerste wil ik zeggen dat je goed bezig bent voor debian/ubuntu op het forum, great stuff and keep it up!

How is webmail running for you?

Do you get this in squirrelmail? :
111 : Connection refused

I do, and i would like to fix it.

Here is alot of stuff but it doesnt apply to debian/ubuntu:
http://www.directadmin.com/help/item.php?id=18

There is also some other stuff but its about dovecot which i dont use.

Got any ideas?

My squirrelmail runs smoothly :) I am gonna look to the other stuff to fix!
 
Today i made a workaround for the incorrect httpd configs which are generated by DirectAdmin every time i add or modify a user, domain or subdomain. The solution is to rewrite_confs, but i dont get why this isnt happening automatically. John tells me in every mailsupport to do './build rewrite_confs' so i automated this in a set of custom scripts:
http://www.directadmin.com/forum/showthread.php?p=120456#post120456
 
Hey, Just wanted to say:

Good job!

PS:
After 6 months of testing (DA + Debian)... It's good to see somene starting thread like this. :)
.. If I just had more time for that.... :D

I have server open for testing so if you need someone to test something to compare a results, just let me know....
 
Last edited:
Hey, Just wanted to say:

Good job!

PS:
After 6 months of testing (DA + Debian)... It's good to see somene starting thread like this. :)
.. If I just had more time for that.... :D

I have server open for testing so if you need someone to test something to compare a results, just let me know....

Thats cool! I will keep that in mind, since i am thinking about creating some sort of ./build file for applying the fixes i described above..
 
If you are a user in group wheel or root, then it is a good thing to become root rights without logging in as root. Therefor you use 'su' or 'sudo'. Also 'visudo' (the sudoers file) is used by many. These are not installed by default. For installing use:

# apt-get install sudo
 
I found that some packages are not yet installed (on all systems), so here some goodies:

// First update all packages, else some commands will go wrong:
# apt-get update

// Install the local ftp client tool for testing
# apt-get install ftp

// Install the lsof monitoring tool for managing your system:
# apt-get install lsof

// Install dig, host and other BIND tools which are not included by default, but which are really needed at a good working system:
# apt-get install bindtools
 
Back
Top