| 1 |
On Wed, Sep 17, 2003 at 05:00:37PM +1000, Mark Francis wrote: |
| 2 |
> I have created bugs 28938, 28940, 28941, 28943 and 28945 to add daemontools |
| 3 |
> support |
| 4 |
> to the init scripts for samba, xinetd, fcron, cupsd and syslog-ng. Feel |
| 5 |
> free to try |
| 6 |
> it and see what you think. |
| 7 |
|
| 8 |
Great idea. |
| 9 |
|
| 10 |
> I discuss my approach in bug 28294. To summarise: |
| 11 |
> |
| 12 |
> 1. daemontools is not required but can optionally be used if available. |
| 13 |
> |
| 14 |
> 2. The daemontools service directory for each daemon is located in |
| 15 |
> /var/daemontools |
| 16 |
|
| 17 |
/var/service/ is already being used by sys-apps/supervise-scripts ... |
| 18 |
|
| 19 |
> |
| 20 |
> 3. This method has flexibility in that a user can choose to start each |
| 21 |
> daemon in |
| 22 |
> one of 3 different ways. The existing method (usually start-stop-daemon) in |
| 23 |
> an init |
| 24 |
> script, supervise from an init script, or svscan by creating a link to |
| 25 |
> /var/daemontools/$name |
| 26 |
> at /service/$name. Running supervise from the init script has the |
| 27 |
> advantages of both |
| 28 |
> init dependancy support and daemon monitoring. |
| 29 |
> |
| 30 |
> 4. No daemontools USE flag is required using this method. |
| 31 |
> |
| 32 |
> Mark |
| 33 |
> |
| 34 |
|
| 35 |
bye, |
| 36 |
peter |
| 37 |
|
| 38 |
> |
| 39 |
> Hallgrimur H. Gunnarsson wrote: |
| 40 |
> |
| 41 |
> >On 11.09.2003 Frederick Grim <fgrim@××××××××××××.org> wrote: |
| 42 |
> > |
| 43 |
> > |
| 44 |
> >>#!/bin/sh |
| 45 |
> >> |
| 46 |
> >>exec /usr/bin/tcpserver 0 111 /sbin/portmap -d 2>&1 |
| 47 |
> >> |
| 48 |
> >>with it's associated log/run script |
| 49 |
> >> |
| 50 |
> >>#!/bin/sh |
| 51 |
> >>exec /usr/bin/setuidgid nobody /usr/bin/multilog t s2500000 |
| 52 |
> >>/var/log/supervise/portmap |
| 53 |
> >> |
| 54 |
> >>which bypasses these dependancies. I have found, using daemontools |
| 55 |
> >>that the system logger is only useful for a few broken daemons that |
| 56 |
> >>can't be configured to log to stdout. |
| 57 |
> >> |
| 58 |
> >>So this is sort of an important point. If runscripts are included |
| 59 |
> >>will the logging by default be to the stdout or to syslog? |
| 60 |
> >> |
| 61 |
> >> |
| 62 |
> > |
| 63 |
> >I think it should definitely be stdout by default, even if it were |
| 64 |
> >just to force that support into all packages who wish to provide |
| 65 |
> >daemontools support, so that you dont install a program that claims |
| 66 |
> >to support 'daemontools' but doesnt allow to use another logger than |
| 67 |
> >syslog. |
| 68 |
> > |
| 69 |
> >Perhaps we should come up with some method in which 'run' files |
| 70 |
> >are installed? |
| 71 |
> > |
| 72 |
> >Should we have a /etc/supervise/packagename or |
| 73 |
> >/etc/daemontools/packagename, or something like that? |
| 74 |
> > |
| 75 |
> >- hhg |
| 76 |
> > |
| 77 |
> >-- |
| 78 |
> >gentoo-dev@g.o mailing list |
| 79 |
> > |
| 80 |
> > |
| 81 |
> > |
| 82 |
> |
| 83 |
> |
| 84 |
> -- |
| 85 |
> gentoo-dev@g.o mailing list |
| 86 |
> |
| 87 |
|
| 88 |
-- |
| 89 |
|
| 90 |
Petre Rodan |
| 91 |
Senior Network Engineer |
| 92 |
GeCAD Software - RAV Division |
| 93 |
|
| 94 |
---------------------------------------------------------------------- |
| 95 |
Tel/Fax: +40-21-321-7803 |
| 96 |
Hotline: +40-21-321-7859 |
| 97 |
|
| 98 |
This message is confidential. It may also be privileged or otherwise |
| 99 |
protected by work product immunity or other legal rules. |
| 100 |
If you have received it by mistake please let us know by reply and then |
| 101 |
delete it from your system; you should not copy the message or disclose |
| 102 |
its contents to anyone. |
| 103 |
|
| 104 |
|
| 105 |
-- |
| 106 |
gentoo-dev@g.o mailing list |
Archives