Re: no response from listmaster

[Jonathan Dowland]

On Mon, Dec 14, 2015 at 09:49:13AM -0500, Bob Bernstein wrote:
> On Mon, 14 Dec 2015, Dan Ritter wrote:
> 
> >Plonk*.
> 
> Sigh. Another satisfied customer.
> 
> >* https://en.wikipedia.org/wiki/Plonk_(Usenet)
> 
> FWIW, I didn't need the wikipedia reference. I've been plonked in classier
> joints than this!

I've never understood the blocker's desire to publish their block.
It's certainly of no interest to anyone else receiving the list.

Re: no response from listmaster

[Lisi Reisz]

On Tuesday 15 December 2015 07:15:57 to...@tuxteam.de wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Mon, Dec 14, 2015 at 03:06:48PM +, Lisi Reisz wrote:
> > On Monday 14 December 2015 13:54:09 to...@tuxteam.de wrote:
> > > > >Woah. Calm down a bit.
> > > >
> > > > That made you uncomfortable a little bit Tomas, huh?
> > >
> > > Most definitely, yes.
> > >
> > > >                                                       Please try to
> > > > deal with it before issuing instructions to me.
> > >
> > > No idea how you could take as "instruction" what only could be meant
> > > as a "proposal", but there you go...
> >
> > It was in the imperative.
> >
> > "imperative ‎(countable and uncountable, plural imperatives)
> > (uncountable, grammar) The grammatical mood expressing an order "
> >
> > https://en.wiktionary.org/wiki/imperative
>
> In the languages I know well imperative can express a strong wish as well
> as it can express an order.
>
> Since I'm not a native English speaker, I'll bow to your interpretation.

Since when could one extrapolate from one language to another??!  Perhaps the 
languages you know well don't really have an imperative.  I quoted Wiktionary 
anyway, so it is not just my interpretation.

Lisi

Re: no response from listmaster

[Lisi Reisz]

On Tuesday 15 December 2015 07:17:20 to...@tuxteam.de wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Mon, Dec 14, 2015 at 09:49:13AM -0500, Bob Bernstein wrote:
> > On Mon, 14 Dec 2015, Dan Ritter wrote:
> > >Plonk*.
> >
> > Sigh. Another satisfied customer.
> >
> > >* https://en.wikipedia.org/wiki/Plonk_(Usenet)
> >
> > FWIW, I didn't need the wikipedia reference. I've been plonked in
> > classier joints than this!
>
> Now, what do you prefer: being plonked or being ordered to do things?

Being plonked.  Any day.  Feel free to plonk me any time.  But issuing orders 
is likely to get an adverse reaction.

Agreed, Bob?

Lisi

Re: no response from listmaster

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, Dec 15, 2015 at 11:00:40AM +, Lisi Reisz wrote:
> On Tuesday 15 December 2015 07:15:57 to...@tuxteam.de wrote:

[...]

> > Since I'm not a native English speaker, I'll bow to your interpretation.
> 
> Since when could one extrapolate from one language to another??!

I have to do this all the time.

>   Perhaps the 
> languages you know well don't really have an imperative.

They both have.
>  I quoted Wiktionary 
> anyway, so it is not just my interpretation.

Quoth Wikipedia [1]

  "The imperative is a grammatical mood that forms commands or
   requests, including the giving of prohibition or permission,
   or any other kind of advice or exhortation."

May I take the "request" part?

I'm done with this thread, btw.

[1] 

regards
- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlZv8I8ACgkQBcgs9XrR2kYfowCdGkbpbscizXUQ8qfO0AvXZlUg
zVMAn3MA2x5imHA93Nn4HLJ8aha8zevb
=rqkC
-END PGP SIGNATURE-

Re: no response from listmaster

[Lisi Reisz]

On Tuesday 15 December 2015 10:50:55 to...@tuxteam.de wrote:
> > Since when could one extrapolate from one language to another??!
>
> I have to do this all the time.

Well, you shouldn't.  Languages don't equate in that way.

Lisi

Re: no response from listmaster

[Lisi Reisz]

On Tuesday 15 December 2015 10:50:55 to...@tuxteam.de wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Tue, Dec 15, 2015 at 11:00:40AM +, Lisi Reisz wrote:
> > On Tuesday 15 December 2015 07:15:57 to...@tuxteam.de wrote:
>
> [...]
>
> > > Since I'm not a native English speaker, I'll bow to your
> > > interpretation.
> >
> > Since when could one extrapolate from one language to another??!
>
> I have to do this all the time.
>
> >   Perhaps
> > the languages you know well don't really have an imperative.
>
> They both have.
>
> >  I quoted
> > Wiktionary anyway, so it is not just my interpretation.
>
> Quoth Wikipedia [1]
>
>   "The imperative is a grammatical mood that forms commands or
>requests, including the giving of prohibition or permission,
>or any other kind of advice or exhortation."
>
> May I take the "request" part?
>
> I'm done with this thread, btw.
>
> [1] 

 "Please be quiet". (from the above) "Be quiet."  In English the second is 
_certainly_ not a request.  Nor in practice is the first.

Re: no response from listmaster

[German]

On Tue, 15 Dec 2015 11:33:18 +
Lisi Reisz  wrote:

> On Tuesday 15 December 2015 10:50:55 to...@tuxteam.de wrote:
> > > Since when could one extrapolate from one language to another??!
> >
> > I have to do this all the time.
> 
> Well, you shouldn't.  Languages don't equate in that way.
> 
> Lisi
> 

Maybe enough needless banter? It would be better if needed questions
was answered better and with specifics

Re: no response from listmaster

[John Hasler]

tomas writes:
> In the languages I know well imperative can express a strong wish as
> well as it can express an order.

True in english as well.  It depends on context, though, and can easily
be misinterpreted.

On the other hand it's silly to take offense at what appears to be an
"order" from someone who is clearly lacks any power or authority to
enforce the "order".
-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA

Re: audio problem with coolmail

[Pierre Frenkiel]

On Mon, 14 Dec 2015, Sven Arvidsson wrote:


. . .
This might be a case where reading the source for the program will give
you more clues.
. . .


  hi Sven,
  that seemed a good idea, but I was unable to find anything useful
  by reading the source.
  Intead, it didn't took too much time to write a small script (40 lines)
  which does exactly what I want. It should not be too difficult
  for somebody with artist skills to create the 2 images UP and DOWN, but
  as I'm not in that category, I just made screen copies of the
  2 coolmail icons.

cheers,
--
Pierre Frenkiel

Re: Changing default XDB browser w/o GNOME etc.

[Christian Seiler]

Hi,

Am 2015-12-13 10:19, schrieb Eduard Bloch:

Observation: various programs use the XDG mechanism (freedesktop
configuration method) to start a specific browser to visit a 
hyperlink.

Easy to verify with the xdg-open tool.


Note that xdg-open is just a single implementation and most GUI
toolkits provide their own implementation of the XDG specifications
that are related to this - so changing xdg-open will typically not help
you, I don't think I'm using any software that actually uses it; it's
useful for scripting though.

But how can I change this setting in a persistent way especially when 
I

don't use Gnome or Kde or Xfce? I tried LxQt once and apparently the
stupid thing has reset some configuration and now xdg-open starts
Qupzilla which I don't like. Before, some other stupid program has 
reset

it to Chromium which I don't like either.

How can I configure this, and do that in a way that is set 
persisently?

i.e. no program or package changes the setting to its own yard.


Well, there's a command line tool to change the current setting, called
xdg-mime.

First of all, you need to figure out how the .desktop file is called
of the browser you want to set. For example, Debian's Iceweasel has
iceweasel.desktop. [*] If the software you want to use as your browser
deosn't have a .desktop file (I suspect all browsers packaged within
Debian do, but I don't know), then you need to create one - see the
man page of xdg-desktop-menu for details. All desktop files are found
in /usr/share/applications for programs installed via Debian packages.

I'll assume Iceweasel here and use 'iceweasel.desktop' in the following
example. Replace it by your browser of choice if appropriate.

The 'default browser' is actually not just a single setting. There are
four main settings that are typically related to the question of
'default browser': what program is associated with the HTTP and HTTPS
protocols and what program should open HTML and XHTML files. The
typical checkboxes in programs such as Chromium that change this
setting typically change all four (maybe some others as well), but you
can in fact change them individually if you like. (Iceweasel/Firefox
also includes text/xml for generic XML files in this list, but I'm
going to skip that here, because I don't think it's sensible to open
generic XML files in browsers.)

The MIME types for HTML and XHTML are text/html and
application/xhtml+xml. Change the defaults for these MIME types to make
local (X)HTML files open in the browser of your choice.

There are some 'special' MIME types for protocols, the dummy MIME
category for that is x-scheme-handler/, so for HTTP and HTTPS you
have x-scheme-handler/http and x-scheme-handler/https - these are the
MIME types used when a remote website is accessed.

The following example will set Iceweasel as the default browser by
setting all four MIME types (but as I said, you can pick and choose
here):

xdg-mime default iceweasel.desktop text/html application/xhtml+xml \
x-scheme-handler/http x-scheme-handler/https

After that all XDG compliant programs will use the browser you've set
here as their default browser - you may test it with xdg-open.

Note: this does not preclude some renegade program from changing this
setting back to something else - other than sandboxing such programs
don't think there's any possibility to stop this, because all these
settings are just a couple of files in your home directory, so any
program you run could in principle change them. I try to avoid programs
that mess up my configuration without asking.

Btw. you can also query the current default, e.g.

xdg-mime query default x-scheme-handler/http
(ignores any additional arguments, at least on my box, so only pass
a single MIME type to it per call)

You can also change your default file mananger via the special
inode/directory MIME type - this is the program executed when clicking
on "open containing folder" in Iceweasel - but also other programs use
it. It doesn't even have to be an X11-based program, mc also works
(and it comes with a .desktop file).

Feels like things that have been established in a sane way 
(alternatives

system and sensible-browser) are now reverted to the chaos we used to
manage in the nineties :-(


Well, there's some logic behind it. The alternatives system can only be
set globally by the administrator, so it doesn't help on multi-user
systems. sensible-* is a Debianism, other than derivatives I don't
think this has been adopted by anybody else (I may be wrong), so if I
were upstream to some project, I would not want to rely on these
things. (Also, I can't extract any inforamtion and e.g. show the user
with which program I was going to open something, which is something
you might want to do in certain circumstances.) Also, sensible-*
requires an environment variable per thing you want to configure it
as a user, which is fine if you restrict yourself to just a couple of
things (there are only sensible-{editor,pager,browser}),

Re: no response from listmaster

[Bob Bernstein]

On Tue, 15 Dec 2015, Lisi Reisz wrote:

Now, what do you prefer: being plonked or being ordered to do 
things?


Being plonked.  Any day.  Feel free to plonk me any time. 
But issuing orders is likely to get an adverse reaction.


Agreed, Bob?


Absolutely! Mais certainement! In short, nobody likes being 
*told* what to do.


And, yes, there is something sophomoric about plonking someone 
but telling them about it first. In the Usenet heydays of 
killfiles, that was not as a rule how it was done.


--
Bob Bernstein

Network settings on gnome-control-center

[Fabrizio Carrai]

Hello All,
I'm experiencing a problem on Debian 8 and the network settings using
gnome-control-center, i.e. the applications that starts when we click on
the upper right corner icon.

I alternated the settings of my network configuration between the command
line and the gnome app and now I have a routing instruction that is always
shown in the app but it does not appear in the editing field. The setting
is applied on exit. It looks like the app parameters are stored somewhere
(?) but I cannot understand where. Can somebody helps ?

Thanks.

-- 
*Fabrizio*

Re: Network settings on gnome-control-center

[Sven Arvidsson]

On Tue, 2015-12-15 at 19:16 +0100, Fabrizio Carrai wrote:
> Hello All,
> I'm experiencing a problem on Debian 8 and the network settings using
> gnome-control-center, i.e. the applications that starts when we click
> on
> the upper right corner icon.
> 
> I alternated the settings of my network configuration between the
> command
> line and the gnome app and now I have a routing instruction that is
> always
> shown in the app but it does not appear in the editing field. The
> setting
> is applied on exit. It looks like the app parameters are stored
> somewhere
> (?) but I cannot understand where. Can somebody helps ?

Not sure if I understand you correctly. But if you changed your network
configuration with something besides NM with the command line (not
using nmcli) you'll probably have problems. 

Either use NM, something similar, or set up the network manually. 

If I misunderstood you the settings for NM connections are in 
/etc/NetworkManager/system-connections

HTH,

-- 
Cheers,
Sven Arvidsson
http://www.whiz.se
PGP Key ID 6FAB5CD5





signature.asc
Description: This is a digitally signed message part

Re: no response from listmaster

[Brian]

On Tue 15 Dec 2015 at 11:49:49 -0500, Bob Bernstein wrote:

> On Tue, 15 Dec 2015, Lisi Reisz wrote:
> 
> >>Now, what do you prefer: being plonked or being ordered to do things?
> >
> >Being plonked.  Any day.  Feel free to plonk me any time. But issuing
> >orders is likely to get an adverse reaction.
> >
> >Agreed, Bob?
> 
> Absolutely! Mais certainement! In short, nobody likes being *told* what to
> do.

I'm going to quote the whole of the mail you sent which started this
subthread:

 > Surely your neuroscience teaching, and other professional duties, at UC and
 > elsewhere keep you sufficiently busy so that you shouldn't really have to
 > pester Debian volunteers trying to keep the massive Debian mailing lists
 > system up and running. You have what appears to be a perfectly serviceable
 > uc.edu personal email account. I understand how attached you must be to
 > syrano, your personal linux server, but please try to get and keep some
 > perspective on all this. You are having difficulties of a strictly personal
 > nature that in now way merit the time of Debian listadmins.

The first sentence is gratuitous ad hominem. The tone and phrasing make
it evident that you think the OP has no justification for posting here.
Why not just tell him to piss off because he is wasting our time?

Then a lecture is launched. It would be hard to say where perspective
has lost here; many difficulties recounted on this list are "personal"
to the user.

All that tomási reasonably said was:

 > Woah. Calm down a bit.

That is polite and succinct enough to clue someone in to responding as
though they are not seated on a high horse.

> And, yes, there is something sophomoric about plonking someone but telling
> them about it first. In the Usenet heydays of killfiles, that was not as a
> rule how it was done.

The boot continues to be put in. Just bought them - or are they new?

Meanwhile, the OP has reached a solution to his problem. Pestering us
appears to have its benefits. Just think, your response might have edged
him towards it. :)

