RE: Kannel startup script does not stop bearerbox completely

2008-10-28 Thread Davor Spasoski
Can you please be more precise with your method? Tried mv access.log acess.rotated cp blank acess.log but kannel continues to write in the acess.rotated Davor -Original Message- From: Mihai Zsigmond [mailto:[EMAIL PROTECTED] Sent: Monday, October 27, 2008 7:02 PM To:

RE: Kannel startup script does not stop bearerbox completely

2008-10-28 Thread Mihai Zsigmond
Hi Davor, Actually is the following sequence: cp access.log access.rotated cp -f a1.txt access.log chmod 644 access.log gzip -f -9 access.rotated As you can see you must not move the access.log but replace it with an empty file. The last step is optional. I must emphasize that I used this

RE: Kannel startup script does not stop bearerbox completely

2008-10-28 Thread Mihai Zsigmond
Hi Davor, As I have said in a previous post this method has been devised for low traffic SMSC links ( limit 1 SMS/sec). Most possible you loose the messages between the end of first copy command and the end of the second command. To minimise that risk, use a script rather than prompt commands

Re: Kannel startup script does not stop bearerbox completely

2008-10-28 Thread Alejandro Guerrieri
The proper approach to log rotation is to rename the files, create new files and kill -HUP the boxes to force them to start logging on the new files. Copying the files it's a very bad idea IMHO. If you happen to have a lot of traffic and the files are big it'll take a while to copy and you'll

send using async

2008-10-28 Thread teoh
when using aysnc mode to send sms, normally, there will be another thread at the backgroud listen to kannel submit_smresp and deliver_sm.  my question is how to know the delivery report belong to which sms message ? anyway to encapsulate hidden id inside submit_sm so that we can retrieve back