Hi Is there any difference in /Library/StartupItems in MacOS 10.4 vs 10.5 ? p2 -- _____________________________________________________________________ Disclaimer: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. Any views expressed in this message are those of the individual sender unless otherwise stated.Company has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. _____________________________________________________________________
not observing, but I developed startupitem too before which run on 10.4 but not on 10.5 p2 ----- Original Message ----- From: Dave Zarzycki To: Pradip Patel Cc: launchd-dev@lists.macosforge.org Sent: Tuesday, April 01, 2008 9:04 PM Subject: Re: [launchd-dev] StartupItems On Apr 1, 2008, at 6:59 AM, Pradip Patel wrote: - This message has been scanned for viruses, spam and dangerous content and is believed to be clean. Is there any difference in /Library/StartupItems in MacOS 10.4 vs 10.5 ? Pradip, Are you observing any differences? If so, what are they? davez -- _____________________________________________________________________ Disclaimer: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. Any views expressed in this message are those of the individual sender unless otherwise stated.Company has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. _____________________________________________________________________
At 22:32 +0530 1/4/08, Pradip Patel wrote:
but I developed startupitem too before which run on 10.4 but not on 10.5
There have not been major changes in startup items at the launchd level. However, Mac OS X 10.5 introduced major changes to other aspects of process management, so it's easy to imagine a startup item that worked on 10.4 but didn't work on 10.5. However, without some specific information to go on, we really can't offer any specific advice. If you're looking for information about the changes in process management in 10.5, the best place to start is TN2083. <http://developer.apple.com/technotes/tn2005/tn2083.html> Specifically, compare Figure 3 and Figure 6. S+E -- Quinn "The Eskimo!" <http://www.apple.com/developer/> Apple Developer Relations, Developer Technical Support, Core OS/Hardware
I found in log it shows <Warning>: 3891612: (connectAndCheck) Untrusted apps are not allowed to connect to or launch Window Server before login. it runs success ,bt not give expected result..my application is console base ----- Original Message ----- From: "Quinn" <eskimo1@apple.com> To: <launchd-dev@lists.macosforge.org> Sent: Wednesday, April 02, 2008 2:35 PM Subject: Re: [launchd-dev] StartupItems
At 22:32 +0530 1/4/08, Pradip Patel wrote:
but I developed startupitem too before which run on 10.4 but not on 10.5
There have not been major changes in startup items at the launchd level. However, Mac OS X 10.5 introduced major changes to other aspects of process management, so it's easy to imagine a startup item that worked on 10.4 but didn't work on 10.5. However, without some specific information to go on, we really can't offer any specific advice.
If you're looking for information about the changes in process management in 10.5, the best place to start is TN2083.
<http://developer.apple.com/technotes/tn2005/tn2083.html>
Specifically, compare Figure 3 and Figure 6.
S+E -- Quinn "The Eskimo!" <http://www.apple.com/developer/> Apple Developer Relations, Developer Technical Support, Core OS/Hardware _______________________________________________ launchd-dev mailing list launchd-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/launchd-dev
- This message has been scanned for viruses, spam and dangerous content and is believed to be clean.
-- _____________________________________________________________________ Disclaimer: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. Any views expressed in this message are those of the individual sender unless otherwise stated.Company has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. _____________________________________________________________________
At 14:58 +0530 2/4/08, Pradip Patel wrote:
I found in log it shows <Warning>: 3891612: (connectAndCheck) Untrusted apps are not allowed to connect to or launch Window Server before login.
it runs success ,bt not give expected result..my application is console base
This is a well known issue that is documented in TN2083. <http://developer.apple.com/technotes/tn2005/tn2083.html> Specifically, the section "Pre-Login Trust Issues". Take a look and let us know if you have any follow-up questions. Curiously, if you Google for "Untrusted apps are not allowed to connect to or launch Window Server before login", TN2083 is the second hit, and the first hit is also relevant. S+E -- Quinn "The Eskimo!" <http://www.apple.com/developer/> Apple Developer Relations, Developer Technical Support, Core OS/Hardware
I am going to read the link which you have given. just a question in mind do I have to sign the code ? or change the code ? ----- Original Message ----- From: "Quinn" <eskimo1@apple.com> To: <launchd-dev@lists.macosforge.org> Sent: Wednesday, April 02, 2008 3:12 PM Subject: Re: [launchd-dev] StartupItems
At 14:58 +0530 2/4/08, Pradip Patel wrote:
I found in log it shows <Warning>: 3891612: (connectAndCheck) Untrusted apps are not allowed to connect to or launch Window Server before login.
it runs success ,bt not give expected result..my application is console base
This is a well known issue that is documented in TN2083.
<http://developer.apple.com/technotes/tn2005/tn2083.html>
Specifically, the section "Pre-Login Trust Issues". Take a look and let us know if you have any follow-up questions.
Curiously, if you Google for "Untrusted apps are not allowed to connect to or launch Window Server before login", TN2083 is the second hit, and the first hit is also relevant.
S+E -- Quinn "The Eskimo!" <http://www.apple.com/developer/> Apple Developer Relations, Developer Technical Support, Core OS/Hardware _______________________________________________ launchd-dev mailing list launchd-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/launchd-dev
- This message has been scanned for viruses, spam and dangerous content and is believed to be clean.
-- _____________________________________________________________________ Disclaimer: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. Any views expressed in this message are those of the individual sender unless otherwise stated.Company has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. _____________________________________________________________________
At 15:40 +0530 2/4/08, Pradip Patel wrote:
do I have to sign the code ?
No. To quote from the technote: If, in Mac OS X 10.5 and later, you see a message like that shown in Listing 9 you might mistakenly think that the solution is to get the system to 'trust' your application, perhaps via code signing. However, this isn't the case. This message is really telling you is that you're trying to connect to the window server from the wrong context. You see this message if you try to connect to the global window server service from outside of the pre-login context before the user has logged in; typically this means that you're trying to use the window server from a daemon.
or change the code ?
Yes. Again, to quote from the technote: You should not attempt to fix this by convincing the window server to trust your program; doing so will just cause other problems further down the road. For example, if you do successfully connect to the window server from your daemon, you still have to deal with window server lifecycle issues described previously. Instead, you should fix this problem by changing your code to run in the correct context. If you need to connect to the window server in a pre-login context, create a pre-login launchd agent. For an example of this, see Sample Code Project 'PreLoginAgents'. S+E -- Quinn "The Eskimo!" <http://www.apple.com/developer/> Apple Developer Relations, Developer Technical Support, Core OS/Hardware
participants (3)
-
Dave Zarzycki
-
Pradip Patel
-
Quinn