[Bug 435484] Re: init script incorrectly 'su's

2012-07-30 Thread Steve Langasek
init scripts should never call su. They should call start-stop-daemon instead. ** Changed in: couchdb (Ubuntu) Status: Confirmed = Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/435484

[Bug 435484] Re: init script incorrectly 'su's

2010-05-28 Thread Tom Haddon
** Tags added: canonical-losa-u1 -- init script incorrectly 'su's https://bugs.launchpad.net/bugs/435484 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

[Bug 435484] Re: init script incorrectly 'su's

2009-12-18 Thread Chad Miller
Reported upstream at https://issues.apache.org/jira/browse/COUCHDB-603. (LP does not track JIRA tickets yet.) -- init script incorrectly 'su's https://bugs.launchpad.net/bugs/435484 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. --

[Bug 435484] Re: init script incorrectly 'su's

2009-12-08 Thread Jonathan Davies
** Changed in: couchdb (Ubuntu) Status: Confirmed = In Progress ** Changed in: couchdb (Ubuntu) Importance: Undecided = Medium ** Changed in: couchdb (Ubuntu) Status: In Progress = Confirmed -- init script incorrectly 'su's https://bugs.launchpad.net/bugs/435484 You received

[Bug 435484] Re: init script incorrectly 'su's

2009-10-16 Thread Chad Miller
** Changed in: couchdb (Ubuntu) Status: In Progress = Confirmed -- init script incorrectly 'su's https://bugs.launchpad.net/bugs/435484 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list

[Bug 435484] Re: init script incorrectly 'su's

2009-10-02 Thread Chad Miller
** Changed in: couchdb (Ubuntu) Assignee: (unassigned) = Chad Miller (cmiller) -- init script incorrectly 'su's https://bugs.launchpad.net/bugs/435484 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list

[Bug 435484] Re: init script incorrectly 'su's

2009-10-02 Thread Chad Miller
** Changed in: couchdb (Ubuntu) Status: Confirmed = In Progress -- init script incorrectly 'su's https://bugs.launchpad.net/bugs/435484 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list

[Bug 435484] Re: init script incorrectly 'su's

2009-10-02 Thread Launchpad Bug Tracker
** Branch linked: lp:~cmiller/ubuntu/karmic/couchdb/fix-init-overeager- su -- init script incorrectly 'su's https://bugs.launchpad.net/bugs/435484 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list

[Bug 435484] Re: init script incorrectly 'su's

2009-09-24 Thread Alex Lourie
Herb, Thank you for taking the time to report this bug and helping to make Ubuntu better. Can you please be more specific? What do you mean by doesn't work? Do you get an error while starting it? I've checked the init script, and it is perfectly normal to run su $USER being already a $USER.

[Bug 435484] Re: init script incorrectly 'su's

2009-09-24 Thread Herb McNew
If you run su as $USER the su process will either a) prompt you for a password (if one is set) or b) return su: Permission denied if the password field is a *. Either way this blocks the startup of the process or the machine. Example a: h...@ramble:~$ id uid=1000(herb) gid=1000(herb)

Re: [Bug 435484] Re: init script incorrectly 'su's

2009-09-24 Thread Alex Lourie
Herb, You are correct; this would be a problem if the script would run by anyone but root. But is it executed as non-root user? Ever? status confirmed -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Use GnuPG with

[Bug 435484] Re: init script incorrectly 'su's

2009-09-24 Thread Herb McNew
It is run as a non-root user. That's how we found this bug. On our production systems we on occasion give people access to certain role accounts, but don't want them to have root access. This includes the ability to start and stop services associated with said role accounts. In particular some