[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#929263: marked as done (/sbin and /usr/sbin are not in $PATH for unpriviledged users)



Your message dated Fri, 31 May 2019 12:28:10 -0500
with message-id <20190531172810.GI9477@mosca.iiec.unam.mx>
and subject line Re:  /sbin and /usr/sbin are not in $PATH for unpriviledged users
has caused the Debian Bug report #929263,
regarding /sbin and /usr/sbin are not in $PATH for unpriviledged users
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
929263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929263
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: cloud.debian.org
Severity: normal

Vagrant image debian/stretch64 v9.6.0
/usr/sbin is not included by default in $PATH

```
vagrant@stretch:~$ service
-bash: service: command not found
vagrant@stretch:~$ /usr/sbin/service
Usage: service < option > | --status-all | [ service_name [ command | --full-restart ] ]
vagrant@stretch:~$ echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
```

-- System Information:
Debian Release: 9.6
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-8-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message ---
Hi,

Given that the bug submitter has expressed he has "learnt a lot"
from the responses to his bug, I believe this bug can be safely
closed.

I agree this is a point that can be discussed in our mailing lists or
other spaces - but it's no longer a bug.

Greetings,

Attachment: signature.asc
Description: PGP signature


--- End Message ---

Reply to: