| 1 |
If I remember correctly with fetchmail you can start it in local.start with a |
| 2 |
username parameter that is the same as if the user started it. I did that |
| 3 |
and used the -d option to make it a daemon so it worked every boot. For |
| 4 |
other services - they may not support that. |
| 5 |
|
| 6 |
On Monday 13 November 2006 09:20, Jorge Almeida wrote: |
| 7 |
> On Mon, 13 Nov 2006, Steve [Gentoo] wrote: |
| 8 |
> > While system-level services are typically managed by /etc/init.d/* in |
| 9 |
> > Gentoo, these are maintained by root for all users. I'm interested in |
| 10 |
> > an end-user without root access who wants to 'run a service-like |
| 11 |
> > process' (for example, fectmail to poll remote accounts...) While an |
| 12 |
> > end user can easily run a daemon process or kill one, this doesn't |
| 13 |
> > persist across a reboot. I've tried using fcron to schedule user |
| 14 |
> > processes to re-start after a re-boot... but this feels like a hack. |
| 15 |
> |
| 16 |
> Use daemontools. It's in portage. Take a look at this site, which is |
| 17 |
> beginner-friendly: |
| 18 |
> http://www.thedjbway.org |
| 19 |
> A run script for fetchmail is in |
| 20 |
> http://smarden.org/runit/runscripts.html#fetchmail |
| 21 |
> but you can probably cook your own once you get used to daemontools. |
| 22 |
> |
| 23 |
> You probably want your service to be kept alive, even when it goes down |
| 24 |
> for whatever reason other than rebooting, so daemontools seems the |
| 25 |
> proper solution. |
| 26 |
> |
| 27 |
> I'm assuming you have root privileges but don't want to run services as |
| 28 |
> root when that's not really necessary. Otherwise, you'll need root's |
| 29 |
> cooperation. |
| 30 |
> -- |
| 31 |
> Jorge Almeida |
| 32 |
|
| 33 |
-- |
| 34 |
|
| 35 |
Brett I. Holcomb |
| 36 |
-- |
| 37 |
gentoo-user@g.o mailing list |
Archives