[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-devel
Subject: Res: resurrecting kwrited
From: dantti85-dev () yahoo ! com ! br
Date: 2008-10-11 23:38:11
Message-ID: 114818.65271.qm () web32103 ! mail ! mud ! yahoo ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hi, i totally agree about the part of
KNotify, also because if a user kills the
kwrited message on the old style he would be killing
kded, also knotify is pretty cooler. (not a very common
case but this way it would never happen as knotify is
another process)
i can't tell you anything about the executable part,
the only problem i see is that an executable consumes
more resources than a kded module.
Congrats for reviving it (actually mine is probably dead
because of that Debian package you said),
Daniel.
----- Mensagem original ----
De: George Kiagiadakis <kiagiadakis.george@gmail.com>
Para: kde-devel@kde.org
Enviadas: Sábado, 11 de Outubro de 2008 19:25:35
Assunto: resurrecting kwrited
Hello folks,
A few days ago I was writing some system script that uses wall(1) to notify me
about events and I was pretty disappointed when I discovered that kwrited
doesn't work at all on my system, so I've spent some time last week working on
it.
For those that are ignorant of what kwrited is, it is a kded module that sits
in the background and listens for messages send with write(1) or wall(1) and
when a message is received, it pops up a window showing the message. The
source code currently lives with konsole in kdebase/apps/konsole.
The problem on my system is that debian does not ship libutempter with it and
as a result, KPty is unable to login to any pseydo-terminal device (in case
libutempter is missing, KPty uses login(3), which requires elevated user
privileges that kwrited does not have). That makes kwrited useless because
wall(1) sends messages only on terminal devices where there are users logged
in. I started working on kwrited mainly to workaround this problem, but seeing
the state of this code (completely abandoned!) I thought it would be nice to
give some more love to it :)
So, I made some modifications and feature additions that can all be found here:
http://git.devreactor.org/?p=gkiagia/kwrited;a=summary
(git clone url: git://git.devreactor.org/gkiagia/kwrited )
There are four branches in this tree where I have split the various new
features so that it is easy to distinguish them.
The master branch contains some minor improvements and code cleanups. This
should be safe to upload to kde's svn as it doesn't really have any major
changes. See the shortlog on gitweb for details.
The knotify branch introduces the feature to use KNotify instead
of popping up the kwrited window on every new message. I was inspired to do
this from bug 104019. The changes in this branch should close now this bug.
Note here that I implemented a knotify popup with two actions, "Details" and
"Ignore". The details action pops up the kwrited window showing the same
message. After I implemented that, I thought it would be better to drop
completely the kwrited window and use ONLY knotify. What do you think of that?
That would also eliminate the dependency on QtGui/kdeui, which is useful to
save resources in the no-utempter version (see below).
The no-utempter branch introduces a workaround to my problem. To satisfy the
need for elevated user privileges, I made kwrited to build as an executable
instead of a kded module, so that it can be setgid to the utmp group, which is
the group that is able to edit the utmp and wtmp system files and login to
terminal devices. Building as an executable is a compile time detection (cmake
detects if libutemtper is available and acts appropriately). I am not sure if
this is really desired in kde, however if this is not going to be merged in
svn, I will probably continue maintaining it as a fork for myself :)
The knotify-no-utempter branch combines all the features from the knotify and
no-utempter branches. (The no-utempter branch has no knotify code).
The reason I send this email is mainly because I don't have an svn account to
commit it myself (this is my first contribution to kde, actually) and I would
also like to receive other people's comments as I am unsure of what should be
committed from all the changes that I've made. I can make a clean patch
against svn trunk upon request, just mail me or catch me on irc (nick:
gkiagia).
Thank you and sorry for the long email :)
George
> > Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Novos endereços, o Yahoo! que você conhece. Crie um email novo com a sua cara \
@ymail.com ou @rocketmail.com. http://br.new.mail.yahoo.com/addresses
[Attachment #5 (text/html)]
<html><head><style type="text/css"><!-- DIV {margin:0px;} \
--></style></head><body><div style="font-family:Courier \
New,courier,monaco,monospace,sans-serif;font-size:10pt"><div>Hi, i totally agree \
about the part of<br>KNotify, also because if a user kills the<br>kwrited message on \
the old style he would be killing<br>kded, also knotify is pretty cooler. (not a very \
common<br>case but this way it would never happen as knotify is<br>another \
process)<br><br>i can't tell you anything about the executable part,<br>the only \
problem i see is that an executable consumes<br>more resources than a kded \
module.<br><br>Congrats for reviving it (actually mine is probably dead<br>because of \
that Debian package you said),<br>Daniel.<br><br></div><div style="font-family: \
Courier New,courier,monaco,monospace,sans-serif; font-size: 10pt;"><br><div \
style="font-family: arial,helvetica,sans-serif; font-size: 13px;">----- Mensagem \
original ----<br>De: George Kiagiadakis \
<kiagiadakis.george@gmail.com><br>Para: kde-devel@kde.org<br>Enviadas: Sábado, \
11 de Outubro de 2008 19:25:35<br>Assunto: resurrecting kwrited<br><br>Hello \
folks,<br><br>A few days ago I was writing some system script that uses wall(1) to \
notify me <br>about events and I was pretty disappointed when I discovered that \
kwrited <br>doesn't work at all on my system, so I've spent some time last week \
working on <br>it.<br><br>For those that are ignorant of what kwrited is, it is a \
kded module that sits <br>in the background and listens for messages send with \
write(1) or wall(1) and <br>when a message is received, it pops up a window showing \
the message. The <br>source code currently lives with konsole in \
kdebase/apps/konsole.<br><br>The problem on my system is that debian does not ship \
libutempter with it and <br>as a result, KPty is unable to login to any \
pseydo-terminal device (in case <br>libutempter is missing, KPty uses login(3), which \
requires elevated user <br>privileges that kwrited does not have). That makes \
kwrited useless because <br>wall(1) sends messages only on terminal devices where \
there are users logged <br>in. I started working on kwrited mainly to workaround this \
problem, but seeing <br>the state of this code (completely abandoned!) I thought it \
would be nice to <br>give some more love to it :)<br><br>So, I made some \
modifications and feature additions that can all be found here: <br><a \
href="http://git.devreactor.org/?p=gkiagia/kwrited;a=summary" \
target="_blank">http://git.devreactor.org/?p=gkiagia/kwrited;a=summary</a><br>(git \
clone url: git://git.devreactor.org/gkiagia/kwrited )<br><br>There are four branches \
in this tree where I have split the various new <br>features so that it is easy to \
distinguish them.<br><br>The master branch contains some minor improvements and code \
cleanups. This <br>should be safe to upload to kde's svn as it doesn't really have \
any major <br>changes. See the shortlog on gitweb for details.<br><br>The knotify \
branch introduces the feature to use KNotify instead <br>of popping up the kwrited \
window on every new message. I was inspired to do <br>this from bug 104019. The \
changes in this branch should close now this bug. <br>Note here that I implemented a \
knotify popup with two actions, "Details" and <br>"Ignore". The details action pops \
up the kwrited window showing the same <br>message. After I implemented that, I \
thought it would be better to drop <br>completely the kwrited window and use ONLY \
knotify. What do you think of that? <br>That would also eliminate the dependency on \
QtGui/kdeui, which is useful to <br>save resources in the no-utempter version (see \
below).<br><br>The no-utempter branch introduces a workaround to my problem. To \
satisfy the <br>need for elevated user privileges, I made kwrited to build as an \
executable <br>instead of a kded module, so that it can be setgid to the utmp group, \
which is <br>the group that is able to edit the utmp and wtmp system files and login \
to <br>terminal devices. Building as an executable is a compile time detection (cmake \
<br>detects if libutemtper is available and acts appropriately). I am not sure if \
<br>this is really desired in kde, however if this is not going to be merged in \
<br>svn, I will probably continue maintaining it as a fork for myself :)<br><br>The \
knotify-no-utempter branch combines all the features from the knotify and \
<br>no-utempter branches. (The no-utempter branch has no knotify code).<br><br>The \
reason I send this email is mainly because I don't have an svn account to <br>commit \
it myself (this is my first contribution to kde, actually) and I would <br>also like \
to receive other people's comments as I am unsure of what should be <br>committed \
from all the changes that I've made. I can make a clean patch <br>against svn trunk \
upon request, just mail me or catch me on irc (nick: <br>gkiagia).<br><br>Thank you \
and sorry for the long email :)<br>George<br><br> <br>>> Visit <a \
href="http://mail.kde.org/mailman/listinfo/kde-devel#unsub" \
target="_blank">http://mail.kde.org/mailman/listinfo/kde-devel#unsub</a> to \
unsubscribe <<<br></div></div></div><br>
<hr size=1>Novos endereços, o Yahoo! que você conhece. <a \
href="http://br.rd.yahoo.com/mail/taglines/mail/*http://br.new.mail.yahoo.com/addresses">Crie \
um email novo</a> com a sua cara @ymail.com ou @rocketmail.com.</body></html>
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic