:
On Wed, 29.04.15 22:08, Roger Qiu (roger@polycademy.com) wrote:
Hi Lennart,
So there really isn't a fast of way just checking if a file has an open file
descriptor on it?
Sometimes atime is on relatime, so it only gets updated if modification is
earlier.
Using relatime is fine, exce
e, and the atime may not be updated.
Thanks,
Roger
On 29/04/2015 9:33 PM, Lennart Poettering wrote:
On Wed, 29.04.15 15:10, Roger Qiu (roger@polycademy.com) wrote:
Hello all,
I'm planning to use tmpwatch's `fuser` feature.
But I'd prefer to run this simple service using
Hello all,
I'm planning to use tmpwatch's `fuser` feature.
But I'd prefer to run this simple service using systemd's tmpfiles.
Does systemd tmpfiles support running `fuser` so that way it won't
delete any files that have an open file descriptor?
I couldn't see any mention of in the docs and s
Hello all,
What is the difference between:
systemctl list-machines
versus
machinectl list
It seems that systemctl list-machines shows my current machine. But
nothing on machinectl. Are they going to merged together any time soon?
Thanks,
Roger
__
be the procedure to install kdbus
(https://github.com/gregkh/kdbus) and replace my current userspace systemd?
There doesn't seem to be any guides/documentation on that area.
Thanks,
Roger
On 18/08/2014 11:53 PM, Lennart Poettering wrote:
On Sun, 17.08.14 14:48, Roger Qiu (roger@polyc
Hello Lennart,
The reason why you don't want explicit ordering is because of a slower
boot time?
When you are referring to patching them out, would that be from upstream
systemd/logind?
Thanks,
Roger
On 15/08/2014 7:41 PM, Lennart Poettering wrote:
On Fri, 15.08.14 15:04, Roge
Hello Lennart,
Thanks for answering.
Is there any way to enforce ordering to make this error not occur?
Or what's the best way to hide that warning?
Or when is the ETA for kdbus?
Thanks,
Roger
On 15/08/2014 8:38 AM, Lennart Poettering wrote:
On Thu, 17.07.14 11:49, Roger Qiu (
asically I would like sshd
to report an error, if it is indeed an error from the host's side, not
the client's side.
On 17/07/2014 12:55 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Thu, Jul 17, 2014 at 12:53:01PM +1000, Roger Qiu wrote:
Hello,
This is the log of the status codes:
nit-script/bin/sshd@-pre-start
KillMode=process
StandardInput=socket
SuccessExitStatus=255
```
If I add that in, what about the normal exit status of "0"? Would that
override the successful exit code of 0?
Thanks,
Roger
On 17/07/2014 12:55 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Thu,
matrix-node systemd[1]: Unit
sshd@3-10.0.2.15:22-10.0.2.2:51014.service entered failed state.
```
Perhaps it's 255?
Thanks,
Roger
On 17/07/2014 12:51 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Thu, Jul 17, 2014 at 12:40:59PM +1000, Roger Qiu wrote:
Hello everybody,
I recently discovered that
Hello everybody,
I recently discovered that when using a socket activated SSHD service on
NixOS, it will show up as a failure on `sudo systemctl status` when the
client fails the connection.
The details are in this issue: https://github.com/NixOS/nixpkgs/issues/3279
Basically all I need to d
Hello Lennart,
Are you saying that logind should be terminated first then dbus should
be terminated second?
In what situations would their termination sequence get mixed?
Thanks,
Roger
On 17/07/2014 1:14 AM, Lennart Poettering wrote:
On Wed, 16.07.14 14:53, Roger Qiu (roger
Hello everybody,
I always receive this error:
```
|Jul 14 08:27:57 matrix-node systemd-logind[1339]: Failed to abandon session
scope: Connection reset by peer|
```
When I shutdown a NixOS instance.
Googling around didn't bring up any useful results. What does this error
mean, and why does
13 matches
Mail list logo
