beppo | hello anyone here? | 11:24 |
---|---|---|
beppo | :) | 11:24 |
beppo | how can i add to smbd.conf that it should start after network interface is started | 11:24 |
=== Keybuk_ is now known as Keybuk | ||
twb | Does upstart log anywhere (e.g. netconsole) when and what events it receives? | 11:59 |
twb | I'm netbooting Ubuntu 10.04 and for some reason the secondary (read-write) NFS mounts on /home and /srv are never mounted. | 12:00 |
twb | Also, how can I get a directed graph of how events are generated and what responds to them? | 12:02 |
twb | It's a lot harder to see the boot order than a simple rcS.d | 12:02 |
=== jussi is now known as Guest7125 | ||
soren | twb: I don't think such a tool exists. | 12:12 |
soren | twb: Also, an upstart job can specify which events it might emit, but it's purely informational. It can emit other ones and never emit the ones it claimed it might. | 12:13 |
soren | twb: ...so any automatically generated graphs of events can't possibly be guaranteed to be accurate. | 12:14 |
twb | I only want a rough approximation, and/or a tracing of *a* real boot | 12:21 |
twb | I don't expect it to be perfect | 12:21 |
=== jussi01 is now known as jussi | ||
twb | Is $PATH guaranteed to be a particular value in upstart scripts (i.e. within sh embedded in /etc/init/foo.conf files)? | 12:40 |
twb | Why does statd.conf's pre-start script say "start portmap || true"? Are scripts invoked with sh -e? | 12:42 |
twb | Christ, this is confusing. | 13:15 |
twb | Where does $UPSTART_STOP_EVENTS come from, for example? | 13:15 |
twb | mountall-shell.conf checks its value without ever setting it | 13:15 |
ion | PATH is predefined IIRC. -e is on by default, as init(5) says. UPSTART_STOP_EVENTS is documented in there as well. | 13:17 |
twb | Hum, I'll read that manpage. | 13:20 |
twb | init(8) talks about /etc/init.conf, but it doesn't exist and there's not init.conf manpage. | 13:20 |
twb | s/not/no/ | 13:20 |
twb | Does upstart detect cycles in the event-wait dependency graph? | 14:48 |
twb | e.g. in the simplest case, foo.conf has "start on bar", and bar.conf has "start on foo" | 14:48 |
ion | There’s nothing wrong with tht. | 14:49 |
twb | Well, I suppose not, if you assume the user can get into the system and run "start foo" by then | 14:49 |
ion | To be more accurate, foo.conf: “start on started bar”, bar.conf: “start on started foo” should work just fine. It just ensures both are running whenever either one is. s/started/starting/ may cause neither to be able to start. | 14:52 |
mbiebl | twb: have you tried the --verbose boot parameter? | 14:53 |
twb | Hum, "--verbose"? Not "verbose"? | 14:54 |
mbiebl | twb: so, apparently you haven't :-) | 14:57 |
mbiebl | yes, it is --verbose | 14:57 |
mbiebl | see also man 7 upstart | 14:58 |
twb | Yeah, that's exactly what I wanted | 14:58 |
twb | Will that get dumped to netconsole? /me tries | 14:58 |
twb | Well, it probably would, if I could get netconsole.ko to load properly from the ramdisk :-/ | 15:18 |
twb | Nope, upstart --verbose output never hits netconsole, so I have no way to get a dump of it short of transcribing the last few lines that are left on the screen. | 15:24 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!