fdo-mirrors/plymouth
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/plymouth/plymouth.git synced 2026-05-08 17:08:35 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

boot-server: don't print error when client goes away

Browse source 
Right now, anytime the server is unable to respond to a
client it puts an ugly message on the screen:

"could not write bytes: Broken pipe"

or some such.  That message isn't really useful unless you're
debugging your distribution, so change it from a ply_error to
ply_trace.
This commit is contained in:
Ray Strode 2010-10-20 10:04:24 -04:00
parent 0f1b124a2b
commit 871dbcbcce
1 changed files with 11 additions and 11 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
src/ply-boot-server.c
View file

@ -271,7 +271,7 @@ ply_boot_connection_send_answer (ply_boot_connection_t *connection,
if (!ply_write (connection->fd,
PLY_BOOT_PROTOCOL_RESPONSE_TYPE_NO_ANSWER,
strlen (PLY_BOOT_PROTOCOL_RESPONSE_TYPE_NO_ANSWER)))
ply_error ("could not write bytes: %m");
ply_trace ("could not write bytes: %m");
}
else
{
@ -284,7 +284,7 @@ ply_boot_connection_send_answer (ply_boot_connection_t *connection,
size) ||
!ply_write (connection->fd,
answer, size))
ply_error ("could not write bytes: %m");
ply_trace ("could not write bytes: %m");
}
@ -311,7 +311,7 @@ ply_boot_connection_on_deactivated (ply_boot_connection_t *connection)
PLY_BOOT_PROTOCOL_RESPONSE_TYPE_ACK,
strlen (PLY_BOOT_PROTOCOL_RESPONSE_TYPE_ACK)))
{
ply_error ("could not write bytes: %m");
ply_trace ("could not write bytes: %m");
}
}
@ -323,7 +323,7 @@ ply_boot_connection_on_quit_complete (ply_boot_connection_t *connection)
PLY_BOOT_PROTOCOL_RESPONSE_TYPE_ACK,
strlen (PLY_BOOT_PROTOCOL_RESPONSE_TYPE_ACK)))
{
ply_error ("could not write bytes: %m");
ply_trace ("could not write bytes: %m");
}
}
@ -390,7 +390,7 @@ ply_boot_connection_on_request (ply_boot_connection_t *connection)
if (!ply_write (connection->fd,
PLY_BOOT_PROTOCOL_RESPONSE_TYPE_NAK,
strlen (PLY_BOOT_PROTOCOL_RESPONSE_TYPE_NAK)))
ply_error ("could not write bytes: %m");
ply_trace ("could not write bytes: %m");
free (command);
return;
@ -402,7 +402,7 @@ ply_boot_connection_on_request (ply_boot_connection_t *connection)
if (!ply_write (connection->fd,
PLY_BOOT_PROTOCOL_RESPONSE_TYPE_ACK,
strlen (PLY_BOOT_PROTOCOL_RESPONSE_TYPE_ACK)))
ply_error ("could not write bytes: %m");
ply_trace ("could not write bytes: %m");
ply_trace ("got update request");
if (server->update_handler != NULL)
@ -548,7 +548,7 @@ ply_boot_connection_on_request (ply_boot_connection_t *connection)
if (!ply_write (connection->fd,
PLY_BOOT_PROTOCOL_RESPONSE_TYPE_NO_ANSWER,
strlen (PLY_BOOT_PROTOCOL_RESPONSE_TYPE_NO_ANSWER)))
ply_error ("could not write bytes: %m");
ply_trace ("could not write bytes: %m");
}
else
{
@ -563,7 +563,7 @@ ply_boot_connection_on_request (ply_boot_connection_t *connection)
size) ||
!ply_write (connection->fd,
ply_buffer_get_bytes (buffer), size))
ply_error ("could not write bytes: %m");
ply_trace ("could not write bytes: %m");
}
ply_buffer_free (buffer);
@ -667,7 +667,7 @@ ply_boot_connection_on_request (ply_boot_connection_t *connection)
if (!ply_write (connection->fd,
PLY_BOOT_PROTOCOL_RESPONSE_TYPE_NAK,
strlen (PLY_BOOT_PROTOCOL_RESPONSE_TYPE_NAK)))
ply_error ("could not write bytes: %m");
ply_trace ("could not write bytes: %m");
free(command);
return;
@ -680,7 +680,7 @@ ply_boot_connection_on_request (ply_boot_connection_t *connection)
if (!ply_write (connection->fd,
PLY_BOOT_PROTOCOL_RESPONSE_TYPE_NAK,
strlen (PLY_BOOT_PROTOCOL_RESPONSE_TYPE_NAK)))
ply_error ("could not write bytes: %m");
ply_trace ("could not write bytes: %m");
free(command);
return;
@ -690,7 +690,7 @@ ply_boot_connection_on_request (ply_boot_connection_t *connection)
PLY_BOOT_PROTOCOL_RESPONSE_TYPE_ACK,
strlen (PLY_BOOT_PROTOCOL_RESPONSE_TYPE_ACK)))
{
ply_error ("could not write bytes: %m");
ply_trace ("could not write bytes: %m");
}
free(command);
}