On Tue, Dec 20, 2016 at 03:30:13PM -0500, Matthew Miller wrote:
>
> On Tue, Dec 20, 2016 at 02:07:03PM -0500, Matthew Miller wrote:
> > If you wanted to change this, drop ProtectHome=false into
> > /etc/systemd/system/NetworkMananger.service.d/override.conf (possibly
> > by using sudo systemctl edi
On Tue, Dec 20, 2016 at 02:07:03PM -0500, Matthew Miller wrote:
> If you wanted to change this, drop ProtectHome=false into
> /etc/systemd/system/NetworkMananger.service.d/override.conf (possibly
> by using sudo systemctl edit foo NetworkMananger).
Sorry, no "foo" — that was a cut-paste error. And
On Tue, Dec 20, 2016 at 03:24:12PM -0500, Jonathan Billings wrote:
> /etc/systemd/system/NetworkManger.service.d/. Otherwise, the next
Obviously spell it right when you do it. :/
--
Jonathan Billings
___
CentOS mailing list
CentOS@centos.org
https:/
On Tue, Dec 20, 2016 at 11:20:57AM -0800, Glenn E. Bailey III wrote:
>
> Yup, verified those options are *not* set in 7.2. For a quick test I
> simply removed them from
> /usr/lib/systemd/system/NetworkManager.service, did a systemctl
> daemon-reload, restarted NetworkManager, logged back in as roo
Yup, verified those options are *not* set in 7.2. For a quick test I
simply removed them from
/usr/lib/systemd/system/NetworkManager.service, did a systemctl
daemon-reload, restarted NetworkManager, logged back in as root, and
was able to whack /home (7.3).
On Tue, Dec 20, 2016 at 11:07 AM, Matthe
On Fri, Dec 16, 2016 at 02:29:28PM -0500, Jonathan Billings wrote:
> The culprit? NetworkManager has /home open. I can't figure out
> *WHY*.
NetworkManager.service has 'ProtectHome=read-only', which keeps NM from
writing there. I presume namespacing /home in this way counts against
unmounting it
Confirmed as well, thanks! What's really odd is I didn't see
*anything* having a lock on /home, nada, zilch. We have a work-around
in place for this but I was beating my head against the wall trying to
figure it out.
On Fri, Dec 16, 2016 at 11:29 AM, Jonathan Billings wrote:
> On Fri, Dec 16, 201
On Fri, Dec 16, 2016 at 10:17:21AM -0800, Glenn E. Bailey III wrote:
> This is a base install. If you deploy an instance in ec2 or GCE (ec2
> you can do the free tier) it's easily repeatable. Even on a RHEL 7.3
> instance. Note you'll need to allow root and password logins via SSH
> before attempti
This is a base install. If you deploy an instance in ec2 or GCE (ec2
you can do the free tier) it's easily repeatable. Even on a RHEL 7.3
instance. Note you'll need to allow root and password logins via SSH
before attempting.
On Fri, Dec 16, 2016 at 5:47 AM, Jonathan Billings wrote:
> On Thu, Dec
On Thu, Dec 15, 2016 at 11:51:28AM -0800, Glenn E. Bailey III wrote:
> Doing a lsof showed no open files against /home. Something else is
> locking it, not a user process. Also disabled SELinux, did a init 1,
> and only way to remove it was via single user by passing
> init=/sysinit/bin/sh
It soun
Doing a lsof showed no open files against /home. Something else is
locking it, not a user process. Also disabled SELinux, did a init 1,
and only way to remove it was via single user by passing
init=/sysinit/bin/sh
On Thu, Dec 15, 2016 at 10:48 AM, Leonard den Ottolander
wrote:
> Hello Glen,
>
> O
Hello Glen,
On Thu, 2016-12-15 at 10:10 -0800, Glenn E. Bailey III wrote:
> I was most def root.
There's a difference whether you logged in as root or su-ed to root. In
the latter case /home is still in use by the user you su-ed from.
Even though it is not strictly necessary to init 1 you must m
I was most def root. /home isn't mounted as a separate filesystem.
It's not even tmpfs or btrfs. I was able to boot into single user mode
to remove it, but this isn't possible in an automated fashion. I may
just have to start building my own images.
Still curious to know why I can't rename or move
Jon LaBadie wrote:
> On Thu, Dec 15, 2016 at 04:10:07AM -0600, geo.inbox.ignored wrote:
>> On 12/15/2016 01:47 AM, Gianluca Cecchi wrote:
>> > On Thu, Dec 15, 2016 at 2:49 AM, Glenn E. Bailey III <
>> > replic...@dallaslamers.org> wrote:
>> >
>> >> Tried this in both AWS and GCE as I though it may
On Thu, Dec 15, 2016 at 04:10:07AM -0600, geo.inbox.ignored wrote:
>
>
> On 12/15/2016 01:47 AM, Gianluca Cecchi wrote:
> > On Thu, Dec 15, 2016 at 2:49 AM, Glenn E. Bailey III <
> > replic...@dallaslamers.org> wrote:
> >
> >> Tried this in both AWS and GCE as I though it may be a specific cloud
On 12/15/2016 01:47 AM, Gianluca Cecchi wrote:
> On Thu, Dec 15, 2016 at 2:49 AM, Glenn E. Bailey III <
> replic...@dallaslamers.org> wrote:
>
>> Tried this in both AWS and GCE as I though it may be a specific cloud
>> vendor issue. SELinux is disabled, lsof | grep home shows nothing,
>> lsattr
On Thu, Dec 15, 2016 at 2:49 AM, Glenn E. Bailey III <
replic...@dallaslamers.org> wrote:
> Tried this in both AWS and GCE as I though it may be a specific cloud
> vendor issue. SELinux is disabled, lsof | grep home shows nothing,
> lsattr /home shows nothing. Simply get "Device or resource busy."
Tried this in both AWS and GCE as I though it may be a specific cloud
vendor issue. SELinux is disabled, lsof | grep home shows nothing,
lsattr /home shows nothing. Simply get "Device or resource busy."
Works just find on 7.2 so I'm kinda at a loss. Scanned over the RHEL
release notes and didn't s
18 matches
Mail list logo
