run the following from terminal
mkdir -P /var/run/pilerimport
chmod 777 /var/run/pilerimport
cd /var/run/pilerimport
su piler -c "pilerimport -i 'host' -u 'user' -p 'password' -P 143 -x '' "
^^note there are single ' and " double quotes.. the -x '' <= are 2x
single quotes
BTW, contact us if you need a proper admin/company to manage your piler
server.
On 2/2/2015 6:21 PM, Philip Deubner wrote:
I disagree with the approach from experience.
Rather write a simple shell script that does a few things.
*** set a pid in /var/run/ to prevent the script from spawning
multiple times..
Your idea is to spawn a new process every 15mins.. however the
pilerimport could still be running... this will eventually lead to a
lock of either the imap server or your pilerimport host.
Never use the harddrive as a store for temporary files, you will lag
your disk i/o and cause excessive wear.
*** set the tempory directory to /var/shm this is a "ram drive"
available on all linux systems, so the temp files will be stored in
memory reducing disk i/o to zero and reducing lag.
*** in the script create a temp dir with mkdir -p
/var/shm/pilerimport and set the permission to 777, to avoid any
permission errors.
Make sure piler import is run as piler user
*** su piler -c "pilerimport"
Well, that would definetely be a fancy script... But honestly, I
currently have no idea on how to do such (setting the pid and setting
the temporary directory). So if you have an idea on where I can search
to solve these issues, please tell me.
Apart from that, the problem would likely be the same, wouldn't it?
Finally, I would have to call the script using cron ans telling cron
to have the commands run in a certain directory - which already
currently does not work.
So, from my point of view, this should be the first problem to deal
with - or am I wrong?
bg,
Philip
