Is there a way to add to OS X's install.log from within a shell script?
up vote
1
down vote
favorite
Is there a way to add an entry to OS X's /var/log/install.log file from within a shell script?
Optimally the method wouldn't require root access as I don't think I'll have it.
The problem I'm having is I'm executing a shell script as part of an installation-check (p15 of Apple's Distribution Definition XML Schema) step from within an OS X installer package via the Javascript System.run() command (p30 of Apple's Installer Javascript Reference), but I can't see any output from that shell script.
I know the shell script is executing, because when I use the "logger" command from within the script, my log text appears inside /var/log/system.log. But in order to get a complete picture of what's going on, I'd need to merge it by hand with /var/log/install.log, which is where the general output of the installer, and any Javascript logging I do, ends up.
Any help would be appreciated. I've tried using the "logger" command's -f flag to use /var/log/install.log, e.g.
logger -f /var/log/install.log sometext
...but no dice; sometext still gets added to /var/log/system.log.
macos logging installer
asked Feb 26 '13 at 19:57
Krishen Greenwell
146
add a comment |
up vote
1
down vote
favorite
Is there a way to add an entry to OS X's /var/log/install.log file from within a shell script?
Optimally the method wouldn't require root access as I don't think I'll have it.
The problem I'm having is I'm executing a shell script as part of an installation-check (p15 of Apple's Distribution Definition XML Schema) step from within an OS X installer package via the Javascript System.run() command (p30 of Apple's Installer Javascript Reference), but I can't see any output from that shell script.
I know the shell script is executing, because when I use the "logger" command from within the script, my log text appears inside /var/log/system.log. But in order to get a complete picture of what's going on, I'd need to merge it by hand with /var/log/install.log, which is where the general output of the installer, and any Javascript logging I do, ends up.
Any help would be appreciated. I've tried using the "logger" command's -f flag to use /var/log/install.log, e.g.
logger -f /var/log/install.log sometext
...but no dice; sometext still gets added to /var/log/system.log.
macos logging installer
asked Feb 26 '13 at 19:57
Krishen Greenwell
146
Have you found a solution? I'm in a very similar scenario (bash/pyhthon pre/post build scripts that need logging). Installer Man page(8) does talk of an "LOG_INSTALL facility" but I wasn't able to understand what it is, and whether my scripts can use it.
– Motti Shneor
Mar 2 '16 at 9:02
@MottiShneor I haven't, but I am still curious.. let me know if you figure anything out. I'm sorry it's taken so long to reply, only just saw your comment today. I might take another look, since it's been 3+ years.
– Krishen Greenwell
Oct 13 '16 at 23:24
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
Is there a way to add an entry to OS X's /var/log/install.log file from within a shell script?
Optimally the method wouldn't require root access as I don't think I'll have it.
The problem I'm having is I'm executing a shell script as part of an installation-check (p15 of Apple's Distribution Definition XML Schema) step from within an OS X installer package via the Javascript System.run() command (p30 of Apple's Installer Javascript Reference), but I can't see any output from that shell script.
I know the shell script is executing, because when I use the "logger" command from within the script, my log text appears inside /var/log/system.log. But in order to get a complete picture of what's going on, I'd need to merge it by hand with /var/log/install.log, which is where the general output of the installer, and any Javascript logging I do, ends up.
Any help would be appreciated. I've tried using the "logger" command's -f flag to use /var/log/install.log, e.g.
logger -f /var/log/install.log sometext
...but no dice; sometext still gets added to /var/log/system.log.
macos logging installer
asked Feb 26 '13 at 19:57
Krishen Greenwell
146
Is there a way to add an entry to OS X's /var/log/install.log file from within a shell script?
Optimally the method wouldn't require root access as I don't think I'll have it.
The problem I'm having is I'm executing a shell script as part of an installation-check (p15 of Apple's Distribution Definition XML Schema) step from within an OS X installer package via the Javascript System.run() command (p30 of Apple's Installer Javascript Reference), but I can't see any output from that shell script.
I know the shell script is executing, because when I use the "logger" command from within the script, my log text appears inside /var/log/system.log. But in order to get a complete picture of what's going on, I'd need to merge it by hand with /var/log/install.log, which is where the general output of the installer, and any Javascript logging I do, ends up.
Any help would be appreciated. I've tried using the "logger" command's -f flag to use /var/log/install.log, e.g.
logger -f /var/log/install.log sometext
...but no dice; sometext still gets added to /var/log/system.log.
macos logging installer
macos logging installer
asked Feb 26 '13 at 19:57
Krishen Greenwell
146
asked Feb 26 '13 at 19:57
Krishen Greenwell
146
edited Mar 3 '13 at 15:57
asked Feb 26 '13 at 19:57
Krishen Greenwell
146
asked Feb 26 '13 at 19:57
Krishen Greenwell
146
asked Feb 26 '13 at 19:57
Krishen Greenwell
146
146
Have you found a solution? I'm in a very similar scenario (bash/pyhthon pre/post build scripts that need logging). Installer Man page(8) does talk of an "LOG_INSTALL facility" but I wasn't able to understand what it is, and whether my scripts can use it.
– Motti Shneor
Mar 2 '16 at 9:02
@MottiShneor I haven't, but I am still curious.. let me know if you figure anything out. I'm sorry it's taken so long to reply, only just saw your comment today. I might take another look, since it's been 3+ years.
– Krishen Greenwell
Oct 13 '16 at 23:24
add a comment |
Have you found a solution? I'm in a very similar scenario (bash/pyhthon pre/post build scripts that need logging). Installer Man page(8) does talk of an "LOG_INSTALL facility" but I wasn't able to understand what it is, and whether my scripts can use it.
– Motti Shneor
Mar 2 '16 at 9:02
@MottiShneor I haven't, but I am still curious.. let me know if you figure anything out. I'm sorry it's taken so long to reply, only just saw your comment today. I might take another look, since it's been 3+ years.
– Krishen Greenwell
Oct 13 '16 at 23:24
Have you found a solution? I'm in a very similar scenario (bash/pyhthon pre/post build scripts that need logging). Installer Man page(8) does talk of an "LOG_INSTALL facility" but I wasn't able to understand what it is, and whether my scripts can use it.
– Motti Shneor
Mar 2 '16 at 9:02
Have you found a solution? I'm in a very similar scenario (bash/pyhthon pre/post build scripts that need logging). Installer Man page(8) does talk of an "LOG_INSTALL facility" but I wasn't able to understand what it is, and whether my scripts can use it.
– Motti Shneor
Mar 2 '16 at 9:02
@MottiShneor I haven't, but I am still curious.. let me know if you figure anything out. I'm sorry it's taken so long to reply, only just saw your comment today. I might take another look, since it's been 3+ years.
– Krishen Greenwell
Oct 13 '16 at 23:24
@MottiShneor I haven't, but I am still curious.. let me know if you figure anything out. I'm sorry it's taken so long to reply, only just saw your comment today. I might take another look, since it's been 3+ years.
– Krishen Greenwell
Oct 13 '16 at 23:24
add a comment |
4 Answers
4
active
oldest
votes
up vote
1
down vote
Read up on bash scripting.
You can add a line to a file like this
echo "My line here" >> /var/log/system.log
If it gives a Permission denied error, you need root access.
answered Feb 26 '13 at 20:29
Chiel ten Brinke
6,30154584
Thanks for your reply Chiel92. Unfortunately that requires root access (the "logger" command gets around this, but only seems to allow additions to /var/log/system.log, and I need to be able to add to /var/log/install.log).
– Krishen Greenwell
Feb 26 '13 at 21:26
If you just need to know the contents of these files, can't you just put the content into a third file?
– Chiel ten Brinke
Feb 26 '13 at 21:45
I could, I was just looking for a clever way to avoid to merging the two files manually.
– Krishen Greenwell
Feb 27 '13 at 20:21
If you don't have write access to install.log or system.log, you can't write to it, so you should write both files to a third file you háve access to. Just runcat /var/log/system.log > myfile.log; cat /var/log/install.log >> myfile.log. Note the double >> in the second command.
– Chiel ten Brinke
Feb 28 '13 at 15:19
Hi Chiel92, thanks for your reply. Let me explain the use case. This is for debugging installer problems that might occur on a customer's machine. When the installer executes its normal operations, logging data from it goes into /var/log/install.log. However, when the installer launches a shell script as a helper, output from it goes nowhere. My hope was that there would be some way to write to /var/log/install.log from said helper shell script. Yes, I could write to another file and merge it later, but optimally I was looking for a way to avoid this. Looks like it might not be possible.
– Krishen Greenwell
Mar 1 '13 at 20:14
|
show 3 more comments
up vote
0
down vote
That's not an answer per se, but maybe a hint? Installer man pages mention a "LOG_INSTALL facility", whose output is the desired /var/log/install.log
But what is this "facility" and where is it available - I can't find. I really need to write my pre/post script failures and specific scenarios to that log.
answered Mar 2 '16 at 9:08
Motti Shneor
1,56611314
add a comment |
up vote
0
down vote
OK. Long time passed, and I found out the following.
In normal scenarios, anything written by pre and post install scripts (mine are python and bash) to stdout will be logged by the installer daemon to the /var/log/install.log. I experimented various tools to create my installer packages, and they usually did this.
However, in my own deployment installer, for some reason, only things written to stderr get logged to the /var/log/install.log - so you might want to try that too.
answered Oct 15 '16 at 16:30
Motti Shneor
1,56611314
Hey, cool, thanks for looking into it again. I will give it a try and report back here how it goes
– Krishen Greenwell
Oct 18 '16 at 1:56
It works in our product... after you test it, and If you find it worthy, vote!
– Motti Shneor
Oct 19 '16 at 18:46
add a comment |
up vote
0
down vote
A little late, but just had the same problem and was able to add logs to install.log from AppleScript using logger with the LOG_INSTALL facility:
logger -p 'install.error' "My error message"
answered Nov 9 at 12:13
sergiopm
1064
add a comment |
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
Read up on bash scripting.
You can add a line to a file like this
echo "My line here" >> /var/log/system.log
If it gives a Permission denied error, you need root access.
answered Feb 26 '13 at 20:29
Chiel ten Brinke
6,30154584
Thanks for your reply Chiel92. Unfortunately that requires root access (the "logger" command gets around this, but only seems to allow additions to /var/log/system.log, and I need to be able to add to /var/log/install.log).
– Krishen Greenwell
Feb 26 '13 at 21:26
If you just need to know the contents of these files, can't you just put the content into a third file?
– Chiel ten Brinke
Feb 26 '13 at 21:45
I could, I was just looking for a clever way to avoid to merging the two files manually.
– Krishen Greenwell
Feb 27 '13 at 20:21
If you don't have write access to install.log or system.log, you can't write to it, so you should write both files to a third file you háve access to. Just runcat /var/log/system.log > myfile.log; cat /var/log/install.log >> myfile.log. Note the double >> in the second command.
– Chiel ten Brinke
Feb 28 '13 at 15:19
Hi Chiel92, thanks for your reply. Let me explain the use case. This is for debugging installer problems that might occur on a customer's machine. When the installer executes its normal operations, logging data from it goes into /var/log/install.log. However, when the installer launches a shell script as a helper, output from it goes nowhere. My hope was that there would be some way to write to /var/log/install.log from said helper shell script. Yes, I could write to another file and merge it later, but optimally I was looking for a way to avoid this. Looks like it might not be possible.
– Krishen Greenwell
Mar 1 '13 at 20:14
|
show 3 more comments
up vote
1
down vote
Read up on bash scripting.
You can add a line to a file like this
echo "My line here" >> /var/log/system.log
If it gives a Permission denied error, you need root access.
answered Feb 26 '13 at 20:29
Chiel ten Brinke
6,30154584
Thanks for your reply Chiel92. Unfortunately that requires root access (the "logger" command gets around this, but only seems to allow additions to /var/log/system.log, and I need to be able to add to /var/log/install.log).
– Krishen Greenwell
Feb 26 '13 at 21:26
If you just need to know the contents of these files, can't you just put the content into a third file?
– Chiel ten Brinke
Feb 26 '13 at 21:45
I could, I was just looking for a clever way to avoid to merging the two files manually.
– Krishen Greenwell
Feb 27 '13 at 20:21
If you don't have write access to install.log or system.log, you can't write to it, so you should write both files to a third file you háve access to. Just runcat /var/log/system.log > myfile.log; cat /var/log/install.log >> myfile.log. Note the double >> in the second command.
– Chiel ten Brinke
Feb 28 '13 at 15:19
Hi Chiel92, thanks for your reply. Let me explain the use case. This is for debugging installer problems that might occur on a customer's machine. When the installer executes its normal operations, logging data from it goes into /var/log/install.log. However, when the installer launches a shell script as a helper, output from it goes nowhere. My hope was that there would be some way to write to /var/log/install.log from said helper shell script. Yes, I could write to another file and merge it later, but optimally I was looking for a way to avoid this. Looks like it might not be possible.
– Krishen Greenwell
Mar 1 '13 at 20:14
|
show 3 more comments
up vote
1
down vote
up vote
1
down vote
Read up on bash scripting.
You can add a line to a file like this
echo "My line here" >> /var/log/system.log
If it gives a Permission denied error, you need root access.
answered Feb 26 '13 at 20:29
Chiel ten Brinke
6,30154584
Read up on bash scripting.
You can add a line to a file like this
echo "My line here" >> /var/log/system.log
If it gives a Permission denied error, you need root access.
answered Feb 26 '13 at 20:29
Chiel ten Brinke
6,30154584
answered Feb 26 '13 at 20:29
Chiel ten Brinke
6,30154584
answered Feb 26 '13 at 20:29
Chiel ten Brinke
6,30154584
answered Feb 26 '13 at 20:29
Chiel ten Brinke
6,30154584
6,30154584
Thanks for your reply Chiel92. Unfortunately that requires root access (the "logger" command gets around this, but only seems to allow additions to /var/log/system.log, and I need to be able to add to /var/log/install.log).
– Krishen Greenwell
Feb 26 '13 at 21:26
If you just need to know the contents of these files, can't you just put the content into a third file?
– Chiel ten Brinke
Feb 26 '13 at 21:45
I could, I was just looking for a clever way to avoid to merging the two files manually.
– Krishen Greenwell
Feb 27 '13 at 20:21
If you don't have write access to install.log or system.log, you can't write to it, so you should write both files to a third file you háve access to. Just runcat /var/log/system.log > myfile.log; cat /var/log/install.log >> myfile.log. Note the double >> in the second command.
– Chiel ten Brinke
Feb 28 '13 at 15:19
Hi Chiel92, thanks for your reply. Let me explain the use case. This is for debugging installer problems that might occur on a customer's machine. When the installer executes its normal operations, logging data from it goes into /var/log/install.log. However, when the installer launches a shell script as a helper, output from it goes nowhere. My hope was that there would be some way to write to /var/log/install.log from said helper shell script. Yes, I could write to another file and merge it later, but optimally I was looking for a way to avoid this. Looks like it might not be possible.
– Krishen Greenwell
Mar 1 '13 at 20:14
|
show 3 more comments
Thanks for your reply Chiel92. Unfortunately that requires root access (the "logger" command gets around this, but only seems to allow additions to /var/log/system.log, and I need to be able to add to /var/log/install.log).
– Krishen Greenwell
Feb 26 '13 at 21:26
If you just need to know the contents of these files, can't you just put the content into a third file?
– Chiel ten Brinke
Feb 26 '13 at 21:45
I could, I was just looking for a clever way to avoid to merging the two files manually.
– Krishen Greenwell
Feb 27 '13 at 20:21
If you don't have write access to install.log or system.log, you can't write to it, so you should write both files to a third file you háve access to. Just runcat /var/log/system.log > myfile.log; cat /var/log/install.log >> myfile.log. Note the double >> in the second command.
– Chiel ten Brinke
Feb 28 '13 at 15:19
Hi Chiel92, thanks for your reply. Let me explain the use case. This is for debugging installer problems that might occur on a customer's machine. When the installer executes its normal operations, logging data from it goes into /var/log/install.log. However, when the installer launches a shell script as a helper, output from it goes nowhere. My hope was that there would be some way to write to /var/log/install.log from said helper shell script. Yes, I could write to another file and merge it later, but optimally I was looking for a way to avoid this. Looks like it might not be possible.
– Krishen Greenwell
Mar 1 '13 at 20:14
Thanks for your reply Chiel92. Unfortunately that requires root access (the "logger" command gets around this, but only seems to allow additions to /var/log/system.log, and I need to be able to add to /var/log/install.log).
– Krishen Greenwell
Feb 26 '13 at 21:26
Thanks for your reply Chiel92. Unfortunately that requires root access (the "logger" command gets around this, but only seems to allow additions to /var/log/system.log, and I need to be able to add to /var/log/install.log).
– Krishen Greenwell
Feb 26 '13 at 21:26
If you just need to know the contents of these files, can't you just put the content into a third file?
– Chiel ten Brinke
Feb 26 '13 at 21:45
If you just need to know the contents of these files, can't you just put the content into a third file?
– Chiel ten Brinke
Feb 26 '13 at 21:45
I could, I was just looking for a clever way to avoid to merging the two files manually.
– Krishen Greenwell
Feb 27 '13 at 20:21
I could, I was just looking for a clever way to avoid to merging the two files manually.
– Krishen Greenwell
Feb 27 '13 at 20:21
If you don't have write access to install.log or system.log, you can't write to it, so you should write both files to a third file you háve access to. Just run
cat /var/log/system.log > myfile.log; cat /var/log/install.log >> myfile.log. Note the double >> in the second command.– Chiel ten Brinke
Feb 28 '13 at 15:19
If you don't have write access to install.log or system.log, you can't write to it, so you should write both files to a third file you háve access to. Just run
cat /var/log/system.log > myfile.log; cat /var/log/install.log >> myfile.log. Note the double >> in the second command.– Chiel ten Brinke
Feb 28 '13 at 15:19
Hi Chiel92, thanks for your reply. Let me explain the use case. This is for debugging installer problems that might occur on a customer's machine. When the installer executes its normal operations, logging data from it goes into /var/log/install.log. However, when the installer launches a shell script as a helper, output from it goes nowhere. My hope was that there would be some way to write to /var/log/install.log from said helper shell script. Yes, I could write to another file and merge it later, but optimally I was looking for a way to avoid this. Looks like it might not be possible.
– Krishen Greenwell
Mar 1 '13 at 20:14
Hi Chiel92, thanks for your reply. Let me explain the use case. This is for debugging installer problems that might occur on a customer's machine. When the installer executes its normal operations, logging data from it goes into /var/log/install.log. However, when the installer launches a shell script as a helper, output from it goes nowhere. My hope was that there would be some way to write to /var/log/install.log from said helper shell script. Yes, I could write to another file and merge it later, but optimally I was looking for a way to avoid this. Looks like it might not be possible.
– Krishen Greenwell
Mar 1 '13 at 20:14
|
show 3 more comments
up vote
0
down vote
That's not an answer per se, but maybe a hint? Installer man pages mention a "LOG_INSTALL facility", whose output is the desired /var/log/install.log
But what is this "facility" and where is it available - I can't find. I really need to write my pre/post script failures and specific scenarios to that log.
answered Mar 2 '16 at 9:08
Motti Shneor
1,56611314
add a comment |
up vote
0
down vote
That's not an answer per se, but maybe a hint? Installer man pages mention a "LOG_INSTALL facility", whose output is the desired /var/log/install.log
But what is this "facility" and where is it available - I can't find. I really need to write my pre/post script failures and specific scenarios to that log.
answered Mar 2 '16 at 9:08
Motti Shneor
1,56611314
add a comment |
up vote
0
down vote
up vote
0
down vote
That's not an answer per se, but maybe a hint? Installer man pages mention a "LOG_INSTALL facility", whose output is the desired /var/log/install.log
But what is this "facility" and where is it available - I can't find. I really need to write my pre/post script failures and specific scenarios to that log.
answered Mar 2 '16 at 9:08
Motti Shneor
1,56611314
That's not an answer per se, but maybe a hint? Installer man pages mention a "LOG_INSTALL facility", whose output is the desired /var/log/install.log
But what is this "facility" and where is it available - I can't find. I really need to write my pre/post script failures and specific scenarios to that log.
answered Mar 2 '16 at 9:08
Motti Shneor
1,56611314
answered Mar 2 '16 at 9:08
Motti Shneor
1,56611314
answered Mar 2 '16 at 9:08
Motti Shneor
1,56611314
answered Mar 2 '16 at 9:08
Motti Shneor
1,56611314
1,56611314
add a comment |
add a comment |
up vote
0
down vote
OK. Long time passed, and I found out the following.
In normal scenarios, anything written by pre and post install scripts (mine are python and bash) to stdout will be logged by the installer daemon to the /var/log/install.log. I experimented various tools to create my installer packages, and they usually did this.
However, in my own deployment installer, for some reason, only things written to stderr get logged to the /var/log/install.log - so you might want to try that too.
answered Oct 15 '16 at 16:30
Motti Shneor
1,56611314
Hey, cool, thanks for looking into it again. I will give it a try and report back here how it goes
– Krishen Greenwell
Oct 18 '16 at 1:56
It works in our product... after you test it, and If you find it worthy, vote!
– Motti Shneor
Oct 19 '16 at 18:46
add a comment |
up vote
0
down vote
OK. Long time passed, and I found out the following.
In normal scenarios, anything written by pre and post install scripts (mine are python and bash) to stdout will be logged by the installer daemon to the /var/log/install.log. I experimented various tools to create my installer packages, and they usually did this.
However, in my own deployment installer, for some reason, only things written to stderr get logged to the /var/log/install.log - so you might want to try that too.
answered Oct 15 '16 at 16:30
Motti Shneor
1,56611314
Hey, cool, thanks for looking into it again. I will give it a try and report back here how it goes
– Krishen Greenwell
Oct 18 '16 at 1:56
It works in our product... after you test it, and If you find it worthy, vote!
– Motti Shneor
Oct 19 '16 at 18:46
add a comment |
up vote
0
down vote
up vote
0
down vote
OK. Long time passed, and I found out the following.
In normal scenarios, anything written by pre and post install scripts (mine are python and bash) to stdout will be logged by the installer daemon to the /var/log/install.log. I experimented various tools to create my installer packages, and they usually did this.
However, in my own deployment installer, for some reason, only things written to stderr get logged to the /var/log/install.log - so you might want to try that too.
answered Oct 15 '16 at 16:30
Motti Shneor
1,56611314
OK. Long time passed, and I found out the following.
In normal scenarios, anything written by pre and post install scripts (mine are python and bash) to stdout will be logged by the installer daemon to the /var/log/install.log. I experimented various tools to create my installer packages, and they usually did this.
However, in my own deployment installer, for some reason, only things written to stderr get logged to the /var/log/install.log - so you might want to try that too.
answered Oct 15 '16 at 16:30
Motti Shneor
1,56611314
answered Oct 15 '16 at 16:30
Motti Shneor
1,56611314
answered Oct 15 '16 at 16:30
Motti Shneor
1,56611314
answered Oct 15 '16 at 16:30
Motti Shneor
1,56611314
1,56611314
Hey, cool, thanks for looking into it again. I will give it a try and report back here how it goes
– Krishen Greenwell
Oct 18 '16 at 1:56
It works in our product... after you test it, and If you find it worthy, vote!
– Motti Shneor
Oct 19 '16 at 18:46
add a comment |
Hey, cool, thanks for looking into it again. I will give it a try and report back here how it goes
– Krishen Greenwell
Oct 18 '16 at 1:56
It works in our product... after you test it, and If you find it worthy, vote!
– Motti Shneor
Oct 19 '16 at 18:46
Hey, cool, thanks for looking into it again. I will give it a try and report back here how it goes
– Krishen Greenwell
Oct 18 '16 at 1:56
Hey, cool, thanks for looking into it again. I will give it a try and report back here how it goes
– Krishen Greenwell
Oct 18 '16 at 1:56
It works in our product... after you test it, and If you find it worthy, vote!
– Motti Shneor
Oct 19 '16 at 18:46
It works in our product... after you test it, and If you find it worthy, vote!
– Motti Shneor
Oct 19 '16 at 18:46
add a comment |
up vote
0
down vote
A little late, but just had the same problem and was able to add logs to install.log from AppleScript using logger with the LOG_INSTALL facility:
logger -p 'install.error' "My error message"
answered Nov 9 at 12:13
sergiopm
1064
add a comment |
up vote
0
down vote
A little late, but just had the same problem and was able to add logs to install.log from AppleScript using logger with the LOG_INSTALL facility:
logger -p 'install.error' "My error message"
answered Nov 9 at 12:13
sergiopm
1064
add a comment |
up vote
0
down vote
up vote
0
down vote
A little late, but just had the same problem and was able to add logs to install.log from AppleScript using logger with the LOG_INSTALL facility:
logger -p 'install.error' "My error message"
answered Nov 9 at 12:13
sergiopm
1064
A little late, but just had the same problem and was able to add logs to install.log from AppleScript using logger with the LOG_INSTALL facility:
logger -p 'install.error' "My error message"
answered Nov 9 at 12:13
sergiopm
1064
answered Nov 9 at 12:13
sergiopm
1064
answered Nov 9 at 12:13
sergiopm
1064
answered Nov 9 at 12:13
sergiopm
1064
1064
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f15098095%2fis-there-a-way-to-add-to-os-xs-install-log-from-within-a-shell-script%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Have you found a solution? I'm in a very similar scenario (bash/pyhthon pre/post build scripts that need logging). Installer Man page(8) does talk of an "LOG_INSTALL facility" but I wasn't able to understand what it is, and whether my scripts can use it.
– Motti Shneor
Mar 2 '16 at 9:02
@MottiShneor I haven't, but I am still curious.. let me know if you figure anything out. I'm sorry it's taken so long to reply, only just saw your comment today. I might take another look, since it's been 3+ years.
– Krishen Greenwell
Oct 13 '16 at 23:24