On Sun, Aug 09, 2015 at 09:11:19PM +0200, Santiago Vila wrote:
On Sun, Aug 09, 2015 at 06:58:15PM +0100, Sami Kerola wrote:
On 9 August 2015 at 18:19, Santiago Vila sanv...@unex.es wrote:
On Sun, Aug 09, 2015 at 07:14:30PM +0200, Reuti wrote:
The profile is usually sourced. How does the
[ Trimming Cc lines a little bit ].
On Tue, Aug 11, 2015 at 12:32:22PM +0200, Karel Zak wrote:
I think Posix standard is pretty explicit:
EXIT STATUS
The following exit values shall be returned:
0 Receiving messages is allowed.
1 Receiving messages is not allowed.
1 An error
On Sun, Aug 09, 2015 at 03:58:27PM +0200, Andreas Henriksson wrote:
Please note:
0 Messages are allowed.
1 Messages are not allowed.
1 An error has occurred.
Small clarification: The error codes are not really the problem.
The problem is
On 9 August 2015 at 18:19, Santiago Vila sanv...@unex.es wrote:
On Sun, Aug 09, 2015 at 07:14:30PM +0200, Reuti wrote:
The profile is usually sourced. How does the error show up at the login
prompt on Debian?
The problem only happens in Debian testing and unstable, which I am not using
On Sun, Aug 09, 2015 at 06:58:15PM +0100, Sami Kerola wrote:
On 9 August 2015 at 18:19, Santiago Vila sanv...@unex.es wrote:
On Sun, Aug 09, 2015 at 07:14:30PM +0200, Reuti wrote:
The profile is usually sourced. How does the error show up at the login
prompt on Debian?
The problem only
On Sun, Aug 09, 2015 at 07:14:30PM +0200, Reuti wrote:
The profile is usually sourced. How does the error show up at the login
prompt on Debian?
The problem only happens in Debian testing and unstable, which I am not using
yet.
This is the original report which I received against base-files:
Hello.
[ Apologies if this is a FAQ ].
Debian has recently switched the mesg implementation from
the one in sysvinit to the one in util-linux.
We have found a subtle issue: The old mesg didn't have any error codes
at all. The new mesg (from util-linux) has the following error codes:
Hello Santiago Vila.
Thanks for bringing this issue to my attention.
On Thu, Aug 06, 2015 at 11:24:05AM +0200, Santiago Vila wrote:
reassign 794727 util-linux
retitle 794727 mesg n exits with error, even if the command is successful
thanks
In this report I'm being asked to change
Am 09.08.2015 um 21:11 schrieb Santiago Vila:
On Sun, Aug 09, 2015 at 06:58:15PM +0100, Sami Kerola wrote:
On 9 August 2015 at 18:19, Santiago Vila sanv...@unex.es wrote:
On Sun, Aug 09, 2015 at 07:14:30PM +0200, Reuti wrote:
The profile is usually sourced. How does the error show up at the
Hello Santiago Vila!
On Sun, Aug 09, 2015 at 04:30:57PM +0200, Santiago Vila wrote:
On Sun, Aug 09, 2015 at 03:58:27PM +0200, Andreas Henriksson wrote:
Please note:
0 Messages are allowed.
1 Messages are not allowed.
1 An error has
Hi,
Am 09.08.2015 um 17:04 schrieb Santiago Vila:
Hello.
[ Apologies if this is a FAQ ].
Debian has recently switched the mesg implementation from
the one in sysvinit to the one in util-linux.
We have found a subtle issue: The old mesg didn't have any error codes
at all. The new mesg
reassign 794727 util-linux
retitle 794727 mesg n exits with error, even if the command is successful
thanks
In this report I'm being asked to change
/usr/share/base-files/dot.profile which is the default for
/root/.profile to accomodate for the new mesg behaviour.
The new behaviour, however,
12 matches
Mail list logo
