Date: Tue, 14 Dec 1999 19:41:21 -0800 (PST) From: John Polstra <jdp@polstra.com> To: dan@langille.org Cc: hubs@freebsd.org Subject: Re: cvsupd will not start Message-ID: <199912150341.TAA01829@vashon.polstra.com> In-Reply-To: <199912141307.CAA09723@ducky.nz.freebsd.org> References: <199912141307.CAA09723@ducky.nz.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <199912141307.CAA09723@ducky.nz.freebsd.org>,
Dan Langille <dan@langille.org> wrote:
> On 14 Dec 99, at 10:25, Dan Langille wrote:
>
> > I'm having trouble getting cvsupd started on a new box. It runs fine on
> > the old box. This problem occurs with both cvsup 16.1 and 16.0.
> >
> > # su -m cvsup -c "/usr/local/sbin/cvsupd -C 8 -l /var/log/cvsupd.log -s
> > sup.client"
> > Cannot become a daemon: Permission denied
...
> > With my reading, either Unix.fork() fails or we're the child process.
> >
> > Does anyone have any clues for me? The box in question is running 3.2-
> > release.
>
> <shrug>
>
> I upgraded to 3.3-19991207-SNAP and the problem went away. I have
> no idea why.
>
> </shrug>
Me neither. I think it probably failed in the setsid() call. It
can raise EPERM if (according to the man page):
[EPERM] The calling process is already a process group leader, or
the process group ID of a process other than the calling
process matches the process ID of the calling process.
But I don't know why that happened to you. I've never gotten any
other reports of this problem before.
John
--
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"No matter how cynical I get, I just can't keep up." -- Nora Ephron
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hubs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199912150341.TAA01829>