| 1 |
Jarry wrote: |
| 2 |
> On 21. 4. 2010 9:43, Amit Dor-Shifer wrote: |
| 3 |
>> Jarry wrote: |
| 4 |
>>> |
| 5 |
>>> s0:12345:respawn:/sbin/agetty 38400 ttyS0 vt100 |
| 6 |
>>> It mostly works, with one exception: right after boot-up |
| 7 |
>>> I get this message: |
| 8 |
>>> |
| 9 |
>>> INIT: ID "s0" respawning too fast: disabled for 5 minutes |
| 10 |
>>> |
| 11 |
>>> How can I control that respawn speed, or prohibit this |
| 12 |
>>> behavior (disabling ttyS0 for 5min)? I do not like waiting |
| 13 |
>>> 5min to log in, after I restarted server... |
| 14 |
>>> |
| 15 |
>> Don't know the answer to yr question. But I'm also not sure if you're |
| 16 |
>> asking the right question. |
| 17 |
>> When I last saw "respawning too fast: disabled for 5 minutes", it was |
| 18 |
>> actually an issue with the spawned process not being able to start. I'm |
| 19 |
>> therefore suggesting you'd want to consider checking why agetty cannot |
| 20 |
>> run, rather than working around init's behavior. |
| 21 |
>> Amit |
| 22 |
> |
| 23 |
> You may be right, but I did not find any clue as why is agetty |
| 24 |
> spawning too fast. I just noticed it happens only during boot-up, |
| 25 |
> with probability about 1:5. Maybe some starting processes are |
| 26 |
> conflicting with agetty. I do not think it is very serious problem, |
| 27 |
> as agetty on ttyS0 is always respawned after those 5min. All I want |
| 28 |
> is to reduce somehow those 5min time... |
| 29 |
> |
| 30 |
> Jarry |
| 31 |
> |
| 32 |
Well then, as far as I can see, the 5 min. timeout is hard-coded in |
| 33 |
/sbin/init. |
| 34 |
Amit |
Archives