[Sorry - the first two words of the last sentence form an imperative].

KDE plasma: accidently destroyed profile-settings

[Hans]

Dear list, 

I accidently deleted/killed/destroyed my activity profile settings in KDE 
plasma.

The problem shows in that way, if I click on the icon in the taskbar to get 
the popping up window, where I can chose the required profile, nothing is to be 
shown.


Instead the system freezes. I can click no other icons and have to restart 
KDE.

I suppose, I can repair it by deleting the required configuration files.

It would be nice, if someone could point me to all involved files, because I do 
not know, which are the correct ones. And of course do not want to delete the 
complete ~/.kde folder.

Thanks for reading and all your help.

Best regards

Hans 

command not found

[Bob Holtzman]

Running Wheezy (7.9) on a reinstall after launching Jessie thru a wall.
Reinstalled all my s/w including msmtp and fetchmail. I brought
.fetchmailrc over from my backup as well as .msmtprc. Both had been
working flawlessly on the previous install. Now when I run "fetchmail" I
get "command not found". Perms on .fetchmailrc are 700. A search on
various variations of Wheezy fetchmail "command not found" came up with 
nothing.

Any ideas, pointers or flames appreciated.

Re: command not found

[Gary Dale]

On 15/12/15 05:02 PM, Bob Holtzman wrote:

Running Wheezy (7.9) on a reinstall after launching Jessie thru a wall.
Reinstalled all my s/w including msmtp and fetchmail. I brought
.fetchmailrc over from my backup as well as .msmtprc. Both had been
working flawlessly on the previous install. Now when I run "fetchmail" I
get "command not found". Perms on .fetchmailrc are 700. A search on
various variations of Wheezy fetchmail "command not found" came up with
nothing.

Any ideas, pointers or flames appreciated.



Check permissions on fetchmail. Your account may not be allowed to 
execute it.

Re: command not found

[Brian]

On Tue 15 Dec 2015 at 15:02:33 -0700, Bob Holtzman wrote:

> Running Wheezy (7.9) on a reinstall after launching Jessie thru a wall.

I suppose everyone understands what this means,

> Reinstalled all my s/w including msmtp and fetchmail. I brought
> .fetchmailrc over from my backup as well as .msmtprc. Both had been
> working flawlessly on the previous install. Now when I run "fetchmail" I
> get "command not found". Perms on .fetchmailrc are 700. A search on
> various variations of Wheezy fetchmail "command not found" came up with 
> nothing.
> 
> Any ideas, pointers or flames appreciated.

Which command isn't found?

Re: no response from listmaster

[Lisi Reisz]

On Tuesday 15 December 2015 19:29:50 Brian wrote:
> Just think, your response might have edged
> him towards it. :)
>
> [Sorry - the first two words of the last sentence form an imperative].

:-))

Lisi

Re: no response from listmaster

[Lisi Reisz]

On Tuesday 15 December 2015 19:29:50 Brian wrote:
> Pestering us
> appears to have its benefits. Just think, your response might have edged
> him towards it. :)

To be fair, Brian, it wasn't pestering us that was complained about, it was 
pestering the listmasters.  "Pestering" us was the right thing to do, and as 
you say helped the OP solve his problem.

Lisi

Re: command not found

[John Hasler]

Probably a missing library.

-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA

Re: command not found

[Andrew M.A. Cater]

