wine proccess list

[Gonzalo Martinez - Sanjuan Sanchez]

Hello to all.

I have something in mind that I would like to ask to Wine developers.
Is it possible using a hack/trick or a hidden option to change the  
name of wine in the proccess lists?
I mean, Is it possible to list 'wine' proccess as, for example  
'iexplorer' when I use Internet Explorer under Wine?

Thanks a lot for your work, hope my question find the answer here.

[Stefan Dösinger]

Am Dienstag, 11. Dezember 2007 18:02:53 schrieb Gonzalo Martinez - Sanjuan 
Sanchez:
> Hello to all.
>
> I have something in mind that I would like to ask to Wine developers.
> Is it possible using a hack/trick or a hidden option to change the
> name of wine in the proccess lists?
> I mean, Is it possible to list 'wine' proccess as, for example
> 'iexplorer' when I use Internet Explorer under Wine?
>
> Thanks a lot for your work, hope my question find the answer here.

This is done since quite some time. apps are usually called "iexplore.exe", or 
they have the name of the file that was passed to wine, like C:\Program 
Files\Internet Explorer\iexplore.exe

If you still see "wine", "wineloader" or something similar you have a very 
outdated version of wine.

[Gonzalo Martinez - Sanjuan Sanchez]

El Tuesday 11 December 2007 7:34:49 pm escribió:
> Am Dienstag, 11. Dezember 2007 18:02:53 schrieb Gonzalo Martinez - Sanjuan
>
> Sanchez:
> > Hello to all.
> >
> > I have something in mind that I would like to ask to Wine developers.
> > Is it possible using a hack/trick or a hidden option to change the
> > name of wine in the proccess lists?
> > I mean, Is it possible to list 'wine' proccess as, for example
> > 'iexplorer' when I use Internet Explorer under Wine?
> >
> > Thanks a lot for your work, hope my question find the answer here.
>
> This is done since quite some time. apps are usually called "iexplore.exe",
> or they have the name of the file that was passed to wine, like C:\Program
> Files\Internet Explorer\iexplore.exe
>
> If you still see "wine", "wineloader" or something similar you have a very
> outdated version of wine.

Well, im talking about Wine 0.9.48 under FreeBSD/PC-BSD OS.

[Stefan Dösinger]

Am Dienstag, 11. Dezember 2007 20:25:20 schrieb Gonzalo Martinez - Sanjuan 
Sanchez:
> El Tuesday 11 December 2007 7:34:49 pm escribió:
> > Am Dienstag, 11. Dezember 2007 18:02:53 schrieb Gonzalo Martinez -
> > Sanjuan
> >
> > Sanchez:
> > > Hello to all.
> > >
> > > I have something in mind that I would like to ask to Wine developers.
> > > Is it possible using a hack/trick or a hidden option to change the
> > > name of wine in the proccess lists?
> > > I mean, Is it possible to list 'wine' proccess as, for example
> > > 'iexplorer' when I use Internet Explorer under Wine?
> > >
> > > Thanks a lot for your work, hope my question find the answer here.
> >
> > This is done since quite some time. apps are usually called
> > "iexplore.exe", or they have the name of the file that was passed to
> > wine, like C:\Program Files\Internet Explorer\iexplore.exe
> >
> > If you still see "wine", "wineloader" or something similar you have a
> > very outdated version of wine.
>
> Well, im talking about Wine 0.9.48 under FreeBSD/PC-BSD OS.

Ow, ah, this is a different business. I think we use some Linux-only feature 
to set the name, and Alexandre told me that at least MacOS doesn't have it. I 
have no idea if there is a way to change the process name under BSD. If there 
is, feel free to implement it and send a patch

[Maarten Lankhorst]

Hi Gonzalo,

Stefan Dösinger schreef:
> Ow, ah, this is a different business. I think we use some Linux-only feature 
> to set the name, and Alexandre told me that at least MacOS doesn't have it. I 
> have no idea if there is a way to change the process name under BSD. If there 
> is, feel free to implement it and send a patch

A slightly hacky method is to copy the process to /tmp, rename it and
execute it there. It would work for mac and bsd, but I have no idea
wether Alexandre would accept it into wine.

Cheers,
Maarten.

[Alexandre Julliard]

Maarten Lankhorst  writes:
> Hi Gonzalo,
>
> Stefan Dösinger schreef:
> > Ow, ah, this is a different business. I think we use some Linux-only feature 
> > to set the name, and Alexandre told me that at least MacOS doesn't have it. I 
> > have no idea if there is a way to change the process name under BSD. If there 
> > is, feel free to implement it and send a patch
>
> A slightly hacky method is to copy the process to /tmp, rename it and
> execute it there. It would work for mac and bsd, but I have no idea
> wether Alexandre would accept it into wine.

I wouldn't, but on FreeBSD you can use setproctitle() for this.

[Wine] wine proccess list

[Geoff Streeter]

At 2007-12-11 20:01, Maarten Lankhorst wrote:
> Hi Gonzalo,
>
> Stefan Dösinger schreef:
> > Ow, ah, this is a different business. I think
>
> we use some Linux-only feature
> > to set the name, and Alexandre told me that
>
> at least MacOS doesn't have it. I
> > have no idea if there is a way to change the
>
> process name under BSD. If there
> > is, feel free to implement it and send a patch
>
> A slightly hacky method is to copy the process to /tmp, rename it and
> execute it there. It would work for mac and bsd, but I have no idea
> wether Alexandre would accept it into wine.
>
> Cheers,
> Maarten.
>
> wine-users mailing list
> [e-mail]
> http://www.winehq.org/mailman/listinfo/wine-users

