[OT] command line and GUI eqivalent
kitts.mailinglists at gmail.com
Tue Nov 7 14:41:54 GMT 2006
On Tuesday 07 November 2006 01:45 IST, Kevin Krammer wrote:
> > I cannot recollect precisely. You may experiment with the parameters or
> > lookup google. :-)
> The values are documented as part of the KApplication class:
> the first value is ShutdownConfirm, the second is ShutdownType and the
> last one is ShutdownMode
> A comination which might be good for your use case could be
> 0 0 0
> (no confirmation, no shutdown/logout only, schedule shutdown)
> 0 0 2
> (no confirmation, no shutdown/logout only, force now)
> It could be (not sure though) that the last value is not important once
> you say "logout only" for the second option.
Thanks for that input Kevin. I am reminded of an old discussion on the need
for better documentation of dcop calls and explanation of parameters being
offerred by tools like kdcop.
Anyway, the point i am looking at is why is it so wrong to use the standard
linux shutdown command from a terminal? The command should automatically
cause each application to exit. wrong?
The only thing i can think of is that kde probably requires that running
processes are exited in a particular order which is not maintained when
using the standard shutdown command.
Im just curious to know. I have a good number of friends and colleagues whom
i have convinced into using linux & kde as their OS. Many of them have had
been linux users many years ago. They are not very accustomed to using the
GUI and hence continue to use the CLI for tasks that have their GUI
The CLI shutdown causes problems with applications not shutting down
properly. Another problem faced is with manual CLI mounting of removable
media. The media gets mounted at 2 points causing occasional corruption.
This message is from the kde mailing list.
Account management: https://mail.kde.org/mailman/listinfo/kde.
More info: http://www.kde.org/faq.html.
More information about the kde