[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] write documents
From: |
Karsten Hilbert |
Subject: |
Re: [Gnumed-devel] write documents |
Date: |
Thu, 21 Apr 2011 15:37:59 +0200 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Wed, Apr 20, 2011 at 05:34:06PM +0530, address@hidden wrote:
> What does this mean?
>
> received signal from client: "statustext"
> [msg]: Script must be readable by the calling user only (permissions
> "0600"): [C:\Users\Vaibhav\.gnumed\scripts\hook_script.py].
> [sender]: None
At various times during running the code GNUmed calls an
external "hook" script. This happens after certain actions
took place in the user interface:
u'post_patient_activation',
u'post_person_creation',
u'shutdown-post-GUI',
u'startup-after-GUI-init',
u'startup-before-GUI',
u'request_user_attention',
u'app_activated_startup',
u'app_activated',
u'app_deactivated',
u'after_substance_intake_modified',
u'after_test_result_modified',
u'after_soap_modified',
u'after_new_doc_created',
u'before_print_doc',
u'before_fax_doc',
u'before_mail_doc',
u'before_print_doc_part',
u'before_fax_doc_part',
u'before_mail_doc_part',
u'before_external_doc_access',
u'db_maintenance_warning'
Whenever one of those hooks is reached GNUmed executes the
hook script. That way the user can configure GNUmed to take
any action the desire. The wiki has a full explanation of
the hooks system.
Now, since the hook script is an external file GNUmed tries
to take at least *some* security checking - in this case it
looks at the permissions of the hook script and makes sure
that it is accessible by the owning user only (permissions
0600 in UNIX speak). If that is not the case it will refuse
the run the script and shows the above warning.
Karsten
--
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346