On Tue, Dec 15, 2015 at 11:07:58PM +, Brian wrote:
> On Tue 15 Dec 2015 at 15:02:33 -0700, Bob Holtzman wrote:
> 
> > Running Wheezy (7.9) on a reinstall after launching Jessie thru a wall.
> 
> I suppose everyone understands what this means,
> 
> > Reinstalled all my s/w including msmtp and fetchmail. I brought
> > .fetchmailrc over from my backup as well as .msmtprc. Both had been
> > working flawlessly on the previous install. Now when I run "fetchmail" I
> > get "command not found". Perms on .fetchmailrc are 700. A search on
> > various variations of Wheezy fetchmail "command not found" came up with 
> > nothing.
> > 
> > Any ideas, pointers or flames appreciated.
> 
> Which command isn't found?

.fetchmailrc needs to be 0600 permissions then it may work.

All the best,

AndyC

Re: command not found

[Lisi Reisz]

On Tuesday 15 December 2015 23:07:58 Brian wrote:
> On Tue 15 Dec 2015 at 15:02:33 -0700, Bob Holtzman wrote:
> > Running Wheezy (7.9) on a reinstall after launching Jessie thru a wall.
>
> I suppose everyone understands what this means,
>
> > Reinstalled all my s/w including msmtp and fetchmail. I brought
> > .fetchmailrc over from my backup as well as .msmtprc. Both had been
> > working flawlessly on the previous install. Now when I run "fetchmail" I
> > get "command not found". Perms on .fetchmailrc are 700. A search on
> > various variations of Wheezy fetchmail "command not found" came up with
> > nothing.
> >
> > Any ideas, pointers or flames appreciated.
>
> Which command isn't found?


