Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #175480 > unrolled thread

"command not found"

Back to article view | Back to linux.debian.user

Contents

  "command not found" Bob Holtzman <holtzm@cox.net> - 2016-12-06 22:30 +0100
    Re: "command not found" Greg Wooledge <wooledg@eeg.ccf.org> - 2016-12-06 22:30 +0100
    Re: "command not found" Jude DaShiell <jdashiel@panix.com> - 2016-12-06 23:30 +0100
      Re: "command not found" Gene Heskett <gheskett@shentel.net> - 2016-12-07 01:40 +0100
      Re: "command not found" Bob Holtzman <holtzm@cox.net> - 2016-12-07 20:20 +0100
    Re: "command not found" Andre Majorel <aym-naibed@teaser.fr> - 2016-12-07 08:10 +0100
    Re: "command not found" Joe <joe@jretrading.com> - 2016-12-07 09:20 +0100
      Re: "command not found" Mark Fletcher <mark27q1@gmail.com> - 2016-12-07 14:30 +0100

#175480 — "command not found"

I've run across this a number of times in the past, but it's usually a
permissions problem, easily fixed. Not this time.

holtzm@localhost:~$ ls -l .fetchmail
-rwx------ 1 holtzm holtzm 365 Nov 26 14:05 .fetchmail

Sure looks like it aught to work. It's probably something simple that
I'm missing and when someone points it ought I will ram my head into a
wall in self-disgust.

-- 
Bob  Holtzman
"Bother", said Pooh, as he chambered another round...

[toc] | [next] | [standalone]

#175481

On Tue, Dec 06, 2016 at 02:21:23PM -0700, Bob Holtzman wrote:
> I've run across this a number of times in the past, but it's usually a
> permissions problem, easily fixed. Not this time.
> 
> holtzm@localhost:~$ ls -l .fetchmail
> -rwx------ 1 holtzm holtzm 365 Nov 26 14:05 .fetchmail

But what command did you try to run?  You didn't say.

> Sure looks like it aught to work. It's probably something simple that
> I'm missing and when someone points it ought I will ram my head into a
> wall in self-disgust.

If you are trying to run a script located in the current directory (which
is not and should not be in your PATH by default), you have to specify
the path to the program.  Which is ./ for current directory.

./myscript

I have no idea why you have an executable file beginning with a dot.
Files that begin with a dot are traditionally configuration files used
by some other program.

I believe the config file for fetchmail is actually ~/.fetchmailrc and
not ~/.fetchmail but it's been years since I last looked at fetchmail.

[toc] | [prev] | [next] | [standalone]

#175486

It may be an ownership problem if you have the fetchmail package 
installed on your system.  The .fetchmailrc file may be in your account 
but that doesn't necessarily mean you explicitly own it.

On Tue, 6 Dec 2016, Bob Holtzman wrote:

> Date: Tue, 6 Dec 2016 16:21:23
> From: Bob Holtzman <holtzm@cox.net>
> To: debian-user@lists.debian.org
> Subject: "command not found"
> Resent-Date: Tue,  6 Dec 2016 21:21:52 +0000 (UTC)
> Resent-From: debian-user@lists.debian.org
> 
> I've run across this a number of times in the past, but it's usually a
> permissions problem, easily fixed. Not this time.
>
> holtzm@localhost:~$ ls -l .fetchmail
> -rwx------ 1 holtzm holtzm 365 Nov 26 14:05 .fetchmail
>
> Sure looks like it aught to work. It's probably something simple that
> I'm missing and when someone points it ought I will ram my head into a
> wall in self-disgust.
>
>

-- 

[toc] | [prev] | [next] | [standalone]

#175491

On Tuesday 06 December 2016 17:26:55 Jude DaShiell wrote:

> It may be an ownership problem if you have the fetchmail package
> installed on your system.  The .fetchmailrc file may be in your
> account but that doesn't necessarily mean you explicitly own it.
>
> On Tue, 6 Dec 2016, Bob Holtzman wrote:
> > Date: Tue, 6 Dec 2016 16:21:23
> > From: Bob Holtzman <holtzm@cox.net>
> > To: debian-user@lists.debian.org
> > Subject: "command not found"
> > Resent-Date: Tue,  6 Dec 2016 21:21:52 +0000 (UTC)
> > Resent-From: debian-user@lists.debian.org
> >
> > I've run across this a number of times in the past, but it's usually
> > a permissions problem, easily fixed. Not this time.
> >
> > holtzm@localhost:~$ ls -l .fetchmail
> > -rwx------ 1 holtzm holtzm 365 Nov 26 14:05 .fetchmail

Who setup those perms?  Of course it will fail.  Heres mine.

-rwxr-xr-x 1 root staff 754964 Feb 11  2015 /usr/local/bin/fetchmail

fetchmail starts as root, and immediately does a set uid to the user that 
launched it, and its been working that way here for for nearly 2 
decades.  Its running as a daemon, as the user me, pulling new mail 
every 3 minutes since the last reboot 11 days back.
> >
> > Sure looks like it aught to work. It's probably something simple
> > that I'm missing and when someone points it ought I will ram my head
> > into a wall in self-disgust.

