| atpa8a | so generally... how can i run sysv scripts only after *all* of the network is up?.. | 01:52 |
|---|---|---|
| Keybuk | change the "start on" line of /etc/init/rc-sysinit.conf | 02:01 |
| Keybuk | if you want to just wedge something, you can do | 02:02 |
| Keybuk | echo start on WHATEVERINDICATESNETWORKINGISUP and starting rc-sysinit | 02:02 |
| Keybuk | that will wedge rc-sysinit from starting until "WHATEVERINDICATESNETWORKINGISUP" happens | 02:02 |
| Keybuk | err | 02:02 |
| Keybuk | echo start on WHATEVERINDICATESNETWORKINGISUP and starting rc-sysinit >> /etc/init/rc-sysinit-networking-wedge.conf | 02:02 |
| Keybuk | obviously | 02:02 |
| atpa8a | hello again | 03:19 |
| atpa8a | need an insight... how can i make sysv scripts run only after all the networking is up? | 03:19 |
| jab_doa | hi | 13:12 |
| jab_doa | can i somehow start a job on two different conditions? i want to use the one or the other. eg on rc2 stopped or on a signal | 13:15 |
| tohava | Question, when I tell upstart to restart a process, what exactly does it do? | 17:30 |
| tohava | anyone? | 17:32 |
| SpamapS | tohava: restart stops then starts the job, but does not reload its configuration (so any changes to the job file will not be recognized by a restart) | 20:31 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!