$ fetchmail (or # fetchmail)  I think.

But I've no idea what "launching Jessie thru a wall" is.

Lisi

Re: command not found

[Brian]

On Tue 15 Dec 2015 at 23:12:56 +, Andrew M.A. Cater wrote:

> On Tue, Dec 15, 2015 at 11:07:58PM +, Brian wrote:
> > On Tue 15 Dec 2015 at 15:02:33 -0700, Bob Holtzman wrote:
> > 
> > > Running Wheezy (7.9) on a reinstall after launching Jessie thru a wall.
> > 
> > I suppose everyone understands what this means,
> > 
> > > Reinstalled all my s/w including msmtp and fetchmail. I brought
> > > .fetchmailrc over from my backup as well as .msmtprc. Both had been
> > > working flawlessly on the previous install. Now when I run "fetchmail" I
> > > get "command not found". Perms on .fetchmailrc are 700. A search on
> > > various variations of Wheezy fetchmail "command not found" came up with 
> > > nothing.
> > > 
> > > Any ideas, pointers or flames appreciated.
> > 
> > Which command isn't found?
> 
> .fetchmailrc needs to be 0600 permissions then it may work.

brian@desktop:~$ chmod 755 .fetchmailrc 
  
brian@desktop:~$ fetchmail 
File /home/brian/.fetchmailrc must have no more than -rwx-- (0700) 
permissions.

So again - which command isn't found?

Re: command not found

[Joe Pfeiffer]

Bob Holtzman  writes:

> Running Wheezy (7.9) on a reinstall after launching Jessie thru a wall.
> Reinstalled all my s/w including msmtp and fetchmail. I brought
> .fetchmailrc over from my backup as well as .msmtprc. Both had been
> working flawlessly on the previous install. Now when I run "fetchmail" I
> get "command not found". Perms on .fetchmailrc are 700. A search on
> various variations of Wheezy fetchmail "command not found" came up with 
> nothing.
>
> Any ideas, pointers or flames appreciated.

I assume when you say you get "command not found" you mean you get
"fetchmail: command not found".  If you mean you get anything else you
can stop reading right now, because everything else in what I'm writing
is assuming that.

Are you *sure* you installed fetchmail on the new system?  I know you
said you did, but that would be the most obvious problem.  You can run

dpkg -l fetchmail

and if it's there, you should get a line like

ii  fetchmail  6.3.26-2   amd64  SSL 
enabled POP3, APOP, IMAP mail gatherer/forwarder

in your output.  Assuming it's there, run

dpkg -L fetchmail | less

and see where the fetchmail program itself is installed.  On my system, I get

/usr/bin/fetchmail

Now, try

echo $PATH

to see if /usr/bin is in your path.  It sort of has to be; I can't
imagine how a system could be useable without it.

Anyway, those are some thoughts...

Re: command not found

[Bob Holtzman]

On Tue, Dec 15, 2015 at 05:37:23PM -0500, Gary Dale wrote:
> On 15/12/15 05:02 PM, Bob Holtzman wrote:
> >Running Wheezy (7.9) on a reinstall after launching Jessie thru a wall.
> >Reinstalled all my s/w including msmtp and fetchmail. I brought
> >.fetchmailrc over from my backup as well as .msmtprc. Both had been
> >working flawlessly on the previous install. Now when I run "fetchmail" I
> >get "command not found". Perms on .fetchmailrc are 700. A search on
> >various variations of Wheezy fetchmail "command not found" came up with
> >nothing.
> >
> >Any ideas, pointers or flames appreciated.
> >
> 
> Check permissions on fetchmail. Your account may not be allowed to
> execute it.

-rwx-- 1 holtzm holtzm 380 Oct 17 18:46 .fetchmailrc

Looks good to me. All the answers I have gotten so far pin the problem
on permissions. Not so.

Thanx to all that replied.

-- 

Bob Holtzman
A fair fight is the result of poor planning.

Re: command not found

[Bob Holtzman]

On Tue, Dec 15, 2015 at 11:12:56PM +, Andrew M.A. Cater wrote:
> On Tue, Dec 15, 2015 at 11:07:58PM +, Brian wrote:
> > On Tue 15 Dec 2015 at 15:02:33 -0700, Bob Holtzman wrote:
> > 
> > > Running Wheezy (7.9) on a reinstall after launching Jessie thru a wall.
> > 
> > I suppose everyone understands what this means,
> > 
> > > Reinstalled all my s/w including msmtp and fetchmail. I brought
> > > .fetchmailrc over from my backup as well as .msmtprc. Both had been
> > > working flawlessly on the previous install. Now when I run "fetchmail" I
> > > get "command not found". Perms on .fetchmailrc are 700. A search on
> > > various variations of Wheezy fetchmail "command not found" came up with 
> > > nothing.
> > > 
> > > Any ideas, pointers or flames appreciated.
> > 
> > Which command isn't found?
> 
> .fetchmailrc needs to be 0600 permissions then it may work.

I would think it should be 0700, but what do I know?

-- 

Bob Holtzman
A fair fight is the result of poor planning.

Re: command not found

[Richard Hector]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 16/12/15 13:52, Bob Holtzman wrote:
> On Tue, Dec 15, 2015 at 05:37:23PM -0500, Gary Dale wrote:
>> On 15/12/15 05:02 PM, Bob Holtzman wrote:
>>> Running Wheezy (7.9) on a reinstall after launching Jessie thru
>>> a wall. Reinstalled all my s/w including msmtp and fetchmail. I
>>> brought .fetchmailrc over from my backup as well as .msmtprc.
>>> Both had been working flawlessly on the previous install. Now
>>> when I run "fetchmail" I get "command not found". Perms on
>>> .fetchmailrc are 700. A search on various variations of Wheezy
>>> fetchmail "command not found" came up with nothing.
>>> 
>>> Any ideas, pointers or flames appreciated.
>>> 
>> 
>> Check permissions on fetchmail. Your account may not be allowed
>> to execute it.
> 
> -rwx-- 1 holtzm holtzm 380 Oct 17 18:46 .fetchmailrc
> 
> Looks good to me. All the answers I have gotten so far pin the
> problem on permissions. Not so.
> 
> Thanx to all that replied.
> 
Not .fetchmailrc - fetchmail. The executable: /usr/bin/fetchmail

Richard

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJWcLfqAAoJELSi8I/scBaNYoQH+gKg6rUKxC/7vGW/2zmdn4Q2
CEhgf2Sm1sScsFOtUwqqy71yHhAnwW8GRyvPNpNsPS3mQUb08EycFD/Bkx/idcDZ
agmi6LqEvZvJqp64de+Q8NdJq/eg4+HEj510TNXtwQi0Lqg4CgNeMNULk8zY+eKi
P7N8YPAF0O+Nekbu18z3QMcFa4hQZBvB+lJmZMS7fNqMUKjIzjE3pMrAJZktB/d9
u/thxVZRZSYAIAhra8RXs3RbLLoROxkbwM+zAl8D4JH4W9XdAsbu5oXORwA9MZ17
+xzYjynxJZlFiKK4FcT2/li2Ia9gQOPI6u3zTDvoWDrrgDqM5T20NXJYnWGuGvs=
=SmbW
-END PGP SIGNATURE-

Re: command not found

[Bob Holtzman]

On Tue, Dec 15, 2015 at 04:53:09PM -0700, Joe Pfeiffer wrote:
> Bob Holtzman  writes:
> 
> > Running Wheezy (7.9) on a reinstall after launching Jessie thru a wall.
> > Reinstalled all my s/w including msmtp and fetchmail. I brought
> > .fetchmailrc over from my backup as well as .msmtprc. Both had been
> > working flawlessly on the previous install. Now when I run "fetchmail" I
> > get "command not found". Perms on .fetchmailrc are 700. A search on
> > various variations of Wheezy fetchmail "command not found" came up with 
> > nothing.
> >
> > Any ideas, pointers or flames appreciated.
> 
> I assume when you say you get "command not found" you mean you get
> "fetchmail: command not found".  If you mean you get anything else you
> can stop reading right now, because everything else in what I'm writing
> is assuming that.
> 
> Are you *sure* you installed fetchmail on the new system?  I know you
> said you did, but that would be the most obvious problem.  You can run
> 
> dpkg -l fetchmail
> 
> and if it's there, you should get a line like
> 
> ii  fetchmail  6.3.26-2   amd64  SSL 
> enabled POP3, APOP, IMAP mail gatherer/forwarder
> 
> in your output.  Assuming it's there, run
> 
> dpkg -L fetchmail | less
> 
> and see where the fetchmail program itself is installed.  On my system, I get
> 
> /usr/bin/fetchmail
> 
> Now, try
> 
> echo $PATH
> 
> to see if /usr/bin is in your path.  It sort of has to be; I can't
> imagine how a system could be useable without it.
> 
> Anyway, those are some thoughts...

Aww give me a break. I've been screwing around w/ linux for 10-12 yrs
and yes, fetchmail is installed. Otherwise how could my .fetchmail file
exist with perms of 700 as I stated in my original post?

dpkg -L fetchmail

..huuuge snip.

/usr/bin
/usr/bin/fetchmail

Yup, there it is.

Thanks for the effort.

-- 

Bob Holtzman
A fair fight is the result of poor planning.

Re: command not found

[Gene Heskett]

On Tuesday 15 December 2015 19:55:05 Bob Holtzman wrote:

> On Tue, Dec 15, 2015 at 11:12:56PM +, Andrew M.A. Cater wrote:
> > On Tue, Dec 15, 2015 at 11:07:58PM +, Brian wrote:
> > > On Tue 15 Dec 2015 at 15:02:33 -0700, Bob Holtzman wrote:
> > > > Running Wheezy (7.9) on a reinstall after launching Jessie thru
> > > > a wall.
> > >
> > > I suppose everyone understands what this means,
> > >
> > > > Reinstalled all my s/w including msmtp and fetchmail. I brought
> > > > .fetchmailrc over from my backup as well as .msmtprc. Both had
> > > > been working flawlessly on the previous install. Now when I run
> > > > "fetchmail" I get "command not found". Perms on .fetchmailrc are
> > > > 700. A search on various variations of Wheezy fetchmail "command
> > > > not found" came up with nothing.
> > > >
> > > > Any ideas, pointers or flames appreciated.
> > >
> > > Which command isn't found?
> >
> > .fetchmailrc needs to be 0600 permissions then it may work.
>
> I would think it should be 0700, but what do I know?

Its -rw--- 1 gene gene 2901 Nov 18 07:59 .fetchmailrc here, has been 
working for a decade.


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Some mill pix are at:
Genes Web page 

Re: command not found

[Gene Heskett]

On Tuesday 15 December 2015 20:01:30 Richard Hector wrote:

> On 16/12/15 13:52, Bob Holtzman wrote:
> > On Tue, Dec 15, 2015 at 05:37:23PM -0500, Gary Dale wrote:
> >> On 15/12/15 05:02 PM, Bob Holtzman wrote:
> >>> Running Wheezy (7.9) on a reinstall after launching Jessie thru
> >>> a wall. Reinstalled all my s/w including msmtp and fetchmail. I
> >>> brought .fetchmailrc over from my backup as well as .msmtprc.
> >>> Both had been working flawlessly on the previous install. Now
> >>> when I run "fetchmail" I get "command not found". Perms on
> >>> .fetchmailrc are 700. A search on various variations of Wheezy
> >>> fetchmail "command not found" came up with nothing.
> >>>
> >>> Any ideas, pointers or flames appreciated.
> >>
> >> Check permissions on fetchmail. Your account may not be allowed
> >> to execute it.
> >
> > -rwx-- 1 holtzm holtzm 380 Oct 17 18:46 .fetchmailrc
> >
> > Looks good to me. All the answers I have gotten so far pin the
> > problem on permissions. Not so.
> >
> > Thanx to all that replied.
>
> Not .fetchmailrc - fetchmail. The executable: /usr/bin/fetchmail
>
> Richard

-rwxr-xr-x 1 root root 28 May  3  2012 /usr/bin/fetchmail

I don't even own it, runs perfectly for me.  Its my understanding that 
fetchmail does an suid to whomever calls it.
Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Some mill pix are at:
Genes Web page 

Re: command not found

[Lisi Reisz]

On Wednesday 16 December 2015 01:30:13 Gene Heskett wrote:
> On Tuesday 15 December 2015 20:01:30 Richard Hector wrote:
> > On 16/12/15 13:52, Bob Holtzman wrote:
> > > On Tue, Dec 15, 2015 at 05:37:23PM -0500, Gary Dale wrote:
> > >> On 15/12/15 05:02 PM, Bob Holtzman wrote:
> > >>> Running Wheezy (7.9) on a reinstall after launching Jessie thru
> > >>> a wall. Reinstalled all my s/w including msmtp and fetchmail. I
> > >>> brought .fetchmailrc over from my backup as well as .msmtprc.
> > >>> Both had been working flawlessly on the previous install. Now
> > >>> when I run "fetchmail" I get "command not found". Perms on
> > >>> .fetchmailrc are 700. A search on various variations of Wheezy
> > >>> fetchmail "command not found" came up with nothing.
> > >>>
> > >>> Any ideas, pointers or flames appreciated.
> > >>
> > >> Check permissions on fetchmail. Your account may not be allowed
> > >> to execute it.
> > >
> > > -rwx-- 1 holtzm holtzm 380 Oct 17 18:46 .fetchmailrc
> > >
> > > Looks good to me. All the answers I have gotten so far pin the
> > > problem on permissions. Not so.
> > >
> > > Thanx to all that replied.
> >
> > Not .fetchmailrc - fetchmail. The executable: /usr/bin/fetchmail
> >
> > Richard
>
> -rwxr-xr-x 1 root root 28 May  3  2012 /usr/bin/fetchmail
>
> I don't even own it, runs perfectly for me.  Its my understanding that
> fetchmail does an suid to whomever calls it.

You have execute permission - and read permission.  You only can't mess around 
with its innards.

Lisi

Re: debmirror hangs

[Joshua]

I too have had this problem, and while I don't know exactly what's 
failing on the script, I know it has something to do with converting the 
Index files to gzip and xz. An easy fix (at the expense of some 
additional bandwidth) is to pass in --slow-cpu, which will make it 
download all versions of the Index files and skip any gzip/xz processing 
on them. That fixed it for me, and I'm now happily updating my week-old 
mirror.


Hope that helps!

Re: command not found

[John Hasler]

That message does not necessarily mean that fetchmail is the command
that was not found.  The message is probably common from the loader due
to it not finding a missing library.
-- 
John Hasler
jhas...@newsguy.com
Elmwood, WI USA

Re: command not found

[Jimmy Johnson]

On 12/15/2015 05:06 PM, Bob Holtzman wrote:


 ..huuuge snip.

/usr/bin
/usr/bin/fetchmail

Yup, there it is.



Could you try starting in from there/that folder using your console? 
It's sure to find the command.

--
Debian Jessie - KDE 4.14.2  - EXT4 - AMD64 at sda10
Registered Linux User #380263

Re: command not found

[Bob Bernstein]

Please post your .fetchmailrc, obfuscating any identifying 
information in it.


Scripts can yield up a "command not found" when the nfg 
executable is not the script itself but, say, some utility 
called in the script. (Think: "Do I need to make any egreps 
greps." Just an _example_.)


Also, run 'fetchmail --version' for debugging info.

--
Bob Bernstein

Re: command not found

[Thomas Schmitt]

Hi,

Bob Holtzman wrote:
>  All the answers I have gotten so far pin the problem
> on permissions. Not so.

There is now a small group of "check your libraries" proposals
which you should consider.

See for an example of such a situation
  
http://superuser.com/questions/248512/why-do-i-get-command-not-found-when-the-binary-file-exists

So what do you get from

  ldd $(which fetchmail)

Are there any complaints about missing files ?
Do all the listed libraries exist ?
If they are symbolic links, do all link targets exist ?

There might also be incompatibilities between library versions and
fetchmail binary.
Did you try installing fetchmail from Debian repositories ?
(apt-get install or alike should care for all needed libraries.)


Have a nice day :)

Thomas