On Thu, 23 Mar 2017, Yunchih Chen wrote:
Hello:
At my organization, there can be hundreds of user logins in a public
workstation each day, among more than one thousand of users. Since each user
login produces a 8MiB sparse log file in /var/log/journal/x/, significant
disk space is
On 03/23/2017 06:29 PM, Michael Chapman wrote:
On Thu, 23 Mar 2017, Yunchih Chen wrote:
Hello:
At my organization, there can be hundreds of user logins in a
public workstation each day, among more than one thousand of users.
Since each user login produces a 8MiB sparse log file in
Hello:
At my organization, there can be hundreds of user logins in a
public workstation each day, among more than one thousand of users.
Since each user login produces a 8MiB sparse log file in
/var/log/journal/x/, significant disk space is consumed. From the
administrator point of
23.03.2017 18:44, John Florian пишет:
> On Thu, 2017-03-23 at 06:38 +0300, Andrei Borzenkov wrote:
>> 22.03.2017 23:47, John Florian пишет:
>>> I build an mostly-stateless appliance OS derived from Fedora (25
>>> ATM)
>>> and have several custom units to make it all possible. My units
>>> had
>>>
On Mon, 20 Mar 2017 at 19:40:04 +0100, Stanislav Angelovič wrote:
> Regarding polling, I understand, but I fear this way we could get race
> condition on the connection instance, since we'd have a thread doing the
> polling and processing in a loop on the connection, and some other thread (say
>
On Thu, 2017-03-23 at 06:38 +0300, Andrei Borzenkov wrote:
> 22.03.2017 23:47, John Florian пишет:
> > I build an mostly-stateless appliance OS derived from Fedora (25
> > ATM)
> > and have several custom units to make it all possible. My units
> > had
> > worked great with F21, but are now
