SOLVED -> How to stop "You will lose data" message?

[fixit]

Is there a way to stop the "You will lose data message." when I want to kill a process ?

[fixit]

I am overwhelmed by the responses.

[disciple]

What program are you using to try to kill the process (I think there are a few different programs used by some puppies)?
With open source there is always a way - the question is how easy it is. If this is with Pprocess it should be fairly easy, as Pprocess is just shell script and you don't need to recompile. But Zigbert is very responsive to feature requests, so you might like to ask for an option for it...

[fixit]

Best that I can come up with.

#!/bin/bash
# Kill a process such as Firefox

# Linux Puppy 5.6.0
# SiegeWorks 2014 A.P.K.
#
ps ux
killall -9 firefox

[Semme]

Mapped via XBindKeys, my *kills* generate no such dialog.

[disciple]

I think fixit is posting his solution/workaround, not clarification of his problem. Unless I'm confusing him with someone else, he has a tendency to do this...

[Semme]

Yeah, he's my bud. As a history major I know all about this cats delivery.

[fixit]

Mapped via XBindKeys, my *kills* generate no such dialog.

Open Grub4Dos, then right click it, and then select kill.

[fixit]

I think fixit is posting his solution/workaround, not clarification of his problem. Unless I'm confusing him with someone else, he has a tendency to do this...

If someone does not understand my problem, then wouldn't asking questions help in that ?

For example, I could tell you how to repair a Flame Spectrophotometer in great detail.

But you would probably want to ask some questions.

[disciple]

I think fixit is posting his solution/workaround, not clarification of his problem. Unless I'm confusing him with someone else, he has a tendency to do this...

If someone does not understand my problem, then wouldn't asking questions help in that ?

Yes, that's why I asked this: "What program are you using to try to kill the process?"
But you didn't answer it then.
Now you have started to - it sounds it's using your window manager (or panel), which is probably JWM.

[fixit]

I just right click on the window to kill it.

[disciple]

Assuming this is in a Puppy with JWM, I think you need JWM recompiled with confirmation dialogs disabled

[fixit]

Will be glad to do so, if someone can tell me how.

[disciple]

To compile things you need the devx as described at http://puppylinux.com/development/compileapps.htm
I think JWM uses the standard `./configure; make; make install` build process.
You need to configure JWM with the option --disable-confirm
Check the other options too by running `./configure --help` (I think the ridiculous rounded windows are evil, so I always disable them).

But I thought Puppies normally didn't use those confirmation dialogs... if you have another recent Puppy which doesn't use them you may just be able to grab its /usr/bin/jwm to use, instead of building your own.

[fixit]

Would that require installing the newer version and then copying those files ?

Maybe someone could post the zip ?

I use Puppy Slacko 5.6.0.

[disciple]

Presumably you are asking about this possibility:

if you have another recent Puppy which doesn't use them you may just be able to grab its /usr/bin/jwm to use, instead of building your own

No, you wouldn't need to install it as you can just open up the .sfs and copy jwm out. But if you don't know a particular Puppy with an appropriate build of JWM, it'll be better just to build it yourself.

[fixit]

Thanks.

[Karl Godt]

The message comes likely when right-clicking a drive icon to unmount it .

Puppy code is in /usr/local/bin/drive_all --> /root/.pup_event/drive_sdaX/AppRun .

It is rather unfortunate, that it uses in
unmount_func()

Code: Select all

fsUSERS=`fuser -m "$MNTPT"`

and not something like

Code: Select all

fsUSERS=`fuser -m "$MNTPT" >2&1`

or

Code: Select all

EXTRAMSG0=`for i in $fsUSERS; do ps | grep -w $i | grep -v grep;done`

[fixit]

Open up Firefox or any browser and right click on the window to kill it.

You will see the message.

[Semme]

Disciple gave the correct answer >> --disable-confirm = disable confirmation dialogs

If it were moi, I'd bypass JWM altogether, install xkill, then wrap it up neatly with a key combo.