[CentOS] Re: Stopping a server not controled by service

Robert Moskowitz rgm at htt-consult.com
Tue Jul 15 22:47:15 UTC 2008


oops

Scott Silva wrote:
> on 7-15-2008 2:36 PM Robert Moskowitz spake the following:
>>
>>
>> Scott Silva wrote:
>>> on 7-15-2008 1:05 PM Robert Moskowitz spake the following:
>>>> Scott Silva wrote:
>>>>> on 7-15-2008 12:33 PM Robert Moskowitz spake the following:
>>>>>> Miredo is run as a server from the command line:
>>>>>>
>>>>>> /usr/sbin/miredo
>>>>>>
>>>>>> The man page says the signal SIGTERM stops the server.
>>>>>>
>>>>>> How do I send SIGTERM to the server?  Or SIGHUP, as I want to 
>>>>>> make a change to the config file.
>>>>>>
>>>>>>
>>>>>> And once I get this as I want it, how do I run it at system boot?
>>>>> You will have to make a sys V init script for it. You can probably 
>>>>> use an existing script and edit it to suit your program, or there 
>>>>> is example in /usr/share/doc/initscripts-xxxxxx directory that you 
>>>>> should be able to hack at. That will also help you to get lock 
>>>>> files and pid files going for it if you need them.
>>>> Thanks.   Something else to learn.  I have been trying to document 
>>>> all that I have been using (skipping what I have discarded, as I 
>>>> don't know if I know it).
>>>>
>>>> It has pid files:  /var/run/miredo.pid
>>>>
>>>> How would I get lock files?
>>>
>>> You create lock files as a simple way to not run a process more than 
>>> one at a time.
>>
>> I was asking how I make/control a lock file when the rpm provides a 
>> binary run module and the man page does not mention a lock file.  How 
>> do I find out if there is a lock file?  How do I get one working?  Do 
>> I necessarily need one, perhaps the binary determines its running 
>> status before trying to start a second copy?  Actually, I think I 
>> discovered that miredo will not start a second copy, oops.
>>
>>>>> The other choice is to add a line to /etc/rc.d/rc.local, but that 
>>>>> won't give you control with the system command.
>>>> I MUST include this in my docs.  I keep forgetting the file name.  
>>>> This will probably be good enough, as once I get it working, it 
>>>> will be an auto start.  And less effort than the first point.
>>>>
>>> Yes, rc.local will be easier to get the service running, but if you 
>>> are creating something for distribution, service miredo restart can 
>>> be easier for a noobie then kill -HUP (what was that pid# again?)
>> Miredo comes from sourceforge.  Fortunately, I do not have to create 
>> it.....
>>>
> Here is an easier option.
> http://dag.wieers.com/rpm/packages/miredo/ 
I ment rpmforge which is how I access dag's stuff per the Centos wiki, 
giving me:

miredo-1.0.6-1.el5.rf.i386.rpm

So I am running it.  I am now fighting with routing.  All eth1 has is a 
Scope:Link address, yet ::/0 is has a metric of 1024 to it, while the 
Teredo route has a metric of 1029, so I am not getting to Teredo relay.  
Only can access other Teredo hosts over the Teredo interface.  Something 
is not right yet:

route -A inet6 -n

Kernel IPv6 routing table
Destination                                 Next 
Hop                                Flags Metric Ref    Use Iface
2001::/32                                   
::                                      U     256    0        0 teredo 
fe80::/64                                   
::                                      U     256    0        0 eth1   
fe80::/64                                   
::                                      U     256    0        0 teredo 
::/0                                        
fe80::a180:bc7:2364:5feb                UGDA  1024   126       0 eth1   
::/0                                        
::                                      U     1029   0        0 teredo 
::1/128                                     
::                                      U     0      0        1 lo     
2001:0:53aa:64c:0:7741:b75b:47b9/128        
::                                      U     0      0        1 lo     
fe80::ffff:ffff:ffff/128                    
::                                      U     0      0        1 lo     
fe80::21b:77ff:fe43:978/128                 
::                                      U     0      37       1 lo     
ff02::1/128                                 
ff02::1                                 UC    0      1        0 eth1   
ff02::2/128                                 
ff02::2                                 UC    0      5        0 eth1   
ff02::c/128                                 
ff02::c                                 UC    0      29       0 eth1   
ff02::16/128                                
ff02::16                                UC    0      33       0 eth1   
ff02::fb/128                                
ff02::fb                                UC    0      114       0 eth1   
ff02::1:2/128                               
ff02::1:2                               UC    0      699       0 eth1   
ff02::1:3/128                               
ff02::1:3                               UC    0      2905       0 eth1   
ff02::1:ff03:10a7/128                       
ff02::1:ff03:10a7                       UC    0      1        0 eth1   
ff02::1:ff10:497/128                        
ff02::1:ff10:497                        UC    0      1        0 eth1   
ff02::1:ff1d:a753/128                       
ff02::1:ff1d:a753                       UC    0      1        0 eth1   
ff02::1:ff3a:3dac/128                       
ff02::1:ff3a:3dac                       UC    0      1        0 eth1   
ff02::1:ff64:5feb/128                       
ff02::1:ff64:5feb                       UC    0      41       0 eth1   
ff02::1:ff7e:6072/128                       
ff02::1:ff7e:6072                       UC    0      1        0 eth1   
ff02::1:ffa0:4931/128                       
ff02::1:ffa0:4931                       UC    0      3        0 eth1   
ff02::1:ffa5:59cd/128                       
ff02::1:ffa5:59cd                       UC    0      3        0 eth1   
ff02::1:ffef:fb68/128                       
ff02::1:ffef:fb68                       UC    0      1        0 eth1   
ff00::/8                                    
::                                      U     256    0        0 eth1   
ff00::/8                                    
::                                      U     256    0        0 teredo 





More information about the CentOS mailing list