Bug#661698: [smstools] /var/run/smstools/smsd.working not created

> Package: smstools > Severity: normal > > The infofile, which is defined in /etc/default/smstools can't be found here. > The running process is: > > /usr/sbin/smsd -p/var/run/smstools/smsd.pid -i/var/run/smstools/smsd.working - > usmsd -gdialout > > Many thanks, Jan. > -- > Never write mail to

Bug#635717: smsd should respect TMPDIR

> Package: smstools > Version: 3.1.11-1 > > Hi, > > with /tmp mounted "noexec": > > 2011-07-28 11:38:21,3, smsd: Exec: startup_check (shell) encountered errors: > 2011-07-28 11:38:21,3, smsd: ! sh: /tmp/smsd_script.hh5rLQ: Permission denied > 2011-07-28 11:38:21,2, smsd: Shell /bin/sh testing

Bug#703687: smstools: inefficient polling of directories should be replaced by inotify interface

> Package: smstools > Version: 3.1.14-1 > Severity: minor > > > Hi, > > Smstools currently checks a couple of directories every x seconds. > That is inefficient: > 1. it doesn't react immediately on new outgoing sms messages, delaying their > transmission > 2. it polls when it is not

Bug#688451: smstools causes huge cpu-usage spikes

> I got frusted a bit by this problem (smsd using incredible much cpu > even when idle) so I ran smsd through valgrind (well, callgrind). > It looks like tons of time is spend in an usleep(100); (yes, hundred). > I always thought that Linux would just round it up to the next > scheduling interval

Bug#569346: Re: Bug#569346: zombies after abnormal termination of modem handlers

> > Package: smstools > > Version: 3.1-2+lenny1 > > Severity: normal > > Tags: patch > > > > After abnormal termination of modem handlers they chanded zombies. > > The attached patch would solve the problem. > > Should also apply to version 3.1.6. > > > > Hi, > > thank's for the information. > > I

Bug#755898: smstools: Great delays before messages are processed

> Package: smstools > Severity: important > Version: 3.1.14-1 > Tags: patch > > On a monitoring system with otherwie heavy I/O load (due to a large > number of RRDs being updated on a regular basis), it was noticed that > sending of a generated SMS was delayed for hours. > > Attaching gdb and

Bug#569346: zombies after abnormal termination of modem handlers

Package: smstools Version: 3.1-2+lenny1 Severity: normal Tags: patch After abnormal termination of modem handlers they chanded zombies. The attached patch would solve the problem. Should also apply to version 3.1.6. Hi, thank's for the information. I tried this patch and it resolved

Bug#476124: feat.req.: write to a log file every, say 5 minutes the signal/noise ratio. there is a command to let the gsm modem return this value

://smstools3.kekekasvi.com/index.php?p=configure (Modem settings). Regards, Keke -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#468349: Featurerequest: run-and-stop option

the init.d script provided_. - give some time for it, for example 20 seconds. - stop the smsd _using the init.d script provided_. This will do what you are missing. There is no reasons to change the SMSTools3, as Patrick already wrote. From the logfile you can see how much time is typically needed

Bug#431079: Invalid validity period in config file: year

No mather which VALUE I use, I get always Invalid validity period in config file: where can be 0-255, year, month, week, day, hour or min. Without the settings it seems to use a validity of ONE HOUR There is a bug which causes that clean numbers are not accepted. This is

Bug#429373: smstools should include a To: number header in received messages

Michelle, I know, since I was one time in contact with Keke. I have not found any emails within this issue. If you have sent any, please resend or use the Support Website. It's updated and is useable over GSM/GPRS/3G (I have used it with N95). Anyway, there is no destination number available

Bug#429374: smstools can not decode received messages but I can manualy...

No, it is not solved. If I install back the version 1.4 it woks. Receiving is no fine because I have to use different settings. Maybe I need special settings if I want to send SMS from a Siemens S40 using smstools 3.0? I cannot check the version 1.4 which is published between 4.12.2001

Bug#431080: smsd ignore pidfile if started as user and can be started in mass

The smsd is designed to run from the init.d script, the Debian one or sms3. The smsd also _should_ be run using the init.d script, because the script contains an important part of a functionality of smsd. The smsd does not do the script job, because a script will and should do it. This is because

Bug#431078: smsd produce files with false group

It seems that you have used an incorrect umask setting while you have started the smsd. I checked this with 3.0.2, and as Debian has not made any changes to the C code, this is not a Debian problem. The smsd inherits umask value from the calling process. This value limits permissions placed on

Bug#429374: smstools can not decode received messages but I can manualy...

have not seen your questions or feedback in there. Best Regards, Keke Author of Smstools 3 http://smstools3.kekekasvi.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#396427: smstools do not support PDU messages

the checkhandler and eventhandler features. Take a look at the next releases, they will include instructions about how this conversion can be done. Instructions can also be found on the support website. Hope this helps. Regards, Keke Author of smstools v3.x http://smstools3.kekekasvi.com