nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

iw.local vs. iwat

System

Our system (TS 5.5) currently has a script running on submit using a trigger in iwlocal.cfg. Is there an advantage (or disadvantage) of setting this script to be run via the iwat command?

Find more posts tagged with

Comments

Adam Stoller

iwat information is recorded in the backing store and doesn't require a separate configuration file to run processes upon reboot.
iwat triggers can be viewed and disabled from the command line with iwlsat and iwrmat, rather than requiring the use of 'ps' and 'kill' (or Task Manager / End Process?)
iwat scripts do not require to be made into services (a pain in the proverbial on Windows) and thus the scripts themselves can be more portable across platforms.

I can't really think of anything in favor of using iw.local.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com