Apologies, pinging again, to see if anyone has had issues with
systemd+mutlipathd running on CentOS7u2 and the creation of devices and
setting up /dev/disk/by-uuid id links during boot up.
if not, no worries and have great days, will check in elsewhere
thanks and regards
On Mon, Mar 13, 2017 at
Am Tue, 21 Mar 2017 07:47:59 -0500
schrieb Ian Pilcher :
> I have a oneshot service (run from a timer) that updates the TLS
> certificates in my mod_nss database. Because NSS doesn't support
> concurrent access to the database, I need to temporarily shut down
> Apache while
On Mon, Mar 20, 2017 at 7:40 PM Stanislav Angelovič
wrote:
Hi Jan,
thanks for quick response. Instead of sd_bus_process(), we could perhaps
use sd_bus_flush() after creating the connection, as that one actually
processes the requests until the connection changes state to
Thanks for the reply.
On Mon, Mar 20, 2017, 11:05 PM Mantas Mikulėnas wrote:
> First thought: Even without the exit code or anything, it's going to be
> -EBUSY like 99.999% of the time. Not much else can fail during umount.
>
> And ”Filesystem is busy" would perfectly fit the
On 03/21/2017 08:09 AM, Mantas Mikulėnas wrote:
Didn't NSS switch to sqlite for precisely that reason?
Yes they did. Unfortunately, this is a FreeIPA server, which still uses
the legacy Berkeley DB format.
--
Ian
I have a oneshot service (run from a timer) that updates the TLS
certificates in my mod_nss database. Because NSS doesn't support
concurrent access to the database, I need to temporarily shut down
Apache while the certificate update service is running.
Currently, I'm using the following entries
On Tue, Mar 21, 2017 at 2:47 PM, Ian Pilcher wrote:
> I have a oneshot service (run from a timer) that updates the TLS
> certificates in my mod_nss database. Because NSS doesn't support
> concurrent access to the database, I need to temporarily shut down
> Apache while the
On Tue, Mar 21, 2017 at 12:04 AM, Chris Murphy wrote:
>
> c. Only XFS is left in a dirty state following the reboot. Ext4 and Btrfs
> are OK.
This is incorrect. This problem affects ext4 as well, it's just that
on ext4, while the fs is left in a dirty state, the
OK so I had the idea to uninstall plymouth, since that's estensibly
what's holding up the remount read-only. But it's not true.
Sending SIGTERM to remaining processes...
Sending SIGKILL to remaining processes...
Unmounting file systems.
Remounting '/tmp' read-only with options 'seclabel'.
22.03.2017 00:10, Chris Murphy пишет:
> OK so I had the idea to uninstall plymouth, since that's estensibly
> what's holding up the remount read-only. But it's not true.
>
> Sending SIGTERM to remaining processes...
> Sending SIGKILL to remaining processes...
> Unmounting file systems.
>
10 matches
Mail list logo