Supervise log processes

General Interworx Control Panel Info General Inquries
1

Hello,

I have a lot of processes running under supervise

…
5241 ? S 0:00 | _ supervise log
5293 ? S 0:06 | | _ multilog t ./main
5243 ? S 0:00 | _ supervise log
5283 ? S 0:00 | | _ multilog t ./main
5245 ? S 0:00 | _ supervise log
5282 ? S 0:00 | | _ multilog t ./main
5247 ? S 0:00 | _ supervise log
5275 ? S 0:00 | | _ multilog t ./main
5249 ? S 0:00 | _ supervise log
5278 ? S 0:00 | | _ multilog t ./main
5251 ? S 0:00 | _ supervise log
5274 ? S 0:00 | | _ multilog t ./main
5253 ? S 0:00 | _ supervise log
5273 ? S 0:00 | | _ multilog t ./main
5255 ? S 0:00 | _ supervise log
5320 ? S 0:00 | | _ multilog t ./main
5257 ? S 0:00 | _ supervise log
5306 ? S 0:00 | | _ multilog t ./main
5259 ? S 0:00 | _ supervise log
5300 ? S 0:00 | | _ multilog t ./main
…

Does somebody know what are these processes ?
Is it safe to kill them ?

Thanks

Pascal

2

They are normal pascal, they are for the logging of dns, mail etc. You can’t directly kill them either, you have to put a ‘down’ file in each log dir to tell them not to start on boot along with doing a ‘svc -d .’ in each log dir.

Chris

3

Thanks chris

Ok I understand that I didn’t explain very well.

you have to put a ‘down’ file in each log dir to tell them not to start on boot along with doing a ‘svc -d .’ in each log dir

I know this but, for me the pbm come from nodeworx. Ok, let me explain why.
I have stopped in nodeworx a lot of tinydns server.

Normally, the

4115 ? S 0:00 | _ supervise log
4164 ? S 0:00 | | _ multilog t ./main

come with something like

4116 ? S 0:00 | _ supervise tinydns-207.150.178.97
4141 ? S 0:00 | | _ /usr/bin/tinydns

So it means that in /service/ I should have a

/tinydns-207.150.178.97/log/main

So, you right, if I wanted to stop the log I should go in

/tinydns-207.150.178.97/log/main

and type svc -d

Stop me if I’m false.

But in my previous case, as I have stopped the tinydns from nodeworx, I do not have any longer in /service/ some files like

/tinydns-207.150.178.97/log/main

in fact I have only 4 directories like this. 2 are the one I have created to sync the dns from all my others boxes to this one and the 2 others are from nodeworx.

It’s like, nodeworx had deleted all directories in /service/ for the tinydns I stopped, but without stop the log. So now I have some

5253 ? S 0:00 | _ supervise log
5273 ? S 0:00 | | _ multilog t ./main

alone, and I can’t stop them, as I do not have a directory log for each of them. In fact I do not have any. So for me, nodeworx delete the directories, stop the tinydns svc but not the log. And now I can’t stop them cleanly.

The more strange, is that I have rebooted my box.

I hope I’ve been understanding.

Of course do not hesitate to tell me I completly false :-p

Pascal

4

ahhhhh :), understanding now. This may be a bug in the deactivation of the dns services and I’ll check it out. The dns interface should kill both, but it may just be killing the main tinydns instance and not the logging instnace.

Chris

5

ok cool :slight_smile:

So what is the cleanest solution to stop them ?

a kill - 9 pid ?

Thanks

Pascal

6

unfortunatley the cleanest is to reboot. kill’ing them won’t do anything except confuse svscan and supervise.

Chris