Re: [expert] manually start / stop gpilotd
On Tue, 2003-11-11 at 19:11, Bill Mullen wrote: Also worth knowing is that view is equivalent to vi -R (and quite a bit easier to remember) ... gview is the same as gvim -R, also ... That's not nearly as fun though! Want a rush? Logon as root and start randomly opening files with vi :) Seriously though, thanks for the 'view' command. I'll switch to that I think, it seems easier to remember - especially if I can still override with :w! -- Michael Holt Snohomish, WA (o_ [EMAIL PROTECTED] (o_ (o_ //\ www.holt-tech.net (/)_ (/)_ V_/_ www.mandrakelinux.com == -2. `We are shutting xxx down from 8.30 to 10.30 on Thursday to install a new tape drive.' The machine was up at about 2pm sans-tape drive --Top 100 things you don't want the sysadmin to say Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
[expert] manually start / stop gpilotd
How can I start / stop the gpilotd manually? I want it to get started when the machine boots but I'd like to be able to shut it off manually. -- Michael Holt Snohomish, WA (o_ [EMAIL PROTECTED](o_ (o_ //\ www.holt-tech.net(/)_ (/)_ V_/_www.mandrake.com Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] manually start / stop gpilotd
On Tue, 2003-11-11 at 07:58, Michael Holt wrote: How can I start / stop the gpilotd manually? I want it to get started when the machine boots but I'd like to be able to shut it off manually. In a terminal, type pkill gpilotd -- Jack Coates Monkeynoodle: A Scientific Venture... Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] manually start / stop gpilotd
Jack Coates mused: On Tue, 2003-11-11 at 07:58, Michael Holt wrote: How can I start / stop the gpilotd manually? I want it to get started when the machine boots but I'd like to be able to shut it off manually. In a terminal, type pkill gpilotd AAA!!! DUH!! I'm sorry I'm very distracted this morning :/ Ok, killing the thing isn't really a problem - starting it when the machine boots would be nice. :) I got a little frustrated trying to find the actual 'gpilotd' on/off button. I'd like to be able to run the gpilotd as an init script, but I don't know where it lives. I did some googling around but had no luck. Anyway, thanks Jack! -- Michael Holt Snohomish, WA (o_ [EMAIL PROTECTED](o_ (o_ //\ www.holt-tech.net(/)_ (/)_ V_/_www.mandrake.com Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] manually start / stop gpilotd
On Tue, 2003-11-11 at 09:42, Michael Holt wrote: Jack Coates mused: On Tue, 2003-11-11 at 07:58, Michael Holt wrote: How can I start / stop the gpilotd manually? I want it to get started when the machine boots but I'd like to be able to shut it off manually. In a terminal, type pkill gpilotd AAA!!! DUH!! I'm sorry I'm very distracted this morning :/ Ok, killing the thing isn't really a problem - starting it when the machine boots would be nice. :) I got a little frustrated trying to find the actual 'gpilotd' on/off button. I'd like to be able to run the gpilotd as an init script, but I don't know where it lives. I did some googling around but had no luck. Anyway, thanks Jack! NP :-) if you've got a sessions-capable window manager, your configger will have some sort of a start these programs tool. Otherwise, put an executable script into ~/Desktop/Autostart/ and call it from there. If you go that route, look our for how you edit the script -- Anything in the folder will be executed, including ~ backup files. -- Jack Coates Monkeynoodle: A Scientific Venture... Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] manually start / stop gpilotd
Jack Coates mused: On Tue, 2003-11-11 at 09:42, Michael Holt wrote: Jack Coates mused: On Tue, 2003-11-11 at 07:58, Michael Holt wrote: How can I start / stop the gpilotd manually? I want it to get started when the machine boots but I'd like to be able to shut it off manually. In a terminal, type pkill gpilotd AAA!!! DUH!! I'm sorry I'm very distracted this morning :/ Ok, killing the thing isn't really a problem - starting it when the machine boots would be nice. :) I got a little frustrated trying to find the actual 'gpilotd' on/off button. I'd like to be able to run the gpilotd as an init script, but I don't know where it lives. I did some googling around but had no luck. Anyway, thanks Jack! NP :-) if you've got a sessions-capable window manager, your configger will have some sort of a start these programs tool. Otherwise, put an executable script into ~/Desktop/Autostart/ and call it from there. If you go that route, look our for how you edit the script -- Anything in the folder will be executed, including ~ backup files. It's not so much that I can't start the program; the start program is 'gpilotd-control-applet'. The thing is, I just want to put my visor in it's cradle and hit the sync button - I've been using jpilot, but you have to hit the button on the cradle then click the sync button on jpilot and sometimes that doesn't work and if you don't hurry, it times out and you have to start over on the series of clicks and button pushes. Gnome-pilot is supposed to have the gpilotd (daemon) which runs in the background. Now once you've started it via the applet / dialog (which also brings up a dialog box asking you to confirm the device and settings), you can hit the cradle button to sync and it works great. The problem is that I don't leave this machine on, so I don't want to have to manually start that applet each time and even if it does start automatically, I still need to hit the 'ok' button each time. I just want it to start silently in the background. I can't seem to find any documentation that covers what I want it to do. -- Michael Holt Snohomish, WA (o_ [EMAIL PROTECTED](o_ (o_ //\ www.holt-tech.net(/)_ (/)_ V_/_www.mandrake.com Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] manually start / stop gpilotd
On Tue, 2003-11-11 at 10:24, Michael Holt wrote: ... It's not so much that I can't start the program; the start program is 'gpilotd-control-applet'. The thing is, I just want to put my no it isn't, that's the control panel applet, which happens to start gpilotd for you if it isn't already running. Just run gpilotd from a startup script. visor in it's cradle and hit the sync button - I've been using jpilot, but you have to hit the button on the cradle then click the sync button on jpilot and sometimes that doesn't work and if you don't hurry, it times out and you have to start over on the series of clicks and button pushes. Gnome-pilot is supposed to have the gpilotd (daemon) which runs in the background. Now once you've started it via the applet / dialog (which also brings up a dialog box asking you to confirm the device and settings), you can hit the cradle button to sync and it works great. The problem is you're lucky that it works at all, gnome-pilot is one finicky pile of junk -- er, fine piece of software. :-) that I don't leave this machine on, so I don't want to have to manually start that applet each time and even if it does start automatically, I still need to hit the 'ok' button each time. I just want it to start silently in the background. I can't seem to find any documentation that covers what I want it to do. What I gave you is what you need. Did you try it and have it not work? -- Jack Coates Monkeynoodle: A Scientific Venture... Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] manually start / stop gpilotd
On Tue, 2003-11-11 at 11:57, Jack Coates wrote: no it isn't, that's the control panel applet, which happens to start gpilotd for you if it isn't already running. Just run gpilotd from a startup script. Ok, if I do 'which gpilotd' it's nowhere to be found. If I do 'gpilotd' from the command, I get --bash command not found. In fact, if you do 'gpiltab' you get: gpilotd-control-applet gpilotd-session-wrapper gpilot-install-file The actual 'gpilotd' seems to be buried somewhere. I tried doing 'vi gpilotd-control-applet' just to see if I could see what is happening, but it wasn't very helpful for me. you're lucky that it works at all, gnome-pilot is one finicky pile of junk -- er, fine piece of software. :-) :) Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] manually start / stop gpilotd
On Tue, 2003-11-11 at 12:14, Michael Holt wrote: On Tue, 2003-11-11 at 11:57, Jack Coates wrote: no it isn't, that's the control panel applet, which happens to start gpilotd for you if it isn't already running. Just run gpilotd from a startup script. Ok, if I do 'which gpilotd' it's nowhere to be found. If I do 'gpilotd' from the command, I get --bash command not found. In fact, if you do 'gpiltab' you get: gpilotd-control-applet gpilotd-session-wrapper gpilot-install-file [EMAIL PROTECTED] html]# urpmf gpilotd libgnome-pilot2:/usr/lib/libgpilotd.so.2 libgnome-pilot2:/usr/lib/libgpilotd.so.2.1.0 libgnome-pilot2:/usr/lib/libgpilotdcm.so.2 libgnome-pilot2:/usr/lib/libgpilotdcm.so.2.0.2 libgnome-pilot2:/usr/lib/libgpilotdconduit.so.2 libgnome-pilot2:/usr/lib/libgpilotdconduit.so.2.0.3 gnome-pilot:/usr/bin/gpilotd-control-applet gnome-pilot:/usr/bin/gpilotd-session-wrapper gnome-pilot:/usr/lib/gpilotd ... ah hah. There's your gpilotd... that session-wrapper thing might be useful... try using file on it, and if it's a script then it might tell you something useful. The actual 'gpilotd' seems to be buried somewhere. I tried doing 'vi gpilotd-control-applet' just to see if I could see what is happening, but it wasn't very helpful for me. isn't that a binary? wouldn't be hlepful to me either :) you're lucky that it works at all, gnome-pilot is one finicky pile of junk -- er, fine piece of software. :-) :) __ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com -- Jack Coates Monkeynoodle: A Scientific Venture... Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] manually start / stop gpilotd
On Tue, 2003-11-11 at 14:13, Jack Coates wrote: [EMAIL PROTECTED] html]# urpmf gpilotd libgnome-pilot2:/usr/lib/libgpilotd.so.2 libgnome-pilot2:/usr/lib/libgpilotd.so.2.1.0 libgnome-pilot2:/usr/lib/libgpilotdcm.so.2 libgnome-pilot2:/usr/lib/libgpilotdcm.so.2.0.2 libgnome-pilot2:/usr/lib/libgpilotdconduit.so.2 libgnome-pilot2:/usr/lib/libgpilotdconduit.so.2.0.3 gnome-pilot:/usr/bin/gpilotd-control-applet gnome-pilot:/usr/bin/gpilotd-session-wrapper gnome-pilot:/usr/lib/gpilotd ... ah hah. There's your gpilotd... that session-wrapper thing might be useful... try using file on it, and if it's a script then it might tell you something useful. You da man!! :) Ok, I ran /usr/lib/gpilotd and all is well. Now, what did 'file' tell me beside the fact that this was an executable file? I noticed that you said if it's a *script* then it might tell you something useful. I tried running file on some scripts; it seems to describe what type of scripts you're looking at. Is that what you were getting at? Thanks Jack! -- Michael Holt Snohomish, WA (o_ [EMAIL PROTECTED] (o_ (o_ //\ www.holt-tech.net (/)_ (/)_ V_/_ www.mandrakelinux.com === Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] manually start / stop gpilotd
On Tue, 2003-11-11 at 15:02, Michael Holt wrote: On Tue, 2003-11-11 at 14:13, Jack Coates wrote: [EMAIL PROTECTED] html]# urpmf gpilotd libgnome-pilot2:/usr/lib/libgpilotd.so.2 libgnome-pilot2:/usr/lib/libgpilotd.so.2.1.0 libgnome-pilot2:/usr/lib/libgpilotdcm.so.2 libgnome-pilot2:/usr/lib/libgpilotdcm.so.2.0.2 libgnome-pilot2:/usr/lib/libgpilotdconduit.so.2 libgnome-pilot2:/usr/lib/libgpilotdconduit.so.2.0.3 gnome-pilot:/usr/bin/gpilotd-control-applet gnome-pilot:/usr/bin/gpilotd-session-wrapper gnome-pilot:/usr/lib/gpilotd ... ah hah. There's your gpilotd... that session-wrapper thing might be useful... try using file on it, and if it's a script then it might tell you something useful. You da man!! :) Ok, I ran /usr/lib/gpilotd and all is well. Now, what did 'file' tell me beside the fact that this was an executable file? I noticed that you said if it's a *script* then it might tell you something useful. I tried running file on some scripts; it seems to describe what type of scripts you're looking at. Is that what you were getting at? Thanks Jack! yeah, if file says it's a script, then you vi -R the script and see what it does (-R means read-only :-) -- Jack Coates Monkeynoodle: A Scientific Venture... Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] manually start / stop gpilotd
On Tue, 2003-11-11 at 16:33, Jack Coates wrote: yeah, if file says it's a script, then you vi -R the script and see what it does (-R means read-only :-) Yeah, pulled that one before ... ouch -- Michael Holt Snohomish, WA (o_ [EMAIL PROTECTED] (o_ (o_ //\ www.holt-tech.net (/)_ (/)_ V_/_ www.mandrakelinux.com === Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] manually start / stop gpilotd
On Tue, 11 Nov 2003, Jack Coates wrote: On Tue, 2003-11-11 at 15:02, Michael Holt wrote: Ok, I ran /usr/lib/gpilotd and all is well. Now, what did 'file' tell me beside the fact that this was an executable file? I noticed that you said if it's a *script* then it might tell you something useful. I tried running file on some scripts; it seems to describe what type of scripts you're looking at. Is that what you were getting at? yeah, if file says it's a script, then you vi -R the script and see what it does (-R means read-only :-) Also worth knowing is that view is equivalent to vi -R (and quite a bit easier to remember) ... gview is the same as gvim -R, also ... -- Bill Mullen [EMAIL PROTECTED] MA, USA RLU #270075 MDK 8.1 9.0 In the beginning the Universe was created. This has made a lot of people very angry and been widely regarded as a bad move. - Douglas Adams Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] manually start / stop gpilotd
On Tue, 2003-11-11 at 19:11, Bill Mullen wrote: On Tue, 11 Nov 2003, Jack Coates wrote: On Tue, 2003-11-11 at 15:02, Michael Holt wrote: Ok, I ran /usr/lib/gpilotd and all is well. Now, what did 'file' tell me beside the fact that this was an executable file? I noticed that you said if it's a *script* then it might tell you something useful. I tried running file on some scripts; it seems to describe what type of scripts you're looking at. Is that what you were getting at? yeah, if file says it's a script, then you vi -R the script and see what it does (-R means read-only :-) Also worth knowing is that view is equivalent to vi -R (and quite a bit easier to remember) ... gview is the same as gvim -R, also ... just beware wq! will override the read only status of the file. James Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
