1 |
Fernando Rodriguez wrote: |
2 |
> On Thursday, September 03, 2015 8:47:34 PM Dale wrote: |
3 |
> |
4 |
> I don't know if this will help or not but don't forget the zap option. |
5 |
> |
6 |
> root@fireball / # /etc/init.d/dhcpcd <tab twice> |
7 |
> broken ineed iuse needsme pause restart start status |
8 |
> stop usesme zap |
9 |
> root@fireball / # /etc/init.d/dhcpcd |
10 |
> |
11 |
> It's been a long time since I used it but if I recall correctly that |
12 |
> resets the status. I think it stops and deletes any files that stores |
13 |
> its run status. |
14 |
> |
15 |
> If that doesn't apply, just ignore me. Heck, a lot of people ignore |
16 |
> me. lol |
17 |
> |
18 |
> Dale |
19 |
> |
20 |
> :-) :-) |
21 |
> |
22 |
> It does. I knew about it but never used it and didn't know what it'll do if |
23 |
> the permissions are wrong so I thought I'd minimize the chances of being |
24 |
> wrong. |
25 |
> |
26 |
|
27 |
I wasn't sure if it would help or not. I know it has worked in the past |
28 |
for me but it has been while. I usually tell the service to stop, make |
29 |
sure any processes are dead, with kill command if needed, and then use |
30 |
the zap thing. Maybe try that as a last resort if nothing else. |
31 |
|
32 |
I just didn't want to not mention it and it turn out to be just what was |
33 |
needed. ;-) |
34 |
|
35 |
Dale |
36 |
|
37 |
:-) :-) |