112127 – start-stop-daemon's --chdir does nothing by default

Bug 112127 - start-stop-daemon's --chdir does nothing by default

Summary: start-stop-daemon's --chdir does nothing by default

Status:	RESOLVED WORKSFORME

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] baselayout (show other bugs)
Hardware:	All Linux

Importance:	High normal (vote)
Assignee:	Gentoo's Team for Core System packages

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2005-11-10 16:26 UTC by Sven
Modified:	2006-04-19 00:19 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Sven 2005-11-10 16:26:38 UTC

Hi,

Look at the output of
cd /somedir; start-stop-daemon --start --exec /usr/bin/pwd

It's "/somedir" and that's problematic. Some programs don't like it, if the
current workdir is not accessible, and this might be the case if you start the
daemon in /root, /root has the mode 0700, and the daemon switches to another user.

Long story short, start-stop-daemon --help states the following:
  -C|--chdir <directory>        Change to <directory>(default is /)

but the default doesn't seem to exist.

I'm using sys-apps/baselayout-1.11.13-r1

Reproducible: Always
Steps to Reproduce:

Comment 1 SpanKY gentoo-dev

2005-11-11 06:52:43 UTC

this has been fixed in baselayout-1.12.x already

Comment 2 Roy Marples (RETIRED) gentoo-dev

2006-04-19 00:19:11 UTC

Do any init scripts do this? If so, file a bug for each package it belongs to. Closing this one as WORKSFORME as we have fixed this in baselayout-1.12