From seasoft at west.net Tue Apr 1 16:37:24 2008 From: seasoft at west.net (Richard Hartman) Date: Tue Apr 1 16:37:36 2008 Subject: [X-Unix] Time Warp Hits System Logs Message-ID: Cross-post apologies: I meant to send this to the x-unix list but sent it to the x4u list by mistake... My bad. ------------------------------- Whilst playing around with Time Machine backups to a mounted AFP volume earlier today, evidently there was some kind of system error that was not reported or evident via the GUI but was recorded in the system & console logs, as I just discovered some 5.5 hours after they happened; nothing really remarkable about that, BUT... The thing is that All the console and system logs quit getting updates at that instant. I just noticed this while I was looking at the system log out of boredom. I was unable to do anything that would generate a log update (for example, I initiated a Time Machine backup which normally always reports progress to system; nothing). I rebooted the system and the log entries began to update normally. Here is the system log portion spanning the "missing" 5+ hours: ================== . . lots of logged errors, like... Apr 1 10:38:34 iMac20 kernel[0]: disk6s2: 0x14 (UNDEFINED). Apr 1 10:38:33 iMac20 fseventsd[38]: failed to unlink old log file / Volumes/Backup of iMac20/.fseventsd/00000000200749a5 (Input/output error) Apr 1 10:38:34 iMac20 kernel[0]: Apr 1 10:38:33 iMac20 fseventsd[38]: failed to unlink old log file / Volumes/Backup of iMac20/.fseventsd/0000000020076c6b (Input/output error) Apr 1 10:38:34 iMac20 kernel[0]: Apr 1 10:38:33 iMac20 fseventsd[38]: failed to unlink old log file / Volumes/Backup of iMac20/.fseventsd/0000000020079a9c (Input/output error) Apr 1 10:38:34 iMac20 kernel[0]: [FSLogMsgOrder Last] Apr 1 10:38:33 iMac20 fseventsd[38]: failed to unlink old log file / Volumes/Backup of iMac20/.fseventsd/000000002007bcea (Input/output error) Apr 1 10:38:34 iMac20 kernel[0]: disk6s2: 0x14 (UNDEFINED). Apr 1 10:38:33 iMac20 fseventsd[38]: failed to unlink old log file / Volumes/Backup of iMac20/.fseventsd/000000002007eb80 (Input/output error) Apr 1 10:38:34 iMac20 kernel[0]: Apr 1 10:38:33 iMac20 fseventsd[38]: failed to unlink old log file / Volumes/Backup of iMac20/.fseventsd/0000000020080fc9 (Input/output error) Apr 1 10:38:34 iMac20 kernel[0]: der First] Apr 1 10:38:33 iMac20 fseventsd[38]: failed to unlink old log file / Volumes/Backup of iMac20/.fseventsd/0000000020084845 (Input/output error) Apr 1 16:05:27 localhost kernel[0]: npvhash=4095 Apr 1 16:05:26 localhost com.apple.launchctl.System[2]: launchctl: Please convert the following to launchd: /etc/mach_init.d/chum.plist Apr 1 16:05:26 localhost com.apple.launchctl.System[2]: launchctl: Please convert the following to launchd: /etc/mach_init.d/ dashboardadvisoryd.plist Apr 1 16:05:26 localhost com.apple.launchctl.System[2]: launchctl: Please convert the following to launchd: /etc/mach_init.d/ pilotfish.plist Apr 1 16:05:26 localhost com.apple.launchd[1] (com.apple.distccdConfigd): Unknown key: SHAuthorizationRight Apr 1 16:05:26 localhost com.apple.launchd[1] (org.apache.httpd): Unknown key: SHAuthorizationRight Apr 1 16:05:26 localhost com.apple.launchd[1] (org.cups.cupsd): Unknown key: SHAuthorizationRight Apr 1 16:05:26 localhost com.apple.launchd[1] (org.ntp.ntpd): Unknown key: SHAuthorizationRight Apr 1 16:05:26 localhost DirectoryService[11]: Launched version 5.2 (v514.4) . . lots more normal startup system log items ================== During that 5.5 hour time warp, lots of stuff went on; I was listening to itunes music, surfing with safari, receiving & sending mail, normal time machine backups, etc., etc. How in blazes can the logs go completely silent for so long with no observable operational consequences? Has anyone here seen such behavior? Should I be concerned? I am really, really confounded by this. Note: This is NOT an April Fool's joke (unless somebody at Apple programmed this log silence to mess with terminal noobs). Richard From ecrist at secure-computing.net Tue Apr 1 17:54:55 2008 From: ecrist at secure-computing.net (Eric F Crist) Date: Tue Apr 1 17:56:30 2008 Subject: [X-Unix] Time Warp Hits System Logs In-Reply-To: References: Message-ID: <54C99EAB-AEBC-46F2-BE57-FE51FFB6C590@secure-computing.net> My guess would be that syslogd is dying. When this happens, check to see if syslogd is running. From Terminal, try: # netstat -a | grep syslog You should see something like: 3e1cdd0 dgram 0 0 3f045b0 0 5bf47f8 0 / var/run/syslog If not, syslog probably died. Restart it and you should be good to go. On Apr 1, 2008, at 6:37 PM, Richard Hartman wrote: > Cross-post apologies: I meant to send this to the x-unix list but > sent it to the x4u list by mistake... My bad. > ------------------------------- > Whilst playing around with Time Machine backups to a mounted AFP > volume earlier today, evidently there was some kind of system error > that was not reported or evident via the GUI but was recorded in the > system & console logs, as I just discovered some 5.5 hours after > they happened; nothing really remarkable about that, BUT... > > The thing is that All the console and system logs quit getting > updates at that instant. I just noticed this while I was looking at > the system log out of boredom. I was unable to do anything that > would generate a log update (for example, I initiated a Time Machine > backup which normally always reports progress to system; nothing). I > rebooted the system and the log entries began to update normally. > Here is the system log portion spanning the "missing" 5+ hours: > > ================== > . > . > lots of logged errors, like... > Apr 1 10:38:34 iMac20 kernel[0]: disk6s2: 0x14 (UNDEFINED). > Apr 1 10:38:33 iMac20 fseventsd[38]: failed to unlink old log file / > Volumes/Backup of iMac20/.fseventsd/00000000200749a5 (Input/output > error) > Apr 1 10:38:34 iMac20 kernel[0]: > Apr 1 10:38:33 iMac20 fseventsd[38]: failed to unlink old log file / > Volumes/Backup of iMac20/.fseventsd/0000000020076c6b (Input/output > error) > Apr 1 10:38:34 iMac20 kernel[0]: > Apr 1 10:38:33 iMac20 fseventsd[38]: failed to unlink old log file / > Volumes/Backup of iMac20/.fseventsd/0000000020079a9c (Input/output > error) > Apr 1 10:38:34 iMac20 kernel[0]: [FSLogMsgOrder Last] > Apr 1 10:38:33 iMac20 fseventsd[38]: failed to unlink old log file / > Volumes/Backup of iMac20/.fseventsd/000000002007bcea (Input/output > error) > Apr 1 10:38:34 iMac20 kernel[0]: disk6s2: 0x14 (UNDEFINED). > Apr 1 10:38:33 iMac20 fseventsd[38]: failed to unlink old log file / > Volumes/Backup of iMac20/.fseventsd/000000002007eb80 (Input/output > error) > Apr 1 10:38:34 iMac20 kernel[0]: > Apr 1 10:38:33 iMac20 fseventsd[38]: failed to unlink old log file / > Volumes/Backup of iMac20/.fseventsd/0000000020080fc9 (Input/output > error) > Apr 1 10:38:34 iMac20 kernel[0]: der First] > Apr 1 10:38:33 iMac20 fseventsd[38]: failed to unlink old log file / > Volumes/Backup of iMac20/.fseventsd/0000000020084845 (Input/output > error) > Apr 1 16:05:27 localhost kernel[0]: npvhash=4095 > Apr 1 16:05:26 localhost com.apple.launchctl.System[2]: launchctl: > Please convert the following to launchd: /etc/mach_init.d/chum.plist > Apr 1 16:05:26 localhost com.apple.launchctl.System[2]: launchctl: > Please convert the following to launchd: /etc/mach_init.d/ > dashboardadvisoryd.plist > Apr 1 16:05:26 localhost com.apple.launchctl.System[2]: launchctl: > Please convert the following to launchd: /etc/mach_init.d/ > pilotfish.plist > Apr 1 16:05:26 localhost com.apple.launchd[1] > (com.apple.distccdConfigd): Unknown key: SHAuthorizationRight > Apr 1 16:05:26 localhost com.apple.launchd[1] (org.apache.httpd): > Unknown key: SHAuthorizationRight > Apr 1 16:05:26 localhost com.apple.launchd[1] (org.cups.cupsd): > Unknown key: SHAuthorizationRight > Apr 1 16:05:26 localhost com.apple.launchd[1] (org.ntp.ntpd): > Unknown key: SHAuthorizationRight > Apr 1 16:05:26 localhost DirectoryService[11]: Launched version 5.2 > (v514.4) > . > . > lots more normal startup system log items > ================== > > During that 5.5 hour time warp, lots of stuff went on; I was > listening to itunes music, surfing with safari, receiving & sending > mail, normal time machine backups, etc., etc. > > How in blazes can the logs go completely silent for so long with no > observable operational consequences? Has anyone here seen such > behavior? Should I be concerned? I am really, really confounded by > this. > > Note: This is NOT an April Fool's joke (unless somebody at Apple > programmed this log silence to mess with terminal noobs). > > Richard > _______________________________________________ > X-Unix mailing list > X-Unix@listserver.themacintoshguy.com > http://listserver.themacintoshguy.com/mailman/listinfo/x-unix ----- Eric F Crist Secure Computing Networks From jerry at ieee.org Tue Apr 1 21:26:23 2008 From: jerry at ieee.org (Jerry Krinock) Date: Tue Apr 1 21:26:44 2008 Subject: [X-Unix] Time Warp Hits System Logs In-Reply-To: References: Message-ID: On 2008 Apr, 01, at 16:37, Richard Hartman wrote: > How in blazes can the logs go completely silent for so long with no > observable operational consequences? Has anyone here seen such > behavior? Should I be concerned? I am really, really confounded by > this. If this is Mac OS 10.5, I would add that I too have started "imagining" weird things in the new and improved Console for Leopard. Example: I do something which should create a log entry, look in Console.app, clear out the "Filter" field and see nothing. Reload. Sometimes that brings up the expected entry. Other times, I wait 2 minutes, reload again, and it appears. > Note: This is NOT an April Fool's joke (unless somebody at Apple > programmed this log silence to mess with terminal noobs). It's just not repeatable enough to be sure that I'm not imagining it just yet. From alex at underwares.org Tue Apr 1 21:33:18 2008 From: alex at underwares.org (Alexandre Gauthier) Date: Tue Apr 1 21:33:25 2008 Subject: [X-Unix] Time Warp Hits System Logs In-Reply-To: References: Message-ID: Le 08-04-02 ? 00:26, Jerry Krinock a ?crit : > > On 2008 Apr, 01, at 16:37, Richard Hartman wrote: > >> How in blazes can the logs go completely silent for so long with no >> observable operational consequences? Has anyone here seen such >> behavior? Should I be concerned? I am really, really confounded by >> this. > > If this is Mac OS 10.5, I would add that I too have started > "imagining" weird things in the new and improved Console for > Leopard. Example: I do something which should create a log entry, > look in Console.app, clear out the "Filter" field and see nothing. > Reload. Sometimes that brings up the expected entry. Other times, > I wait 2 minutes, reload again, and it appears. I noticed this as well on my G5, but not on my Mac Book Pro. 10.5 here too. > >> Note: This is NOT an April Fool's joke (unless somebody at Apple >> programmed this log silence to mess with terminal noobs). > > It's just not repeatable enough to be sure that I'm not imagining it > just yet. Not exactly related, but I don't use Console.app nearly enough to confirm it either. I use this: http://www.mulle-kybernetik.com/software/MkConsole/ It's basically a console widget on your desktop that, when configured correctly, blends in with the wallpaper, serving the purpose of a generic tail -n window. I find it really speeds up my diagnosis process when trying to find out what's borked. mkconsole i also available from MacPorts :) From seasoft at west.net Tue Apr 1 21:44:50 2008 From: seasoft at west.net (Richard Hartman) Date: Tue Apr 1 21:45:20 2008 Subject: [X-Unix] Time Warp Hits System Logs In-Reply-To: References: Message-ID: <18C8591E-C4FF-46A7-9823-8417CA3CCE61@west.net> On Apr 1, 2008, at 9:26 PM, Jerry Krinock wrote: > > On 2008 Apr, 01, at 16:37, Richard Hartman wrote: > >> How in blazes can the logs go completely silent for so long with no >> observable operational consequences? Has anyone here seen such >> behavior? Should I be concerned? I am really, really confounded by >> this. > > If this is Mac OS 10.5, I would add that I too have started > "imagining" weird things in the new and improved Console for > Leopard. Example: I do something which should create a log entry, > look in Console.app, clear out the "Filter" field and see nothing. > Reload. Sometimes that brings up the expected entry. Other times, > I wait 2 minutes, reload again, and it appears. > Yes, OS 10.5.2 on an intel iMac. Although I can't prove it since I did a reboot, Eric Christ has convinced me that my recent bizarre episode was probably caused by syslogd taking a powder... >> Note: This is NOT an April Fool's joke (unless somebody at Apple >> programmed this log silence to mess with terminal noobs). > > It's just not repeatable enough to be sure that I'm not imagining it > just yet. > I have to admit to noticing some other sporadic console weirdness, but had also chalked it up to my imagination. Richard From jerry at ieee.org Sun Apr 6 14:49:50 2008 From: jerry at ieee.org (Jerry Krinock) Date: Sun Apr 6 14:50:33 2008 Subject: [X-Unix] How to get working directory in a perl script? Message-ID: <2D2B4336-F545-4B0C-9C14-8300591FF3A3@ieee.org> Apparently, a perl script has a different "working" directory than the bash shell that spawned it, or something like that... ##### Script: ########################## #!/usr/bin/perl print "1. pwd is: $ENV{'PWD'}\n" ; my $newDir = "/Users/jk/Music" ; if (chdir $newDir) { print "Succeeded chdir to $newDir\n" ; } my $wdContents = `ls` ; print "wd contents:\n$wdContents\n" ; print "2. pwd is: $ENV{'PWD'}\n" ; ##### Actual Output: ################## 1. pwd is: /Users/jk Succeeded chdir to /Users/jk/Music wd contents: GarageBand iTunes 2. pwd is: /Users/jk ###################################### As you can see, the script did successfully change my working directory to /Users/jk/Music, but $ENV{'PWD'} is giving me /Users/jk. How can I get the correct answer? Thanks, Jerry Krinock From scruss at scruss.com Sun Apr 6 15:01:27 2008 From: scruss at scruss.com (Stewart C. Russell) Date: Sun Apr 6 15:01:58 2008 Subject: [X-Unix] How to get working directory in a perl script? In-Reply-To: <2D2B4336-F545-4B0C-9C14-8300591FF3A3@ieee.org> References: <2D2B4336-F545-4B0C-9C14-8300591FF3A3@ieee.org> Message-ID: <47F94837.9050605@scruss.com> Jerry Krinock wrote: > > As you can see, the script did successfully change my working directory > to /Users/jk/Music, but $ENV{'PWD'} is giving me /Users/jk. How can I > get the correct answer? use Cwd qw(chdir); Stewart From jerry at ieee.org Sun Apr 6 17:25:52 2008 From: jerry at ieee.org (Jerry Krinock) Date: Sun Apr 6 17:26:01 2008 Subject: [X-Unix] How to get working directory in a perl script? In-Reply-To: <47F94837.9050605@scruss.com> References: <2D2B4336-F545-4B0C-9C14-8300591FF3A3@ieee.org> <47F94837.9050605@scruss.com> Message-ID: <0803ADD1-61A8-43BB-992F-0BF40965115F@ieee.org> On 2008 Apr, 06, at 15:01, Stewart C. Russell wrote: > use Cwd qw(chdir); Thank you, Stewart. It works. From the CPAN documentation [1], under subhead "$ENV{PWD}", I read that "If you ask to override your chdir() built-in function, use Cwd qw(chdir); then your PWD environment variable will be kept up to date. Note that it will only be kept up to date if all packages which use chdir import it from Cwd." Sheesh. "What will they think of next??" I am going to our little greenhouse to plant some more lettuce seeds now. [1] http://search.cpan.org/~kwilliams/PathTools-3.2701/Cwd.pm From jerry at ieee.org Wed Apr 16 19:57:19 2008 From: jerry at ieee.org (Jerry Krinock) Date: Wed Apr 16 19:57:27 2008 Subject: [X-Unix] How make launchd stop trying to launch nonexistent program? Message-ID: <735A47D6-5C33-477F-BED4-48AD6903FF33@ieee.org> To make a long story short, I've got my launchd trying to launch a program that does not exist. I get this in Console.app every 10 seconds: 08/04/16 18:18:08 com.apple.launchd[1] (com.example.BetterAuthorizationSample[1146]) posix_spawnp("/Library/ PrivilegedHelperTools/com.example.BetterAuthorizationSample", ...): No such file or directory 08/04/16 18:18:08 com.apple.launchd[1] (com.example.BetterAuthorizationSample[1146]) Exited with exit code: 1 08/04/16 18:18:08 com.apple.launchd[1] (com.example.BetterAuthorizationSample) Throttling respawn: Will start in 10 seconds I want to stop this. Killing the program which requested the launch does not help; apparently launchd is doing this repeatedly under its own power. I commanded launchctl to 'list', and found what looked like the offending process label which was "0x112e20.BetterAuthorizat". That's a rather strange label but it is correct, because if I mis-spell it in a command to launchctl, I get "No such process", but if I spell it exactly like that, it "takes" it. This command: launchctl stop 0x112e20.BetterAuthorizat had no effect. This command: launchctl remove 0x112e20.BetterAuthorizat removed it from 'launchctl list' output, but did not stop the attempted launch every 10 seconds. I don't see any other ideas in man launchctl. Log-out/in does not stop it. Only a restart will stop the repeated attempted launching. Restarts were for Mac OS 9, though. Does anyone know the smart way to stop this? Thanks, Jerry From ecrist at secure-computing.net Wed Apr 16 20:12:26 2008 From: ecrist at secure-computing.net (=?utf-8?B?RXJpYyBGIENyaXN0?=) Date: Wed Apr 16 20:15:51 2008 Subject: [X-Unix] How make launchd stop trying to launch nonexistent program? In-Reply-To: <735A47D6-5C33-477F-BED4-48AD6903FF33@ieee.org> References: <735A47D6-5C33-477F-BED4-48AD6903FF33@ieee.org> Message-ID: <1037140667-1208402142-cardhu_decombobulator_blackberry.rim.net-2113996465-@bxe130.bisx.prod.on.blackberry> Sighup the launchd process maybe. If that doesn't help, restart the daemon entirely. I'll look more into it if you don't have a solution by tomorrow morning. --- Eric F Crist Secure Computing Networks -----Original Message----- From: Jerry Krinock Date: Wed, 16 Apr 2008 19:57:19 To:Mac OS X Unix Subject: [X-Unix] How make launchd stop trying to launch nonexistent program? To make a long story short, I've got my launchd trying to launch a program that does not exist. I get this in Console.app every 10 seconds: 08/04/16 18:18:08 com.apple.launchd[1] (com.example.BetterAuthorizationSample[1146]) posix_spawnp("/Library/ PrivilegedHelperTools/com.example.BetterAuthorizationSample", ...): No such file or directory 08/04/16 18:18:08 com.apple.launchd[1] (com.example.BetterAuthorizationSample[1146]) Exited with exit code: 1 08/04/16 18:18:08 com.apple.launchd[1] (com.example.BetterAuthorizationSample) Throttling respawn: Will start in 10 seconds I want to stop this. Killing the program which requested the launch does not help; apparently launchd is doing this repeatedly under its own power. I commanded launchctl to 'list', and found what looked like the offending process label which was "0x112e20.BetterAuthorizat". That's a rather strange label but it is correct, because if I mis-spell it in a command to launchctl, I get "No such process", but if I spell it exactly like that, it "takes" it. This command: launchctl stop 0x112e20.BetterAuthorizat had no effect. This command: launchctl remove 0x112e20.BetterAuthorizat removed it from 'launchctl list' output, but did not stop the attempted launch every 10 seconds. I don't see any other ideas in man launchctl. Log-out/in does not stop it. Only a restart will stop the repeated attempted launching. Restarts were for Mac OS 9, though. Does anyone know the smart way to stop this? Thanks, Jerry _______________________________________________ X-Unix mailing list X-Unix@listserver.themacintoshguy.com http://listserver.themacintoshguy.com/mailman/listinfo/x-unix From jerry at ieee.org Wed Apr 16 21:12:23 2008 From: jerry at ieee.org (Jerry Krinock) Date: Wed Apr 16 21:12:35 2008 Subject: [X-Unix] How make launchd stop trying to launch nonexistent program? In-Reply-To: <1037140667-1208402142-cardhu_decombobulator_blackberry.rim.net-2113996465-@bxe130.bisx.prod.on.blackberry> References: <735A47D6-5C33-477F-BED4-48AD6903FF33@ieee.org> <1037140667-1208402142-cardhu_decombobulator_blackberry.rim.net-2113996465-@bxe130.bisx.prod.on.blackberry> Message-ID: <9B4A79AD-BE3D-4BFC-84BC-0ECF9D1BD79B@ieee.org> On 2008 Apr, 16, at 20:12, Eric F Crist wrote: > Sighup the launchd process maybe. I typed into Terminal "kill -1 1" since HUP is signal 1 and launchd's pid=1. Did not help. > If that doesn't help, restart the daemon entirely. Not sure what you mean by that, but I tried "kill -9 1". Also did not help. I think maybe launchd ignored the signal since after doing this it was still running and still had the same pid=1. > I'll look more into it if you don't have a solution by tomorrow > morning. Didn't find anything yet. I'm going to bed soon myself. Thanks Eric, Jerry From ecrist at secure-computing.net Thu Apr 17 05:19:40 2008 From: ecrist at secure-computing.net (Eric F Crist) Date: Thu Apr 17 05:20:20 2008 Subject: [X-Unix] How make launchd stop trying to launch nonexistent program? In-Reply-To: <9B4A79AD-BE3D-4BFC-84BC-0ECF9D1BD79B@ieee.org> References: <735A47D6-5C33-477F-BED4-48AD6903FF33@ieee.org> <1037140667-1208402142-cardhu_decombobulator_blackberry.rim.net-2113996465-@bxe130.bisx.prod.on.blackberry> <9B4A79AD-BE3D-4BFC-84BC-0ECF9D1BD79B@ieee.org> Message-ID: According to man launchd, a separate launchd process is started for each application started and controlled by launchd. As such, I get the following output: ecrist@swordfish:~-> ps auxwww |grep launch ecrist 110 0.0 0.2 391468 3728 ?? S 6:56PM 0:00.16 /System/Library/CoreServices/AirPort Base Station Agent.app/ Contents/MacOS/AirPort Base Station Agent -launchd ecrist 106 0.0 0.0 599792 652 ?? Ss 6:56PM 0:01.05 /sbin/launchd _mdnsresponder 20 0.0 0.1 77312 1264 ?? Ss 6:56PM 0:00.50 /usr/sbin/mDNSResponder -launchd ecrist 1690 0.0 0.0 599780 400 s000 R+ 7:13AM 0:00.00 grep launch root 1 0.0 0.0 600816 560 ?? Ss 6:56PM 0:01.30 /sbin/launchd Do you see your process when you run a ps auxwww? You can see above that there is a launchd proccess (pid 106) and another process, AirPort Base Station (pid 110). Both are owned by my user, and since they're pretty close to the same pid, I'd make the assumption they're related. Look for this type of output on your system and see if you can't kill the launchd process responsible. The funny thing about launchd is that Apple actually recommends *against* using it, and instead asks you to use whatever programs own daemon instead. From the launchd man page: Where possible, it is preferable for jobs to launch on demand based on criteria specified in their respective configuration files. HTH Eric On Apr 16, 2008, at 11:12 PM, Jerry Krinock wrote: > > On 2008 Apr, 16, at 20:12, Eric F Crist wrote: > >> Sighup the launchd process maybe. > > I typed into Terminal "kill -1 1" since HUP is signal 1 and > launchd's pid=1. Did not help. > >> If that doesn't help, restart the daemon entirely. > > Not sure what you mean by that, but I tried "kill -9 1". Also did > not help. I think maybe launchd ignored the signal since after > doing this it was still running and still had the same pid=1. > >> I'll look more into it if you don't have a solution by tomorrow >> morning. > > Didn't find anything yet. I'm going to bed soon myself. > > Thanks Eric, > > Jerry > > _______________________________________________ > X-Unix mailing list > X-Unix@listserver.themacintoshguy.com > http://listserver.themacintoshguy.com/mailman/listinfo/x-unix ----- Eric F Crist Secure Computing Networks From G.J.Perrin at bton.ac.uk Thu Apr 17 05:46:43 2008 From: G.J.Perrin at bton.ac.uk (Graham Perrin) Date: Thu Apr 17 05:46:54 2008 Subject: [X-Unix] How make launchd stop trying to launch nonexistent program? In-Reply-To: <735A47D6-5C33-477F-BED4-48AD6903FF33@ieee.org> References: <735A47D6-5C33-477F-BED4-48AD6903FF33@ieee.org> Message-ID: <398683E5-EA5C-4BBF-B887-EA6FA36B44F0@bton.ac.uk> On 17 Apr 2008, at 03:57, Jerry Krinock wrote: > Does anyone know the smart way to stop this? Lingon , maybe? From jerry at ieee.org Thu Apr 17 05:56:49 2008 From: jerry at ieee.org (Jerry Krinock) Date: Thu Apr 17 05:57:28 2008 Subject: [X-Unix] How make launchd stop trying to launch nonexistent program? In-Reply-To: References: <735A47D6-5C33-477F-BED4-48AD6903FF33@ieee.org> <1037140667-1208402142-cardhu_decombobulator_blackberry.rim.net-2113996465-@bxe130.bisx.prod.on.blackberry> <9B4A79AD-BE3D-4BFC-84BC-0ECF9D1BD79B@ieee.org> Message-ID: <402B45E9-205A-4386-8B15-6661A5052051@ieee.org> On 2008 Apr, 17, at 5:19, Eric F Crist wrote: > According to man launchd, a separate launchd process is started for > each application started and controlled by launchd. As such, I get > the following output: > > ecrist@swordfish:~-> ps auxwww |grep launch > ecrist 110 0.0 0.2 391468 3728 ?? S 6:56PM > 0:00.16 /System/Library/CoreServices/AirPort Base Station Agent.app/ > Contents/MacOS/AirPort Base Station Agent -launchd > ecrist 106 0.0 0.0 599792 652 ?? Ss 6:56PM > 0:01.05 /sbin/launchd > _mdnsresponder 20 0.0 0.1 77312 1264 ?? Ss 6:56PM > 0:00.50 /usr/sbin/mDNSResponder -launchd > ecrist 1690 0.0 0.0 599780 400 s000 R+ 7:13AM > 0:00.00 grep launch > root 1 0.0 0.0 600816 560 ?? Ss 6:56PM > 0:01.30 /sbin/launchd > > Do you see your process when you run a ps auxwww? No, I only see two /sbin/launchd processes, very similar to yours... Jerrys-Mac-Mini:~ jk$ ps auxww | grep launchd nobody 124 0.0 0.0 601068 692 ?? Ss 8:36PM 0:00.01 /System/Library/PrivateFrameworks/MobileDevice.framework/ Versions/A/Resources/usbmuxd -launchd jk 91 0.0 0.2 406216 3192 ?? S 8:35PM 0:00.14 /System/Library/CoreServices/AirPort Base Station Agent.app/ Contents/MacOS/AirPort Base Station Agent -launchd jk 85 0.0 0.0 599792 560 ?? Ss 8:35PM 0:03.78 /sbin/launchd _mdnsresponder 17 0.0 0.1 601584 1196 ?? Ss 8:35PM 0:00.13 /usr/sbin/mDNSResponder -launchd jk 4909 0.0 0.0 599780 464 s001 R+ 5:43AM 0:00.00 grep launchd root 1 0.0 0.0 600816 592 ?? Ss 8:34PM 0:55.65 /sbin/launchd Actually I believe it is pid=1 which is causing the problem since if I examine the complete console output I'm still getting every 10 seconds, com.apple.launchd[1] (com.example.BetterAuthorizationSample[4963]) posix_spawnp("/Library/PrivilegedHelperTools/ com.example.BetterAuthorizationSample", ...): No such file or directory com.apple.launchd[1] (com.example.BetterAuthorizationSample[4963]) Exited with exit code: 1 com.apple.launchd[1] (com.example.BetterAuthorizationSample) Throttling respawn: Will start in 10 seconds That [1] is indicating the pid. > HTH I'm hoping too. I'm also working at the other problem, which is the nonexistence of this program that launchd is looking for. Still soliciting clues. Thanks again, Jerry From jerry at ieee.org Thu Apr 17 06:02:17 2008 From: jerry at ieee.org (Jerry Krinock) Date: Thu Apr 17 06:02:25 2008 Subject: [X-Unix] How make launchd stop trying to launch nonexistent program? In-Reply-To: <398683E5-EA5C-4BBF-B887-EA6FA36B44F0@bton.ac.uk> References: <735A47D6-5C33-477F-BED4-48AD6903FF33@ieee.org> <398683E5-EA5C-4BBF-B887-EA6FA36B44F0@bton.ac.uk> Message-ID: <6D5E99EF-8191-4E29-B9D4-E0D225B4D54C@ieee.org> On 2008 Apr, 17, at 5:46, Graham Perrin wrote: > Lingon , maybe? Thanks but, no that seems to be for creating launchd configuration plists, which I already have. I did try ^removing^ the launchd configuration plist for this nonexisting program, but, not surprisingly, that did not stop the repeated attempts to launch it. From ecrist at secure-computing.net Thu Apr 17 06:13:11 2008 From: ecrist at secure-computing.net (Eric F Crist) Date: Thu Apr 17 06:13:51 2008 Subject: [X-Unix] How make launchd stop trying to launch nonexistent program? In-Reply-To: <402B45E9-205A-4386-8B15-6661A5052051@ieee.org> References: <735A47D6-5C33-477F-BED4-48AD6903FF33@ieee.org> <1037140667-1208402142-cardhu_decombobulator_blackberry.rim.net-2113996465-@bxe130.bisx.prod.on.blackberry> <9B4A79AD-BE3D-4BFC-84BC-0ECF9D1BD79B@ieee.org> <402B45E9-205A-4386-8B15-6661A5052051@ieee.org> Message-ID: <76528B4C-6340-4D32-A144-2000487CB4A1@secure-computing.net> Jerry, I would punt. Unless this is a production server, just reboot. I'll keep looking for the 'right' way to do this, however. Eric On Apr 17, 2008, at 7:56 AM, Jerry Krinock wrote: > > On 2008 Apr, 17, at 5:19, Eric F Crist wrote: > >> According to man launchd, a separate launchd process is started for >> each application started and controlled by launchd. As such, I get >> the following output: >> >> ecrist@swordfish:~-> ps auxwww |grep launch >> ecrist 110 0.0 0.2 391468 3728 ?? S 6:56PM >> 0:00.16 /System/Library/CoreServices/AirPort Base Station Agent.app/ >> Contents/MacOS/AirPort Base Station Agent -launchd >> ecrist 106 0.0 0.0 599792 652 ?? Ss 6:56PM >> 0:01.05 /sbin/launchd >> _mdnsresponder 20 0.0 0.1 77312 1264 ?? Ss >> 6:56PM 0:00.50 /usr/sbin/mDNSResponder -launchd >> ecrist 1690 0.0 0.0 599780 400 s000 R+ 7:13AM >> 0:00.00 grep launch >> root 1 0.0 0.0 600816 560 ?? Ss 6:56PM >> 0:01.30 /sbin/launchd >> >> Do you see your process when you run a ps auxwww? > > No, I only see two /sbin/launchd processes, very similar to yours... > > Jerrys-Mac-Mini:~ jk$ ps auxww | grep launchd > nobody 124 0.0 0.0 601068 692 ?? Ss 8:36PM > 0:00.01 /System/Library/PrivateFrameworks/MobileDevice.framework/ > Versions/A/Resources/usbmuxd -launchd > jk 91 0.0 0.2 406216 3192 ?? S 8:35PM > 0:00.14 /System/Library/CoreServices/AirPort Base Station Agent.app/ > Contents/MacOS/AirPort Base Station Agent -launchd > jk 85 0.0 0.0 599792 560 ?? Ss 8:35PM > 0:03.78 /sbin/launchd > _mdnsresponder 17 0.0 0.1 601584 1196 ?? Ss 8:35PM > 0:00.13 /usr/sbin/mDNSResponder -launchd > jk 4909 0.0 0.0 599780 464 s001 R+ 5:43AM > 0:00.00 grep launchd > root 1 0.0 0.0 600816 592 ?? Ss 8:34PM > 0:55.65 /sbin/launchd > > Actually I believe it is pid=1 which is causing the problem since if > I examine the complete console output I'm still getting every 10 > seconds, > > com.apple.launchd[1] (com.example.BetterAuthorizationSample[4963]) > posix_spawnp("/Library/PrivilegedHelperTools/ > com.example.BetterAuthorizationSample", ...): No such file or > directory > com.apple.launchd[1] (com.example.BetterAuthorizationSample[4963]) > Exited with exit code: 1 > com.apple.launchd[1] (com.example.BetterAuthorizationSample) > Throttling respawn: Will start in 10 seconds > > That [1] is indicating the pid. > >> HTH > > I'm hoping too. I'm also working at the other problem, which is the > nonexistence of this program that launchd is looking for. Still > soliciting clues. > > Thanks again, > > Jerry > _______________________________________________ > X-Unix mailing list > X-Unix@listserver.themacintoshguy.com > http://listserver.themacintoshguy.com/mailman/listinfo/x-unix ----- Eric F Crist Secure Computing Networks From alex at underwares.org Thu Apr 17 06:46:40 2008 From: alex at underwares.org (Alexandre Gauthier) Date: Thu Apr 17 06:47:04 2008 Subject: [X-Unix] How make launchd stop trying to launch nonexistent program? In-Reply-To: <6D5E99EF-8191-4E29-B9D4-E0D225B4D54C@ieee.org> References: <735A47D6-5C33-477F-BED4-48AD6903FF33@ieee.org> <398683E5-EA5C-4BBF-B887-EA6FA36B44F0@bton.ac.uk> <6D5E99EF-8191-4E29-B9D4-E0D225B4D54C@ieee.org> Message-ID: <1208440000.15854.2.camel@deimos> Le jeudi 17 avril 2008 ? 06:02 -0700, Jerry Krinock a ?crit : > On 2008 Apr, 17, at 5:46, Graham Perrin wrote: > > > Lingon , maybe? > > Thanks but, no that seems to be for creating launchd configuration > plists, which I already have. I did try ^removing^ the launchd > configuration plist for this nonexisting program, but, not > surprisingly, that did not stop the repeated attempts to launch it. Have you tried 'launchctl remove' to remove the plist? This usually also stops the job and process. Have you also tried refering to the process as "com.example.BetterAuthorizationSample" instead of the hexadecimal name? -- Alexandre Gauthier - Network Analyst / Analyste R?seau The human brain operates at only 10% of its capacity. The rest is overhead for the operating system. From subscriber at gloaming.com Thu Apr 17 08:29:49 2008 From: subscriber at gloaming.com (James Bucanek) Date: Thu Apr 17 08:31:05 2008 Subject: [X-Unix] How make launchd stop trying to launch nonexistent program? In-Reply-To: <6D5E99EF-8191-4E29-B9D4-E0D225B4D54C@ieee.org> Message-ID: Jerry Krinock wrote (Thursday, April 17, 2008 6:02 AM -0700): >I did try ^removing^ the launchd configuration plist for this >nonexisting program, but, not surprisingly, that did not stop >the repeated attempts to launch it. Removing the .plist will have no effect once the configuration file has been read by launchd when it started up. You need to unload, remove, or stop the job via launchctl (see man launchctl). For the record, the correct way of removing a .plist is use 'launchctl unload '. If you still have the .plist you can probably stop the job using 'launchctl remove ' (look in the .plist file to find the