Yep! Best thing to do is start simple:
DEVPATH!="*/smsgiucv_app", GOTO="smsgiucv_app_end"
SUBSYSTEM=="module", ACTION=="add", RUN+="/sbin/vmcp msg JAMES udev rules
loaded"
ENV{SMSG_SENDER}!="JAMES", GOTO="smsgiucv_app_end"
ACTION=="change", \
PROGRAM=="/usr/local/bin/myscript $env{SMSG_SENDER} $env{SMSG_TEXT}", \
RUN+="/sbin/vmcp -k MSG $env{SMSG_SENDER} $result"
LABEL="smsgiucv_app_end"
This would be in a rule file in /etc/udev/rules.d/ Breaking this example
down, it sends "JAMES" a message letting me know that the smsgiucv_app is
loaded up and ready. The ENV(SMSG_SENDER) makes sure only my userid "JAMES"
is allowed to use this rule, otherwise it bails out.
Then the ACTION calls a script evaluating the sent info and sends the
response back.
-- *James Vincent*
On Wed, Aug 19, 2020 at 8:19 AM Dave Jones <[email protected]> wrote:
> Hello, all.
>
> Before I go down this rabbit hole, does anyone here have a working
> example of the smsgiucv_app that I could look at? I don't seem to
> understand how to code the udev rules correctly.
> Many thanks and stay safe.
> DJ
>
> --
> DAVID JONES | MANAGING DIRECTOR FOR ZSYSTEMS SERVICES | z/VM, Linux, and
> Cloud
> 703.237.7370 (Office) | 281.578.7544 (CELL)
>
> INFORMATION TECHNOLOGY COMPANY
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO LINUX-390 or
> visit
> http://www2.marist.edu/htbin/wlvindex?LINUX-390
>
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390