Bristol Digest, Vol 620, Issue 3

Send Bristol mailing list submissions to
bristol@mailman.lug.org.uk

To subscribe or unsubscribe via the World Wide Web, visit
https://mailman.lug.org.uk/mailman/listinfo/bristol
or, via email, send a message with subject or body 'help' to
bristol-request@mailman.lug.org.uk

You can reach the person managing the list at
bristol-owner@mailman.lug.org.uk

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Bristol digest..."


Today's Topics:

1. Fedora 22 - Slow Shutdown (Peter Hemmings)
2. Liberty asking for help (Andy Pepperdine (BBLUG account))
3. Re: Fedora 22 - Slow Shutdown (Shane McEwan)
4. Re: Fedora 22 - Slow Shutdown (Peter Hemmings)


----------------------------------------------------------------------

Message: 1
Date: Tue, 6 Oct 2015 21:26:34 +0100
From: Peter Hemmings <peter@hemmings.eclipse.co.uk>
To: Bristol and Bath Linux User Group <bristol@mailman.lug.org.uk>
Subject: [bristol] Fedora 22 - Slow Shutdown
Message-ID: <56142E7A.7060805@hemmings.eclipse.co.uk>
Content-Type: text/plain; charset=utf-8; format=flowed

Hi,

I am trying to diagnose a slow (2min approx) shutdown on my laptop using
this:

http://freedesktop.org/wiki/Software/systemd/Debugging/#shutdowncompleteseventually.

I am trying to save the script as /usr/lib/systemd/system-shutdown/debug.sh

I do not have a folder "system-shutdown" and have a file of the same
name so cannot make a directory or perform the instruction.

Is the instruction out of date, or is there another way to do it on
fedora or am I doing something wrong!?

Regards

--
Peter H



------------------------------

Message: 2
Date: Wed, 7 Oct 2015 09:34:02 +0100
From: "Andy Pepperdine (BBLUG account)" <bbl.andy@pepsplace.org.uk>
To: Bristol and Bath Linux User Group <bristol@mailman.lug.org.uk>
Subject: [bristol] Liberty asking for help
Message-ID: <5614D8FA.3090507@pepsplace.org.uk>
Content-Type: text/plain; charset=utf-8

The human rights organisation Liberty is looking for someone to help
them formulate policy in the area of surveillance. The job description
is here:

https://www.liberty-human-rights.org.uk/sites/default/files/Policy%20Officer%20%28Technology%20and%20Surveillance%29%20Sept%202015.pdf

Perhaps a job for someone who want a change of direction, or a
sabbatical between jobs.

--
Andy Pepperdine



------------------------------

Message: 3
Date: Wed, 7 Oct 2015 10:53:10 +0100
From: Shane McEwan <shane@mcewan.id.au>
To: bristol@mailman.lug.org.uk
Subject: Re: [bristol] Fedora 22 - Slow Shutdown
Message-ID: <5614EB86.7070601@mcewan.id.au>
Content-Type: text/plain; charset=utf-8

I'm not sure (having not done anything with systemd yet) but if it
follows the usual conventions then I think you need to put the debug.sh
file into a /usr/lib/systemd/system-shutdown.d directory (note the
addition of '.d' to the end). That way it shouldn't clash with the
system-shutdown file. systemd should execute anything in the
/usr/lib/systemd/*.d directories.

Shane.

On 06/10/15 21:26, Peter Hemmings wrote:
> Hi,
>
> I am trying to diagnose a slow (2min approx) shutdown on my laptop using
> this:
>
> http://freedesktop.org/wiki/Software/systemd/Debugging/#shutdowncompleteseventually.
>
>
> I am trying to save the script as /usr/lib/systemd/system-shutdown/debug.sh
>
> I do not have a folder "system-shutdown" and have a file of the same
> name so cannot make a directory or perform the instruction.
>
> Is the instruction out of date, or is there another way to do it on
> fedora or am I doing something wrong!?
>
> Regards
>



------------------------------

Message: 4
Date: Wed, 7 Oct 2015 11:44:54 +0100
From: Peter Hemmings <peter@hemmings.eclipse.co.uk>
To: Bristol and Bath Linux User Group <bristol@mailman.lug.org.uk>
Subject: Re: [bristol] Fedora 22 - Slow Shutdown
Message-ID: <5614F7A6.4060705@hemmings.eclipse.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed

Hi,


On 07/10/15 10:53, Shane McEwan wrote:
> I'm not sure (having not done anything with systemd yet) but if it
> follows the usual conventions then I think you need to put the debug.sh
> file into a /usr/lib/systemd/system-shutdown.d directory (note the
> addition of '.d' to the end). That way it shouldn't clash with the
> system-shutdown file. systemd should execute anything in the
> /usr/lib/systemd/*.d directories.

Thanks for the info.

I do not have a "systen-shutdown.d directory atm but do have a
/usr/lib/systemd/scripts/ directory.

It has just one file in it "nfs-utils_env.sh", I assume I could put it
in there rather than make a new directory!?

As I understand it, the debug script is run almost at the end of
shutdown and should show what process is not closing correctly.
>
> Shane.
>
> On 06/10/15 21:26, Peter Hemmings wrote:
>> Hi,
>>
>> I am trying to diagnose a slow (2min approx) shutdown on my laptop using
>> this:
>>
>> http://freedesktop.org/wiki/Software/systemd/Debugging/#shutdowncompleteseventually.
>>
>>
>> I am trying to save the script as /usr/lib/systemd/system-shutdown/debug.sh
>>
>> I do not have a folder "system-shutdown" and have a file of the same
>> name so cannot make a directory or perform the instruction.
>>
>> Is the instruction out of date, or is there another way to do it on
>> fedora or am I doing something wrong!?
>>
>> Regards
>>
>
> _______________________________________________
> Bristol mailing list
> Bristol@mailman.lug.org.uk
> https://mailman.lug.org.uk/mailman/listinfo/bristol
>

I could just do a new clean install but I would prefer to find what
caused this to happen.

Regards
--
Peter H



------------------------------

Subject: Digest Footer

_______________________________________________
Bristol mailing list
Bristol@mailman.lug.org.uk
https://mailman.lug.org.uk/mailman/listinfo/bristol

------------------------------

End of Bristol Digest, Vol 620, Issue 3
***************************************