| Caesar | Oh Keybuk... | 20:52 |
|---|---|---|
| mbiebl | Keybuk: around? | 20:55 |
| sadmac | Keybuk: well since you're so popular in the last 5 minutes, I want to talk to you too :) | 20:56 |
| JanC | lol | 21:05 |
| === pocek_ is now known as pocek | ||
| Keybuk | Caesar: hey | 22:24 |
| Caesar | Keybuk: I think I figured out the answer to my question | 23:49 |
| Caesar | It was something along the lines of "don't do that" :-) | 23:49 |
| Keybuk | what was your question OOI? | 23:50 |
| Caesar | Keybuk: I was trying to write an Upstart job that would DWIM on Hardy and Lucid | 23:50 |
| Caesar | Then I remembered /etc/event.d vs /etc/init, so the probably all became rather moot | 23:50 |
| Caesar | I guess my meta-question is does Lucid's Upstart only accept a single "start on"/"stop on" line in the job file, whereas Hardy's would handle multiples? | 23:51 |
| Keybuk | ah | 23:51 |
| Keybuk | yeah | 23:51 |
| Keybuk | Hardy's OR'd them together and had no support for AND | 23:52 |
| Caesar | Ah | 23:52 |
| Caesar | Change is such a PITA | 23:52 |
| Keybuk | Lucid supports "and" & "or" as explicit operators | 23:52 |
| Caesar | Yeah, found that in init(5) | 23:52 |
| Caesar | Couldn't find much about the job spec in Hardy | 23:52 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!