-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
于 2011年04月12日 22:44, Zbigniew Jędrzejewski-Szmek wrote:
> On 04/12/2011 04:33 PM, microcai wrote:
>> > Shell is evil as Lennart said.
>> >
>> > Then I say, escaping non-ascii char is also evil.
>> >
>> > mount point should use only printable and type
On 04/12/2011 04:33 PM, microcai wrote:
> Shell is evil as Lennart said.
>
> Then I say, escaping non-ascii char is also evil.
>
> mount point should use only printable and type-able name, aka, valid
> UTF-8 string.
>
> Among them, / and - can be used, since unit file name can't contain /, /
> i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Shell is evil as Lennart said.
Then I say, escaping non-ascii char is also evil.
mount point should use only printable and type-able name, aka, valid
UTF-8 string.
Among them, / and - can be used, since unit file name can't contain /, /
is escaped a
On 04/12/2011 02:15 PM, Albert Strasheim wrote:
Hello all
I had the following in my syslog today while my service was running:
systemd[1]: Got invalid poll event on socket.
systemd[1]: foo.service: main process exited, code=exited, status=1
What causes invalid poll events on the socket? Which
Hello all
I had the following in my syslog today while my service was running:
systemd[1]: Got invalid poll event on socket.
systemd[1]: foo.service: main process exited, code=exited, status=1
What causes invalid poll events on the socket? Which socket?
It would be useful if systemd could give
