Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Customize Symantec LiveUpdate Apps

If anyone uses Norton AntiVirus on OS X in a big company, then you know how annoying it is to configure it for a big company. Well I learned some stuff that I thought I'd share with the world. Tomorrow maybe I'll share my daily cron job that replaces the Symantec Scheduler for updates on my corporate build.

What switches are available when calling LiveUpdate from a cron job or applescript?

  • This will make LiveUpdate exit after running: -liveupdateautoquit YES
  • Make LiveUpdate quiet except for an icon in the dock: -liveupdatequiet YES
  • Prompt you with a Yes / No about running LiveUpdate (used by the Installer): -liveupdateoninstall YES
  • The switch to do an update. LUal is the code for all products and virus defs: -update LUal
Example for use in a cron job or shell script (enter as one line, no added spaces):
 % /Applications/Norton Solutions/
   MacOS/LiveUpdate -liveupdateautoquit YES  -update LUal
Example so that the TV set update window won't appear (again, one line, no space after the "/" but add one after "YES"):
 % /Applications/Norton Solutions/
   MacOS/LiveUpdate -liveupdateautoquit YES  -liveupdatequiet YES 
   -update LUal
Hope this helps!
  • Currently 1.25 / 5
  You rated: 1 / 5 (4 votes cast)

Customize Symantec LiveUpdate | 8 comments | Create New Account
Click here to return to the 'Customize Symantec LiveUpdate' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Customize Symantec LiveUpdate
Authored by: Safar on Feb 12, '04 12:52:14PM

do you need an antivirus with os X ? I thought antivirus were for unsecure systems...

[ Reply to This | # ]
Customize Symantec LiveUpdate
Authored by: madamov on Feb 13, '04 09:56:28AM

If you run mail server on your OS X machine, then you need it to protect Windows clients from infecting by blocking emails that contain virus as attachment.

[ Reply to This | # ]
Check for net access
Authored by: ssevenup on Feb 13, '04 12:44:39AM

A collegue suggested the following...

en0status=`ifconfig en0 | /usr/bin/awk '/status: active/ {print $1}'`
en1status=`ifconfig en1 | /usr/bin/awk '/status: active/ {print $1}'`

if [ $en0status ] || [ $en1status ]; then

This way if you run a CRON script it won't run when your connect bandwidth is low. Liveupdate via modem could really suck.


Mark Moorcroft
Sys. Admin.

[ Reply to This | # ]
Check for net access
Authored by: jlevitsk on Apr 02, '04 12:58:28PM

That's awesome. I will probably switch to your check for eth0 or eth1 being up before doing a dig. I'll still do the dig because it's possible you can see an airport that doesn't actually have public internet access.

Thanks much.

[ Reply to This | # ]
Authored by: -McG- on Feb 13, '04 06:17:14PM

Safar -- As part of our corporate security policy, all our workstations are required to run A/V software, regardless of how susceptible they are to infection.

jlevitsk -- How do you go about authenticating the installer/updater after LiveUpdate has run, i.e. to actually install the defs? There's just no way I'm giving out admin rights to each user to do this....which seems to be NAV's default method. Any pointers/scripts you're willing to provide, I'd happily glom onto....thanks!


[ Reply to This | # ]
Authored by: jlevitsk on Feb 15, '04 06:43:00PM

I'm right there with you. I do not make my users admins. NAV 9.0.1 runs LiveUpdate with suid root so any user is capable of running LiveUpdate without admin privs.

[ Reply to This | # ]
Customize Symantec LiveUpdate
Authored by: cpragman on Feb 17, '04 02:09:43PM

Can you post a link to where you got the info on running LiveUpdate from the Terminal? I've been all over Symantec's website, but can't find any info on doing this.

[ Reply to This | # ]
Customize Symantec LiveUpdate
Authored by: jlevitsk on Feb 19, '04 12:47:34AM

I actually figured it out on my own. I submitted an article for Symantec to consider posting in their KB. I maintain my own little hints on so there are a couple more things I documented there. I submitted them here but they haven't posted yet.

I figured this all out by using the strings command to look at the strings within LiveUpdate. I knew about the -update switch and so I looked at what strings were near that in the binary. Ultimately I got the exact answers by looking at the installer and I found where they kick off LiveUpdate during install because the one during install exits when it is done.

[ Reply to This | # ]