__/ [Doug Laidlaw] on Thursday 02 February 2006 09:04 \__
> I have a script to generate a signature. It runs O.K. under Kmail, but I
> Knode, I always get a message "cannot run the signature generator". I have
> an alternative user boinc for the setiathome project, and the user boinc
> can run it with no problems. Deleting the .kde/share/config/knoderc file
> and regenerating a default one makes no difference.
> I tried running knode with strace, but the recording seemed to stop when
> knode opened, and subsequent operations within it were not there.
> It sounds very much like a permission problem, but where?
I know this does not resolve your issue directly, but due to limitation in
some mail/news clients, which do not support binary file execution and still
need to share the same signature, I chose to rotate signature using a
light-weight cron job. Something along the lines of:
5,10,15,20,25,30,35,40,45,50,55,0 * * * * <PATH>/your_executable
In my individual case:
5,20,35,50 * * * * nice /home/roy/Main/Programs/HTML_Tools/ransig/randsig;
'http://Schestowitz.com | SuSE Linux | PGP-Key: 0x74572E8E' >>
/home/roy/.signature; uptime >> /home/roy/.signature; echo '
http://iuron.com - Open Source knowledge engine project' >>
If you are not familiar with cron jobs, just put your command (formatted as
in the examples above) in a simple text file, say cron.text, and then run
'crontab cron.text'. 'crontab -l' will show you which jobs are run. 'man
crontab' for more details. I know I may be stating the obvious here.
Bear in mind that .signature will be usable and accessible by all
applications. I need this for Thunderbird and Horde, for example. KNode uses
that too and so does KMail (I rarely ever use it though). Admittedly, it's
not real-time though, which might be an issue depending on the nature of
Hope it helps,