Programming stuff: Bash, Linux, SQL and Java

i set gvim as the editor in the preferences of gftp.
the problem was that, when saving and exiting gvim, the file was removed from the temp folder, but was not uploaded back on the server.
this used to work with gedit.
a search on google took me to a post where a guy had the same problem as me, but no answer.
a man vim solved it.
it says there that gvim detaches itself from the shell , so gftp won’t see any exit code when you close gvim.
all i did was putting /usr/bin/gvim –nofork in the editor field.
voila!

some of my clients were having trouble sending large attachements throush my postfix server.
It went like this: when the file attached was bigger than 1 MB, the receiver got the mail around 8 times.
First i thought it is the person who sent it, being tired of waiting [they were on a slow connection to the internet] it clicked the send button several times.
it wasn’t the case.
then i thought , maybe there is a microsoft thing that didn’t comply with the standards. No it wasn’t.
i disabled their anti-virus software, check my postfix configuration, analysed the logs. nothing.
then, i saw a setting in the outlook called "server timeout". Bingo. that did it.
it was set to 1 minute and a half, and i increased it to 8 minutes.
no duplicate sent emails any more.

another client satisfied. Next! :)

I just started my own hosting business, and after buying a server [-dedicated :)], I began configuring my environment.
The hosting company provided me with a 3.1rc3 debian 64 bit version – minimal install – on an AMD dual core 64 bit with 2GB of RAM.
That was BIG, for I was coming from a VPS 200MHz CPU, 200 MB RAM.
So I started to prepare the install phase of all servers I needed.
here is my list:
bind – for nameserver
cyrus-sasl
postfix
postgrey
dovecot
apache-httpd
php
eaccelerator
lighttpd
mysql
java
jetty
openssl
vsftpd
All sources, all compiled as I like – maybe i will tell the arguments passed to the ./configure command line in another post.
Then was the environment.
.bash_history 10000 lines -> HISTSIZE=10000
HISTIGNORE=’\&:fg:bg:ls:pwd:cd ..:cd ~:ls -al:cd:ps -A:mc:ls -l:%1:%2:top:exit:halt*’ , this is in order to save only the important lines
Ctrl-R then would come handy to search for those precious lines.
VISUAL=/usr/bin/vim needed for crontab, and other tools that need an external editor
vim is my editor. VIM rules.