How to remove/unload anonymous job labels?

[Conrad Taylor]

Hi, could someone tell me how to remove jobs which have labels like to the following:

353 - 0x10c8d0.mysqld

353 - 0x10b250.mysqld

BTW, I have tried the following:

sudo launchctl stop 0x10c8d0.mysqld

sudo launchctl stop 0x10b250.mysqld

However, they seem to persist after the above command has been invoked.

-Conrad

_______________________________________________
launchd-dev mailing list
launchd-dev@...
http://lists.macosforge.org/mailman/listinfo.cgi/launchd-dev

[Damien Sorresso]

On Jul 16, 2009, at 4:05 AM, Conrad Taylor wrote:

> Hi, could someone tell me how to remove jobs which have labels like  
> to the following:
>
> 353 - 0x10c8d0.mysqld
> 353 - 0x10b250.mysqld
>
> BTW, I have tried the following:
>
> sudo launchctl stop 0x10c8d0.mysqld
> sudo launchctl stop 0x10b250.mysqld
>
> However, they seem to persist after the above command has been  
> invoked.

launchd does not control those jobs. Those entries are purely for  
bookkeeping purposes. Pay them no mind.
--
Damien Sorresso
BSD Engineering
Apple Inc.



_______________________________________________
launchd-dev mailing list
launchd-dev@...
http://lists.macosforge.org/mailman/listinfo.cgi/launchd-dev

[Conrad Taylor]

On Thu, Jul 16, 2009 at 9:28 AM, Damien Sorresso <dsorresso@...> wrote:

On Jul 16, 2009, at 4:05 AM, Conrad Taylor wrote:

Hi, could someone tell me how to remove jobs which have labels like to the following:

353     -       0x10c8d0.mysqld
353     -       0x10b250.mysqld

BTW, I have tried the following:

sudo launchctl stop 0x10c8d0.mysqld
sudo launchctl stop 0x10b250.mysqld

However, they seem to persist after the above command has been invoked.

I have created a plist for MySQL that should start on demand on PowerMac G5 using Mac OS 10.5.7.  However, when I look at the process list, I'm seeing the following:

  116   ??  S      0:00.04 /bin/sh ./bin/mysqld_safe --datadir=/usr/local/mysql/data --pid-file=/usr/local/mysql/data/darnoc-desktop.local.pid

  143   ??  S      0:01.61 /usr/local/mysql/bin/mysqld --basedir=/usr/local/mysql --datadir=/usr/local/mysql/data --user=mysql --pid-file=/usr/local/mysql/data/darnoc-desktop.local.pid

Note:  After rebooting the machine, I'm seeing the following:

sudo launchctl list | grep mysql

143 - 0x10c5d0.mysqld

143 - 0x10b430.mysqld

Now, when I perform the following on MacBook Pro:

sudo launchctl unload -w /opt/local/etc/LaunchDaemons/org.macports.mysql5/org.macports.mysql5.plist

sudo launchctl list | grep mysql

<no results>

sudo launchctl load -w /opt/local/etc/LaunchDaemons/org.macports.mysql5/org.macports.mysql5.plist

sudo launchctl list | grep mysql

232 - 0x100119dc0.anonymous.mysqld

202 - org.macports.mysql5

Would it be possible to put job in a bad state if you edit its plist file while it's loaded?  At this time, I

can connect to the MySQL process without getting a connection error even when the job is loaded.

-Conrad

_______________________________________________
launchd-dev mailing list
launchd-dev@...
http://lists.macosforge.org/mailman/listinfo.cgi/launchd-dev

[Damien Sorresso]

On Jul 16, 2009, at 10:41 PM, Conrad Taylor wrote:

> I have created a plist for MySQL that should start on demand on  
> PowerMac G5 using Mac OS 10.5.7.  However, when I look at the  
> process list, I'm seeing the following:
>
>   116   ??  S      0:00.04 /bin/sh ./bin/mysqld_safe --datadir=/usr/
> local/mysql/data --pid-file=/usr/local/mysql/data/darnoc-
> desktop.local.pid
>   143   ??  S      0:01.61 /usr/local/mysql/bin/mysqld --basedir=/
> usr/local/mysql --datadir=/usr/local/mysql/data --user=mysql --pid-
> file=/usr/local/mysql/data/darnoc-desktop.local.pid
>
> Note:  After rebooting the machine, I'm seeing the following:
>
> sudo launchctl list | grep mysql
>
> 143 - 0x10c5d0.mysqld
> 143 - 0x10b430.mysqld

I'm betting that mysqld did something that launchd jobs aren't  
supposed to do, like calling daemon(2) or the moral equivalent by fork
(2)ing and then exiting the parent.

> Now, when I perform the following on MacBook Pro:
>
> sudo launchctl unload -w /opt/local/etc/LaunchDaemons/
> org.macports.mysql5/org.macports.mysql5.plist
>
> sudo launchctl list | grep mysql
>
> <no results>

You unloaded the job, so that's to be expected.

> sudo launchctl load -w /opt/local/etc/LaunchDaemons/
> org.macports.mysql5/org.macports.mysql5.plist
>
> sudo launchctl list | grep mysql
>
> 232 - 0x100119dc0.anonymous.mysqld
> 202 - org.macports.mysql5

mysqld probably fork(2)ed, and the child tried talking to launchd.  
That's where the anonymous job comes from.

> Would it be possible to put job in a bad state if you edit its plist  
> file while it's loaded?

No. Your job isn't in a bad state.

> At this time, I
> can connect to the MySQL process without getting a connection error  
> even when the job is loaded.

You're supposed to be able to connect to the server when the job is  
loaded. What exactly is the bug you're experiencing?
--
Damien Sorresso
BSD Engineering
Apple Inc.



_______________________________________________
launchd-dev mailing list
launchd-dev@...
http://lists.macosforge.org/mailman/listinfo.cgi/launchd-dev