Not recommended. But a repeated reading of the man page might be 
illuminating.

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)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#175524

On Tue, Dec 06, 2016 at 07:33:06PM -0500, Gene Heskett wrote:
> On Tuesday 06 December 2016 17:26:55 Jude DaShiell wrote:
> 
> > It may be an ownership problem if you have the fetchmail package
> > installed on your system.  The .fetchmailrc file may be in your
> > account but that doesn't necessarily mean you explicitly own it.
> >
> > On Tue, 6 Dec 2016, Bob Holtzman wrote:
> > > Date: Tue, 6 Dec 2016 16:21:23
> > > From: Bob Holtzman <holtzm@cox.net>
> > > To: debian-user@lists.debian.org
> > > Subject: "command not found"
> > > Resent-Date: Tue,  6 Dec 2016 21:21:52 +0000 (UTC)
> > > Resent-From: debian-user@lists.debian.org
> > >
> > > I've run across this a number of times in the past, but it's usually
> > > a permissions problem, easily fixed. Not this time.
> > >
> > > holtzm@localhost:~$ ls -l .fetchmail
> > > -rwx------ 1 holtzm holtzm 365 Nov 26 14:05 .fetchmail
> 
> Who setup those perms?  Of course it will fail.  Heres mine.

Me, and they have been working flawlessly on another installation.

> 
> -rwxr-xr-x 1 root staff 754964 Feb 11  2015 /usr/local/bin/fetchmail
> 
> fetchmail starts as root, and immediately does a set uid to the user that 
> launched it, and its been working that way here for for nearly 2 
> decades.  Its running as a daemon, as the user me, pulling new mail 
> every 3 minutes since the last reboot 11 days back.
> > >
> > > Sure looks like it aught to work. It's probably something simple
> > > that I'm missing and when someone points it ought I will ram my head
> > > into a wall in self-disgust.
> 
> Not recommended. But a repeated reading of the man page might be 
> illuminating.

Either that or my learning to proof read would be equally illuminating.

-- 
Bob  Holtzman
"Bother", said Pooh, as he chambered another round...

[toc] | [prev] | [next] | [standalone]

#175496

On 2016-12-06 14:21 -0700, Bob Holtzman wrote:

> I've run across this a number of times in the past, but it's usually a
> permissions problem, easily fixed. Not this time.
> 
> holtzm@localhost:~$ ls -l .fetchmail
> -rwx------ 1 holtzm holtzm 365 Nov 26 14:05 .fetchmail
> 
> Sure looks like it aught to work. It's probably something simple that
> I'm missing and when someone points it ought I will ram my head into a
> wall in self-disgust.

As Greg said, you probably just need to prefix the file name
with its path when invoking it, in this case "~/.fetchmail" (or
"./.fetchmail" when you already are in your home directory).

If you don't want to have to do that, you could instead move
.fetchmail to ~/bin/, /usr/local/bin/ or some other directory
that is listed in the PATH environment variable (but probably
not /bin, /sbin, /usr/bin or /usr/sbin as these are reserved for
Debian).

-- 
André Majorel <http://www.teaser.fr/~amajorel/>
lists.debian.org, your one-stop shop for email addresses.

[toc] | [prev] | [next] | [standalone]

#175499

On Tue, 6 Dec 2016 14:21:23 -0700
Bob Holtzman <holtzm@cox.net> wrote:

> I've run across this a number of times in the past, but it's usually a
> permissions problem, easily fixed. Not this time.
> 
> holtzm@localhost:~$ ls -l .fetchmail
> -rwx------ 1 holtzm holtzm 365 Nov 26 14:05 .fetchmail
> 
> Sure looks like it aught to work. It's probably something simple that
> I'm missing and when someone points it ought I will ram my head into a
> wall in self-disgust.
> 

Try losing the x. Many programs, when checking for a secure
configuration file, look for 600, not 700.

-- 
Joe

[toc] | [prev] | [next] | [standalone]

#175503

On Wed, Dec 07, 2016 at 08:17:44AM +0000, Joe wrote:
> On Tue, 6 Dec 2016 14:21:23 -0700
> Bob Holtzman <holtzm@cox.net> wrote:
> 
> > I've run across this a number of times in the past, but it's usually a
> > permissions problem, easily fixed. Not this time.
> > 
> > holtzm@localhost:~$ ls -l .fetchmail
> > -rwx------ 1 holtzm holtzm 365 Nov 26 14:05 .fetchmail
> > 
> > Sure looks like it aught to work. It's probably something simple that
> > I'm missing and when someone points it ought I will ram my head into a
> > wall in self-disgust.
> > 
> 
> Try losing the x. Many programs, when checking for a secure
> configuration file, look for 600, not 700.
> 
> -- 

There seems to be some confusion around whether that .fetchmail file is 
the executable or the config file. Perhaps the OP could elucidate? I 
doubt we are going to nail it until that is clear, except by accident.

If it is the binary, suggest you lose the . and listen to the advice of 
people suggesting you prefix with ./ . If it is the config file, as some 
people seem to be guessing, then it has nothing to do with a command not 
found error and you should be focused on where the binary is. which 
fetchail or locate fetchmail may help.

Mark

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web