On Fri, Jul 08, 2022 at 08:37:19AM -0500, Albretch Mueller wrote:
> [...] that bash utils needed to be declared in
> the PATH in order for you to access them. Noticing it and opening
> another windows was all it took.
Ah, oh. You overwrote your PATH. Makes sense now :)
> it amazes me also how a
On Fri, 2022-07-08 at 08:37 -0500, Albretch Mueller wrote:
> it seemed to have been somehow
> blanketed by my "unconscious" that bash utils needed to be declared in
> the PATH in order for you to access them.
'which' isn't a 'bash util' whatever that is (presumably you mean a
shell built-in). As y
after reading through all your suggestions and still wondering about
what exactly was the mistake that I had made, I realized that it was a
simple and stupid "type in a rush and let 'the compiler' (sorry!) find
the mistake for you" kind of error: it seemed to have been somehow
blanketed by my "unc
On 2022-07-08 12:48, Greg Wooledge wrote:
https://wiki.debian.org/DebianAlternatives
thanks
mick
ste* the relevant lines (whole lines)
from your terminal session into the email. What you paste should show
us your shell prompt, the shell command that you typed, and all of the
output you received. For example:
unicorn:~$ catt /etc/group
bash: catt: command not found
2) Give us bas
On 2022-07-08 at 07:48, Greg Wooledge wrote:
> On Fri, Jul 08, 2022 at 12:47:19PM +0100, mick crane wrote:
>
>> here on bookworm
>> mick@pumpkin:~$ ls -la /usr/bin |grep which
>> lrwxrwxrwx 1 root root 23 Jan 23 18:05 which ->
>> /etc/alternatives/which
>> -rwxr-xr-x 1 root root
On Fri, Jul 08, 2022 at 12:47:19PM +0100, mick crane wrote:
> here on bookworm
> mick@pumpkin:~$ ls -la /usr/bin |grep which
> lrwxrwxrwx 1 root root 23 Jan 23 18:05 which ->
> /etc/alternatives/which
> -rwxr-xr-x 1 root root 946 May 1 17:47 which.debianutils
> mick@pumpkin:~$
>
On 2022-07-08 11:30, to...@tuxteam.de wrote:
Not every binary is contained in a package called like it.
That's what "apt-file" is for (in the same named package):
tomas@trotzki:~$ apt-file search bin/which
debian-goodies: /usr/bin/which-pkg-broke
debian-goodies: /usr/bin/which-pkg-b
e what that has to do with anything else that's in this
message.
> export _GRAALVM_HOME=.../graalvm-ce-java17-22.1.0
> export PATH=${PATH}:${_GRAALVM_HOME}/bin
> which javac
> which java
> $
>
> bash: which: command not found
>
> # apt-get install which
> Reading packa
r work)?
>
> export _GRAALVM_HOME=.../graalvm-ce-java17-22.1.0
There's one too many '.' characters there, but that shouldn't be the
cause of your issue.
> export PATH=${PATH}:${_GRAALVM_HOME}/bin
> which javac
> which java
> $
>
> bash: which: comman
aving forces actively messing with your work)?
>
> export _GRAALVM_HOME=.../graalvm-ce-java17-22.1.0
> export PATH=${PATH}:${_GRAALVM_HOME}/bin
> which javac
> which java
> $
>
> bash: which: command not found
>
> # apt-get install which
> Reading package lists...
graalvm-ce-java17-22.1.0
> export PATH=${PATH}:${_GRAALVM_HOME}/bin
> which javac
> which java
> $
>
> bash: which: command not found
>
> # apt-get install which
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
&g
rk)?
>
This could happen if cat has mode 744 (executable only
by owner) or some kind of SElinux magic.
> export _GRAALVM_HOME=.../graalvm-ce-java17-22.1.0
> export PATH=${PATH}:${_GRAALVM_HOME}/bin
> which javac
> which java
> $
>
> bash: which: command not found
>
Hi,
Albretch Mueller wrote:
> # apt-get install which
> E: Unable to locate package which
Try
apt-get install debianutils
I got the proposal from
$ apt-file search which | grep 'which$' | less
which still finds 18 lines which end by "which".
Number two looks like the program you look for:
ATH}:${_GRAALVM_HOME}/bin
which javac
which java
$
bash: which: command not found
# apt-get install which
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package which
#
# cat /etc/apt/sources.list
# deb cdrom:[Official Deb
Hi,
lists.deb...@netc.eu
> it seams that you found the reason...
Nbsp played similar tricks on me 6 years ago.
https://lists.debian.org/debian-user/2015/08/msg00030.html
But there is still the question how you produced Em Space by mistake.
Did you copy the line from some web page ?
Have a ni
Oh my god, Nice found, thanks very much, it seams that you found the reason...
Thank you !!! Nice day to you also Le 2021-11-25 12:34, Thomas Schmitt
a écrit : > > Hi, > > lists.deb...@netc.eu wrote: > > To
test I did "sudo apt install" and it worked > > [...] > > But just after I
retried
Hi,
lists.deb...@netc.eu wrote:
> To test I did "sudo apt install" and it worked
> [...]
> But just after I retried "apt install" and it not work. Here is all the
> output:
> [...]
> $ sudo apt install nfs-common
> Lecture des listes de paquets... Fait
> [...]
> $ sudo apt install nfs-common
s with sudo): apt update apt
search __ apt upgrade apt show __ ... And they all work as intended,
only "apt install" is giving me the output "command not found" :( Do you have
any idea on what might be the problem? Thanks all in advance for the help, Best
regards, Ma
PC. I already used a few days ago... I've tried several other options (always with sudo): apt update apt
search __ apt upgrade apt show __ ... And they all work as intended, only "apt install" is
giving me the output "command not found" :( Do you have any idea
intended, only "apt install" is giving me
the output "command not found" :( Do you have any idea on what might be the
problem? Thanks all in advance for the help, Best regards, Marc
intended, only "apt install" is giving me
the output "command not found" :( Do you have any idea on what might be the
problem? Thanks all in advance for the help, Best regards, Marc
On Fri, May 21, 2021 at 06:47:17PM -0400, Mohamud Ali wrote:
> dictionory
> Sorry, command-not-found has crashed! Please file a bug report at:
> http://www.debian.org/Bugs/Reporting
> Please include the following information with the report:
>
> command-not-found version: 0.
On Fri, Apr 30, 2021 at 12:33:27AM -0400, Xhorium Tech wrote:
> OBTAINING FOLLOWING PROBLEM
>
> command-not-found version: 0.3
> Python version: 3.9.1 final 0
> Distributor ID: Kali
> Description:Kali GNU/Linux Rolling
> Release:2021.1
> Codename:
OBTAINING FOLLOWING PROBLEM
command-not-found version: 0.3
Python version: 3.9.1 final 0
Distributor ID: Kali
Description:Kali GNU/Linux Rolling
Release:2021.1
Codename: kali-rolling
Exception information:
unable to open database file
Traceback (most recent call last):
File
ght i
>> got them all, but I missed one, tinyply.
>> When I went to complied tinyply i get the following on terminal shell:
>>
>>
>> *Could not find the database of available applications, run
>> update-command-not-found as root to fix thisSorry, command-n
gt; When I went to complied tinyply i get the following on terminal shell:
>
>
> *Could not find the database of available applications, run
> update-command-not-found as root to fix thisSorry, command-not-found has
> crashed! Please file a bug report at:http://www.deb
I missed one, tinyply.
> When I went to complied tinyply i get the following on terminal shell:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *Could not find the database of available applications, run
> update-command-not-found as
the following on terminal shell:
*Could not find the database of available applications, run
update-command-not-found as root to fix thisSorry, command-not-found has
crashed! Please file a bug report at:http://www.debian.org/Bugs/Reporting
<http://www.debian.org/Bugs/Report
On 2019-07-30, Rodolfo Medina wrote:
>>>
>>>
>>> curty@einstein:~$ apt-cache show texlive-base | grep -i updmap
>>> updmap-map --
>>>
>>> So simply spelt 'updmap-map', I guess.
>>
>> On stretch, it seems it's just updmap
>
>
> Thanks all, that seems to be the case...
Yes, I managed to get th
David Wright writes:
> On Mon 29 Jul 2019 at 19:56:32 (-), Curt wrote:
>> On 2019-07-29, wrote:
>> >
>> > (this is an oldstable Debian).
>> >
>> > Perhaps the thing you're looking for is simply spelt "updmap"?
>>
>>
>> curty@einstein:~$ apt-cache show texlive-base | grep -i updmap
>> up
On Mon 29 Jul 2019 at 19:56:32 (-), Curt wrote:
> On 2019-07-29, wrote:
> >
> > (this is an oldstable Debian).
> >
> > Perhaps the thing you're looking for is simply spelt "updmap"?
>
>
> curty@einstein:~$ apt-cache show texlive-base | grep -i updmap
> updmap-map --
>
> So simply spelt '
On 2019-07-29, wrote:
>
> (this is an oldstable Debian).
>
> Perhaps the thing you're looking for is simply spelt "updmap"?
curty@einstein:~$ apt-cache show texlive-base | grep -i updmap
updmap-map --
So simply spelt 'updmap-map', I guess.
> Cheers
--
“We are all in the gutter, but some
On Mon, Jul 29, 2019 at 08:25:42PM +0100, Rodolfo Medina wrote:
> Hi all.
>
> On my Debian Stretch box, the `updmap-user' command is declared `not found'
> although the package texlive-base is installed. Why?
>
> Please help.
Those are the similar commands I see:
tomas@trotzki:~$ man -k updm
Hi all.
On my Debian Stretch box, the `updmap-user' command is declared `not found'
although the package texlive-base is installed. Why?
Please help.
Thanks in advance,
Rodolfo
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
> > > To: debian-user@lists.debian.org
> > > Subject: "command not found&q
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
fo
On Tue, 6 Dec 2016 14:21:23 -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 lik
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 aug
c 2016, Bob Holtzman wrote:
> > Date: Tue, 6 Dec 2016 16:21:23
> > From: Bob Holtzman
> > To: debian-user@lists.debian.org
> > Subject: "command not found"
> > Resent-Date: Tue, 6 Dec 2016 21:21:52 + (UTC)
> > Resent-From: debian-user@lists.debian.o
n
To: debian-user@lists.debian.org
Subject: "command not found"
Resent-Date: Tue, 6 Dec 2016 21:21:52 + (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.
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 com
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 an
On Sun, 20 Dec 2015, Bob Holtzman wrote:
When I had to put down my old guy and best friend "Num Nutz" I
cried more than I did at my mother's funeralso I know the
feeling.
Yes. Some may want to complain that this exchange is OT, but I
submit that this Christmas week, with the world seemin
On Sat, Dec 19, 2015 at 07:19:17PM -0500, Bob Bernstein wrote:
> On Sat, 19 Dec 2015, Curt wrote:
>
> >My cat died and I don't want another because of the heartbreak I
> >went through.
>
> I am so sorry for your loss, which very clearly was a *major* one.
> Try to give yourself enough time to gri
On Sat, 19 Dec 2015, Curt wrote:
My cat died and I don't want another because of the heartbreak
I went through.
I am so sorry for your loss, which very clearly was a *major*
one. Try to give yourself enough time to grieve; there's no
telling how long that will take. There's no FAQ for grief,
On Fri 18 Dec 2015 at 10:09:30 -0700, Bob Holtzman wrote:
> On Fri, Dec 18, 2015 at 09:49:59AM +, Brian wrote:
> >
> > The guts of my ~/.fetchmailrc are
> >
> > poll
> > protopop3
> > user
> > password
> > ssl
> >
> > 'fetchmail -c -v' for testing.
>
> Mine i
On 2015-12-18, Ric Moore wrote:
I just don't, for my use, like a lot of what IMAP does.
>
> I use POP. Nuff said. :) Ric
And I don't give a shit what you use. I don't have a car and bought my
first cell phone six months ago. My cat died and I don't want another
because of the heartbrea
On Friday 18 December 2015 14:02:52 Martin Read wrote:
> On 18/12/15 18:14, Gene Heskett wrote:
> > Ok, I have constructed a recursive pull ~/.wgetrc, but all I get are
> > syntax errors. The file: (which kmail cannit insert, so copy-paste)
> > gene@coyote:~/Documents/dovecot-wiki$ cat ~/.wgetrc
On Fri, 18 Dec 2015 16:33:14 -0500 (EST)
Bob Bernstein wrote:
> On Fri, 18 Dec 2015, Gene Heskett wrote:
>
> > A mailfile, as I understand it, is the whole thing merged into
> > one file, with a blank line or something as a separator, and
> > an index file containing the starting offset and re
On Fri, 18 Dec 2015, Gene Heskett wrote:
A mailfile, as I understand it, is the whole thing merged into
one file, with a blank line or something as a separator, and
an index file containing the starting offset and read status
of each message in the main file to speed up the search for
new mai
On 12/18/2015 10:19 AM, Petter Adsen wrote:
On Fri, 18 Dec 2015 09:31:45 -0500
Gene Heskett wrote:
On Friday 18 December 2015 05:32:01 Lisi Reisz wrote:
Having just by implication been told by someone that only muggles,
lusers and/or dinosaurs use POP3, how many others of us will admit
to it?
On 18/12/15 18:14, Gene Heskett wrote:
Ok, I have constructed a recursive pull ~/.wgetrc, but all I get are
syntax errors. The file: (which kmail cannit insert, so copy-paste)
gene@coyote:~/Documents/dovecot-wiki$ cat ~/.wgetrc
-np
--follow-ftp
-r
-l 20
-k
Using "info wget" to read the wget us
On Friday 18 December 2015 12:23:25 Petter Adsen wrote:
> On Fri, 18 Dec 2015 11:07:57 -0500
>
> Gene Heskett wrote:
> > On Friday 18 December 2015 10:19:46 Petter Adsen wrote:
> > > If you want to try setting up a Dovecot server, there are lots of
> > > good tutorials and other docs out there. I
On Fri, 18 Dec 2015 11:07:57 -0500
Gene Heskett wrote:
> On Friday 18 December 2015 10:19:46 Petter Adsen wrote:
> > If you want to try setting up a Dovecot server, there are lots of
> > good tutorials and other docs out there. I can probably dig up
> > links to the pages I used for setting up my
; On Wed, Dec 16, 2015 at 12:06:14AM -0500, Bob Bernstein wrote:
> > > > > Please post your .fetchmailrc, obfuscating any identifying
> > > > > information in it.
> > > > >
> > > > > Scripts can yield up a "command not found"
On Friday 18 December 2015 16:07:57 Gene Heskett wrote:
> And I was confused, I meant dovecot, not icedove, and whose magic crystal
> ball issues these names anyway? :) icedove is of course t-bird, without
> the branding.
Phew. Glad it wasn't me. I couldn't make sense of "Icedove", but there is
On Friday 18 December 2015 10:19:46 Petter Adsen wrote:
> On Fri, 18 Dec 2015 09:31:45 -0500
>
> Gene Heskett wrote:
> > On Friday 18 December 2015 05:32:01 Lisi Reisz wrote:
> > > Having just by implication been told by someone that only muggles,
> > > lusers and/or dinosaurs use POP3, how many
On Friday 18 December 2015 10:19:46 Petter Adsen wrote:
> On Fri, 18 Dec 2015 09:31:45 -0500
>
> Gene Heskett wrote:
> > On Friday 18 December 2015 05:32:01 Lisi Reisz wrote:
> > > Having just by implication been told by someone that only muggles,
> > > lusers and/or dinosaurs use POP3, how many
On Friday 18 December 2015 09:54:54 Bob Bernstein wrote:
> Gene: I'm unfamiliar with the term "mailfile." Can you expand a
> tad on that? Q'est-ce que?
A mailfile, as I understand it, is the whole thing merged into one file,
with a blank line or something as a separator, and an index file
conta
On Fri, 18 Dec 2015 09:31:45 -0500
Gene Heskett wrote:
> On Friday 18 December 2015 05:32:01 Lisi Reisz wrote:
> > Having just by implication been told by someone that only muggles,
> > lusers and/or dinosaurs use POP3, how many others of us will admit
> > to it? (For the avoidance of doubt, I us
Gene: I'm unfamiliar with the term "mailfile." Can you expand a
tad on that? Q'est-ce que?
--
Bob Bernstein
On Friday 18 December 2015 07:13:42 Brad Rogers wrote:
> On Fri, 18 Dec 2015 07:57:37 -0300
> Renaud (Ron) OLGIATI wrote:
>
> Hello Renaud,
>
> >backwoods and using POP3 (and refusing systemd...)
>
> Using POP3 here, too. I don't need access 24/7 worldwide to all my
> emails. And frankly, leavi
On Friday 18 December 2015 05:32:01 Lisi Reisz wrote:
> On Friday 18 December 2015 09:49:59 Brian wrote:
> > > > > > > Also, run 'fetchmail --version' for debugging info.
> >
> > The guts of my ~/.fetchmailrc are
> >
> > poll
> > protopop3
> > user
> > password
> > ssl
On Fri, 18 Dec 2015 07:57:37 -0300
Renaud (Ron) OLGIATI wrote:
Hello Renaud,
>backwoods and using POP3 (and refusing systemd...)
Using POP3 here, too. I don't need access 24/7 worldwide to all my
emails. And frankly, leaving (some of my personal) emails on a server I
have no control over is a
On Friday 18 December 2015 11:26:35 Joe wrote:
> On Fri, 18 Dec 2015 10:32:01 +
>
> Lisi Reisz wrote:
> > On Friday 18 December 2015 09:49:59 Brian wrote:
> > > > > > > > Also, run 'fetchmail --version' for debugging info.
> > >
> > > The guts of my ~/.fetchmailrc are
> > >
> > > poll
>
On Fri, 18 Dec 2015 10:32:01 +
Lisi Reisz wrote:
> On Friday 18 December 2015 09:49:59 Brian wrote:
> > > > > > > Also, run 'fetchmail --version' for debugging info.
> >
> > The guts of my ~/.fetchmailrc are
> >
> > poll
> > protopop3
> > user
> > password
> > ssl
On Fri, 18 Dec 2015 10:32:01 +
Lisi Reisz wrote:
> Having just by implication been told by someone that only muggles, lusers
> and/or dinosaurs use POP3, how many others of us will admit to it? (For the
> avoidance of doubt, I use POP3.)
I am also one of the unenlightened users, making gr
On Friday 18 December 2015 09:49:59 Brian wrote:
> > > > > > Also, run 'fetchmail --version' for debugging info.
>
> The guts of my ~/.fetchmailrc are
>
> poll
> protopop3
> user
> password
> ssl
>
> 'fetchmail -c -v' for testing.
Having just by implication been told
; > 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
on 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
> > > _examp
On Wednesday 16 December 2015 13:05:22 Bob Holtzman wrote:
> On Wed, Dec 16, 2015 at 12:06:14AM -0500, Bob Bernstein wrote:
> > Please post your .fetchmailrc, obfuscating any identifying
> > information in it.
> >
> > Scripts can yield up a "command not found&quo
On Wed 16 Dec 2015 at 11:05:22 -0700, Bob Holtzman wrote:
> On Wed, Dec 16, 2015 at 12:06:14AM -0500, Bob Bernstein wrote:
> > Please post your .fetchmailrc, obfuscating any identifying
> > information in it.
> >
> > Scripts can yield up a "command not found&quo
On Wed, Dec 16, 2015 at 12:06:14AM -0500, Bob Bernstein wrote:
> 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 calle
512/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 libr
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 _ex
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
Regi
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
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
ching 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 "fet
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 f
s 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
all. 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". P
; >
> > 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.
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
w 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
; >
> > 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.
ding 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
>
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
Probably a missing library.
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
s 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
> noth
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.
uot;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.
On Fri, May 01, 2015 at 12:12:43PM +, T o n g wrote:
> Hi,
>
> Having installed extlinux in sid, I still don't have the /boot/extlinux/
> linux.cfg file, so I tried to run extlinux-update to generate one.
> However, I got:
>
> extlinux-update: command
Hi,
Having installed extlinux in sid, I still don't have the /boot/extlinux/
linux.cfg file, so I tried to run extlinux-update to generate one.
However, I got:
extlinux-update: command not found
Also, https://packages.debian.org/search?
searchon=contents&keywords=extlinux-
up
On 16/11/2014 17:01, Ron Leach wrote:
ron@d7server:~$ ssh-keygen
-bash: ssh_keygen : command not found
ron@d7server:~$
Idiot.
I've been typing ssh_keygen .
Apologies to the list. And thanks to Lisi and Ansgar.
Don't you ever only see it after it's too late.
Sor
Hi.
On Sun, 16 Nov 2014 17:01:41 +
Ron Leach wrote:
> I hesitate to trouble the list with this but, when trying to generate
> a key pair on a (lenny) system recently upgraded to wheezy, 7.7, I am
> seeing this:
>
> ron@d7server:~$ ssh-keygen
> -bash: ssh_keygen : comma
Hi,
Ron Leach writes:
> I hesitate to trouble the list with this but, when trying to generate
> a key pair on a (lenny) system recently upgraded to wheezy, 7.7, I am
> seeing this:
>
> ron@d7server:~$ ssh-keygen
> -bash: ssh_keygen : command not found
Hmm, bash complainin
On Sunday 16 November 2014 17:01:41 Ron Leach wrote:
> I hesitate to trouble the list with this but, when trying to generate
> a key pair on a (lenny) system recently upgraded to wheezy, 7.7, I am
> seeing this:
>
> ron@d7server:~$ ssh-keygen
> -bash: ssh_keygen : command not fo
I hesitate to trouble the list with this but, when trying to generate
a key pair on a (lenny) system recently upgraded to wheezy, 7.7, I am
seeing this:
ron@d7server:~$ ssh-keygen
-bash: ssh_keygen : command not found
ron@d7server:~$
Aptitude says that openssh-client, version 1:6.0p1-4+deb7
1 - 100 of 350 matches
Mail list logo
