| kaushal | hi | 09:40 |
|---|---|---|
| kaushal | when i edit any files in /etc/event.d/* | 09:40 |
| kaushal | what i have to run after that to update | 09:40 |
| ion_ | If your inotify is working, nothing. | 09:41 |
| kaushal | ok | 09:42 |
| kaushal | ion_, how can i check whether my inotify is working or not | 09:42 |
| ion_ | If you’re running a kernel image from any Ubuntu release shipping Upstart, you have a working inotify. | 09:44 |
| kaushal | oh ok | 09:45 |
| kaushal | is there a way i can find out on the Ubuntu Server | 09:45 |
| ion_ | If you have /proc/sys/fs/inotify, it’s working. | 09:46 |
| kaushal | ok | 09:46 |
| kaushal | ion_, its there | 09:48 |
| kaushal | I find it it has a directory | 09:49 |
| kaushal | max_queued_events max_user_instances max_user_watches | 09:49 |
| kaushal | ion_, for example if its not there how can i update /etc/event.d/ | 09:52 |
| ion_ | Some version of Upstart gained functionality to reload the job directory on signal, HUP perhaps. The version might have been 0.5. | 09:55 |
| kaushal | ii upstart 0.3.9-2 event-based init daemo | 09:56 |
| ion_ | See https://launchpad.net/upstart/0.5/0.5.0 | 09:56 |
| kaushal | ion_, I am running 0.3.9-2 version | 09:57 |
| ion_ | Yes | 09:57 |
| kaushal | on ubuntu 8.04 server | 09:57 |
| kaushal | ion_, can you please explain me about those 3 files | 09:58 |
| kaushal | max_queued_events max_user_instances max_user_watches | 09:58 |
| ion_ | Nothing except what’s obvious from the filenames. | 09:58 |
| kaushal | ok | 09:59 |
| ion_ | For more info, please look it up with Google or something. | 09:59 |
| kaushal | ion_, i have another query how can i know what all services has been started on Ubuntu Server | 09:59 |
| kaushal | I have been using Gentoo and Redhat | 10:00 |
| kaushal | on Gentoo its rc-status and on Redhat its service --status-all | 10:00 |
| kaushal | whats on Ubuntu | 10:00 |
| ion_ | Almost all of the services in Ubuntu are still started using sysvrc, which doesn’t have a consistent method for querying the status. For instance, pgrep -l sshd lists whether sshd is running. As soon as the ssh service is migrated to an Upstart job, both ‘inictl list’ and ‘initctl status ssh’ should list its status. | 10:02 |
| kaushal | ok | 10:04 |
| kaushal | ion_, please give me a moment | 10:04 |
| kaushal | initctl: Unknown job: s | 10:08 |
| kaushal | initctl: Unknown job: ssh | 10:08 |
| kaushal | initctl: Unknown job: sshd | 10:11 |
| kaushal | :( | 10:11 |
| AlexExtreme | As soon as the ssh service is migrated to an Upstart job, both ‘inictl list’ and ‘initctl status ssh’ should list its status. | 10:13 |
| AlexExtreme | read properly what ion_ said. "pgrep -l sshd lists whether sshd is running" | 10:14 |
| kaushal | AlexExtreme, ok | 10:47 |
| kaushal | AlexExtreme, Thanks | 10:47 |
| kaushal | Just curious to know when will ssh service is migrated to an Upstart job | 10:48 |
| pbn | Hello, how do I tell upstart that my default runlevel is not 2 but 3 ? | 20:22 |
| keesj | pbn: edit inittab (look at /etc/event.d/rc-default (that one does some grep magic) | 20:29 |
| keesj | hmm I perhap sjust would edit that file :P | 20:30 |
| pbn | keesj: thank you | 20:31 |
| pbn | yes but that script looks into /etc/inittab :) | 20:31 |
| pbn | perhaps is the solution: echo "id:3:initdefault" > /etc/inittab ... ? :) | 20:32 |
| keesj | pbn: so I guess that if you have a inittab you should modify it , oterwise it's easyer to changed it in the rc-default | 21:24 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!