Every time you installed a new app to run under 
wine you could create a new hard link for wine 
which had the requisite name. Use that name to 
start wine and hay presto that's the name in the ps listing.

Warning: be very careful when you update wine 
that you keep the same inode number otherwise all 
of the links will point to the old wine. Or give 
yourself a directory like 
/usr/local/bin/wineapps, put the links in there. 
Put it on your PATH. Then when you update wine, 
run a simple script to relink them to the new wine.

Geoff

[Pavel Troller]

> Am Dienstag, 11. Dezember 2007 18:02:53 schrieb Gonzalo Martinez - Sanjuan 
> Sanchez:
> > Hello to all.
> >
> > I have something in mind that I would like to ask to Wine developers.
> > Is it possible using a hack/trick or a hidden option to change the
> > name of wine in the proccess lists?
> > I mean, Is it possible to list 'wine' proccess as, for example
> > 'iexplorer' when I use Internet Explorer under Wine?
> >
> > Thanks a lot for your work, hope my question find the answer here.
>
> This is done since quite some time. apps are usually called "iexplore.exe", or 
> they have the name of the file that was passed to wine, like C:\Program 
> Files\Internet Explorer\iexplore.exe
>
> If you still see "wine", "wineloader" or something similar you have a very 
> outdated version of wine.

Hi!
  BTW I don't like this feature and I would prefer at least a commandline 
switch, or maybe a registry key, to prevent it.
  Why ?
  Because wine (and windows apps) sometimes crash and remain running, doing
nothing useful but eating CPU/memory, and not being able to be killed easily
(even killing the window doesn't close the app reliably). For this case, it's
most easy to execute "killall -KILL <some static name like wine/wine-pthread>"
instead of doing ps axufw, searching for the name of the app and then killing
it. I had a single-liner script called kw (kill wine) and doing exactly the
above command, and a beutifull bomb icon calling it. Now I can't se it - even
killing wineserver sometimes doesn't help.
  With regards, Pavel Troller
>

[Chris Robinson]

On Tuesday 11 December 2007 09:07:15 pm Pavel Troller wrote:
> Because wine (and windows apps) sometimes crash and remain running, doing
> nothing useful but eating CPU/memory, and not being able to be killed
> easily (even killing the window doesn't close the app reliably). For this
> case, it's most easy to execute "killall -KILL <some static name like
> wine/wine-pthread>" instead of doing ps axufw, searching for the name of
> the app and then killing it. I had a single-liner script called kw (kill
> wine) and doing exactly the above command, and a beutifull bomb icon
> calling it. Now I can't se it - even killing wineserver sometimes doesn't
> help.

IIRC, running 'wineserver -k' will kill wineserver and its processes. It's 
always worked for me, even on apparently stuck programs.

Though both methods (killall with a static wine process name and 
wineserver -k) will kill all wine/windows processes, even ones that are 
running fine. It's easier to killall a specific .exe named process, than 
using ps -fel to look for the PID and using regular kill on it.

[L. Rahyen]

On Wednesday December 12 2007 05:07, Pavel Troller wrote:
> > Am Dienstag, 11. Dezember 2007 18:02:53 schrieb Gonzalo Martinez -
> > Sanjuan
> >
> > Sanchez:
> > > Hello to all.
> > >
> > > I have something in mind that I would like to ask to Wine developers.
> > > Is it possible using a hack/trick or a hidden option to change the
> > > name of wine in the proccess lists?
> > > I mean, Is it possible to list 'wine' proccess as, for example
> > > 'iexplorer' when I use Internet Explorer under Wine?
> > >
> > > Thanks a lot for your work, hope my question find the answer here.
> >
> > This is done since quite some time. apps are usually called
> > "iexplore.exe", or they have the name of the file that was passed to
> > wine, like C:\Program Files\Internet Explorer\iexplore.exe
> >
> > If you still see "wine", "wineloader" or something similar you have a
> > very outdated version of wine.
>
> Hi!
>   BTW I don't like this feature and I would prefer at least a commandline
> switch, or maybe a registry key, to prevent it.
>   Why ?
>   Because wine (and windows apps) sometimes crash and remain running, doing
> nothing useful but eating CPU/memory, and not being able to be killed
> easily (even killing the window doesn't close the app reliably). For this
> case, it's most easy to execute "killall -KILL <some static name like
> wine/wine-pthread>" instead of doing ps axufw, searching for the name of
> the app and then killing it. I had a single-liner script called kw (kill
> wine) and doing exactly the above command, and a beutifull bomb icon
> calling it. Now I can't se it - even killing wineserver sometimes doesn't
> help.

You can simply run:

wineserver -k

This kills all processes which belongs to current WINE prefix (as specified 
in WINEPREFIX environment variable or ~/.wine otherwise). For me this works 
in 100% of cases so I see no problem here.
    Personally I really like this feature because I always know what Windows 
program(s) use my CPU and I can easily send STOP/CONT/KILL signals to Windows 
program(s) I want. Without this features this would be (almost) impossible.

[Wine] wine proccess list

[Markus Hitter]

Am 11.12.2007 um 18:02 schrieb Gonzalo Martinez - Sanjuan Sanchez:
> Is it possible using a hack/trick or a hidden option to change the
> name of wine in the proccess lists?

While this isn't a Wine specific question, you'd have to write your  
own executable-launcher. None of the shells I'm aware of allow to  
tweak argv[0]. The hearth of a custom launcher would be an execve()  
system call, see "man execve" on what it does.

Markus

- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de/