Bernard Schoenacker a écrit :
> Je recherche un moyen de pouvoir afficher un caractère par lettre ou
> signe lorsque l'opérateur inscrit son mot de passe, cette solution est
> employée sur Debian facile comme distro...
Cf. script ci-dessous :
Bonjour,
Je recherche un moyen de pouvoir afficher un caractère par lettre ou signe
lorsque l'opérateur inscrit son mot de passe, cette solution est employée
sur Debian facile comme distro...
Merci pour votre aimable attention
Bien à vous
Bernard
Thanks a lot @Will Mengarini
On Wed, Jan 12, 2022 at 8:21 PM Will Mengarini wrote:
> * Yamada??? [22-01/12=We 20:10 +0800]:
> > Do you mean if .bash_profile exists, .bashrc will be ignored?
>
> Sometimes. From `man bash`:
> When bash is invoked as an inter
* Yamada??? [22-01/12=We 20:10 +0800]:
> Do you mean if .bash_profile exists, .bashrc will be ignored?
Sometimes. From `man bash`:
When bash is invoked as an interactive login shell, or as a
non-interactive shell with the --login option, it first reads
and executes commands from the f
* Yamada??? [22-01/12=We 19:49 +0800]:
> I have a .bashrc file in my home dir, whose content is shown as follows.
> But every time I log into the system, I have to source this file by hand.
>
> $ which scala
> /usr/bin/scala
>
> $ cat .bashrc
> #THIS MUST BE AT THE EN
Do you mean if .bash_profile exists, .bashrc will be ignored?
Thanks.
On Wed, Jan 12, 2022 at 8:07 PM Will Mengarini wrote:
> * Yamada??? [22-01/12=We 19:49 +0800]:
> > I have a .bashrc file in my home dir, whose content is shown as follows.
> > But every time I log into the
Hello list
I have a .bashrc file in my home dir, whose content is shown as follows.
But every time I log into the system, I have to source this file by hand.
$ which scala
/usr/bin/scala
$ cat .bashrc
#THIS MUST BE AT THE END OF THE FILE FOR SDKMAN TO WORK!!!
export SDKMAN_DIR="$HOME/.s
of the alias statements
in my user .bashrc are no longer working!.
The strange thing is that some still are working. Also, if I enter the
complete path to an executable whose alias is NOT working, the
executable works Reentering the alias statement in .bashrc does not
restore the function
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Stephen P. Molnar wrote:
> The subject line tells it all!? Debian Stretch (64bit).
>
> Without warning, or any other indications, some of the alias statements
> in my user .bashrc are no longer working!.
>
> The strange thing
The subject line tells it all!? Debian Stretch (64bit).
Without warning, or any other indications, some of the alias statements
in my user .bashrc are no longer working!.
The strange thing is that some still are working. Also, if I enter the
complete path to an executable whose alias
Thanks for the reply.
Adding the lines from your .bash_profile to mine restored the
functionality of .bashrc.
I don't have any backups of .bash_profile, but I would guess the the HEX
installation script woped out the origional .bash_profile. ( I try to
never assume anything as we all know
On Wed, Apr 25, 2018 at 10:49:52PM +0300, Abdullah Ramazanoglu wrote:
> It seems like when ~/.bash_profile did not exist, then ~/.bashrc is called
> directly.
That's not correct.
As a LOGIN shell, bash reads ONE file, searching among the following items
in sequence:
a) ~/.bash_pro
On Wed, Apr 25, 2018 at 03:34:02PM -0400, Stephen P. Molnar wrote:
> Bu bumbling about I discovered
> the it is necessary to source .bashrc inorder to recticate the alias lines
> in .bashrc (note: commenting out the added lines in .bash_profile did not
> solve the problem).
>
On Wed, 25 Apr 2018 15:34:02 -0400 Stephen P. Molnar said:
> What's going on what is the fix?
It seems like when ~/.bash_profile did not exist, then ~/.bashrc is called
directly. However, when ~/.bash_profile did exist, then it is called *instead
of* ~/.bashrc and it is up to ~/.bash_prof
Hello,
On Wed, Apr 25, 2018 at 03:34:02PM -0400, Stephen P. Molnar wrote:
> Whie the additional lines are necessary for the execution of HEX they seem
> to have wiped oour all of the alias entries I have in .bashrc. Rebooting
> the system does not eliminate the problem! Bu bumblin
=8.0.0
export PATH=${PATH}:${HEX_ROOT}/bin
export HEX_CACHE=/home/comp/Apps/Hex/hex_cache
Whie the additional lines are necessary for the execution of HEX they
seem to have wiped oour all of the alias entries I have in .bashrc.
Rebooting the system does not eliminate the problem! Bu bumbling
Le 28/08/2017 à 19:42, Étienne Mollier a écrit :
> G2PC, le 2017-08-28 :
>> Mon shell est zsh.
>>
>> [...]
>>
>> Recharger .bashrc avec la commande source ~/.bashrc
>>
>> J'ai une erreur avec mon .bashrc
>> source ~/.bashrc
>> /home/root/.
G2PC, le 2017-08-28 :
> Mon shell est zsh.
>
> [...]
>
> Recharger .bashrc avec la commande source ~/.bashrc
>
> J'ai une erreur avec mon .bashrc
> source ~/.bashrc
> /home/root/.bashrc:16: command not found: shopt
> /home/root/.bashrc:24: command not found: shopt
>
Le 28/08/2017 à 15:14, Francois Lafont a écrit :
> Bonjour,
>
> On 08/28/2017 03:02 PM, G2PC wrote:
>
>> Pouvez vous m'aider pour .bashrc ? J'ai ajouté des alias, mais,
>> je n'arrive pas à recharger le .bashrc Mon shell est zsh.
> Sauf erreur, le .bashrc, comme so
Bonjour,
On 08/28/2017 03:02 PM, G2PC wrote:
> Pouvez vous m'aider pour .bashrc ? J'ai ajouté des alias, mais,
> je n'arrive pas à recharger le .bashrc Mon shell est zsh.
Sauf erreur, le .bashrc, comme son nom l'indique, c'est pour
shell bash. Si tu utilises zsh, alors il doit y avoi
Bonjour, Pouvez vous m'aider pour .bashrc ? J'ai ajouté des alias, mais,
je n'arrive pas à recharger le .bashrc Mon shell est zsh. Exemples pour
des alias avec apt-get
alias search='apt-cache search'
alias show='apt-cache show'
alias install='sudo apt-get install'
alias remove='sudo apt-get
Hello José,
José Luis Segura Lucas josel.seg...@gmx.es wrote:
In one (and only one) of then, when I open a terminal or connect by SSH,
my bash load the default system configuration from /etc/bash.bashrc,
instead of reading, as usual, ~/.bashrc.
I can think that I don't really have
like the following:
# if running bash
if [ -n $BASH_VERSION ]; then
# include .bashrc if it exists
if [ -f $HOME/.bashrc ]; then
. $HOME/.bashrc
fi
fi
which is also in the .profile in /etc/skel/, I therefore assume that
this is currently shipped with Debian.
I suggest
On Sat, Jun 23, 2012 at 05:24:59PM +0200, José Luis Segura Lucas wrote:
You are right: I have the ~/.profile file missing. I don't know how can
I miss this file, but it didn't exist at all. I copied this from another
computer and it works.
tal% less .profile
# ~/.profile: executed by the
Hello José,
José Luis Segura Lucas josel.seg...@gmx.es wrote:
I don't remember to write or generate by hand this ~/.profile. Is it
created automatically?
It should be created automatically from the files in /etc/skel/ if
you are using useradd or adduser (the former with the --create-home
, as usual, ~/.bashrc.
I can think that I don't really have a ~/.bashrc (or have a mispelling
on the file name), but if I run bash from the terminal, my configuration
file in ~/.bashrc is loaded.
I add an echo on each files before sending you my problem to check
that the problem
Hi,
I was tried Gentoo Linux system but after a while I come back to Debian
GNU/Linux system again on my PC Box.
So, in my /home/csanyipal/ directory there remain some dot files from
Gentoo system, eg.: .bashrc, .bash_profile.
When I installed 64bit Debian GNU/Linux Squeeze, I used my $HOME
, Csanyi Pal csanyi...@gmail.com wrote:
Hi,
I was tried Gentoo Linux system but after a while I come back to Debian
GNU/Linux system again on my PC Box.
So, in my /home/csanyipal/ directory there remain some dot files from
Gentoo system, eg.: .bashrc, .bash_profile.
When I installed 64bit
Csanyi Pal:
When I installed 64bit Debian GNU/Linux Squeeze, I used my $HOME
directory with it's dot files too.
So, I think the .bashrc and .bash_profile remain in the state in which
was on Gentoo.
Yes, that's how it should be. Debian package managers must never touch
anything under /home
or
something)
After I copy .bashrc and .profile to my $HOME directory, and setup owner
for these files to be owned by user: by me, everything back to the
normal. Thanks!
OK, I edited these files and add some lines there, like:
EDITOR=emacsclient; export EDITOR
--
Regards, Paul Chany
http
2010/8/16 Ronaldo Reis Junior chrys...@gmail.com
Pessoal,
estou usando o debian testing/unstable. Tem alguns comandos que preciso que
rode assim que faço o login em meu ambiente (icewm ou kde) mas o GDM não
está rodando o meu .bashrc. Assim sempre que logo tenho que abrir o xterm
para que
não está rodando o meu .bashrc. Assim sempre que
logo tenho que abrir o xterm para que ele rode o .bashrc e com isto
defina algumas variáveis.
Como faço para corrigir isto?
Eu já ouvi alguém falar num tal de '.gnomerc'. Já testou isso ?
Uso o '.xsessionrc'. Não sei se é o recomendado
Quando vc loga no KDE, eh executado um shell de login, ou não-interativo.
Nesse momento, o GDM (ou KDE?) procura por um arquivo de perfil para ler
(.profile ou .bash_profile -- este último tem precedência sobre o .profile).
Ou seja, provavelmente vc quer utilizar o arquivo .bash_profile, se o
Use este arquivo aqui:
/etc/gdm/PostLogin/Default
como já foi falado vc só usa o .bashrc quando executa um console/terminal.
Em 16 de agosto de 2010 12:40, Ronaldo Reis Junior chrys...@gmail.comescreveu:
Pessoal,
estou usando o debian testing/unstable. Tem alguns comandos que preciso que
Pessoal,
estou usando o debian testing/unstable. Tem alguns comandos que preciso
que rode assim que faço o login em meu ambiente (icewm ou kde) mas o GDM
não está rodando o meu .bashrc. Assim sempre que logo tenho que abrir o
xterm para que ele rode o .bashrc e com isto defina algumas
2010/8/16 Ronaldo Reis Junior chrys...@gmail.com
estou usando o debian testing/unstable. Tem alguns comandos que preciso que
rode assim que faço o login em meu ambiente (icewm ou kde) mas o GDM não
está rodando o meu .bashrc. Assim sempre que logo tenho que abrir o xterm
para que ele rode o
Bonsoir,
Je poste dans cette liste parce que j'utilisais cette fonction sous
FreeBSD+tcsh et qu'après recherches, je ne comprends pas ce qui se passe
sous debian+bash
J'utilise une fonction dans '.bashrc' basée sur 'find' et utilisant le
paramètre '-prune' pour simplifier des recherches en
Boyd Stephen Smith Jr. wrote:
On Wednesday 19 November 2008, tyler [EMAIL PROTECTED] wrote
about 'Re: Which files do what: .bashrc and friends':
I believe .profile and .bash_profile are synonyms, so you'd only use one
or the other.
.profile is only used by bash when it cannot find
On a Debian-based system running KDE 3.5.10 I see several files that
are used when logging in / starting a Konsole:
.profile
.bash_history
.bash_logout
.bash_profile
.bashrc
I imagine three times these files might be used:
1) When logging in
2) When starting Konsole
3) When running a shell
Dotan Cohen [EMAIL PROTECTED] writes:
On a Debian-based system running KDE 3.5.10 I see several files that
are used when logging in / starting a Konsole:
.profile
.bash_history
.bash_logout
.bash_profile
.bashrc
Thanks in advance. If there are any good docs that explain this, I'd
love
2008/11/19 tyler [EMAIL PROTECTED]:
Dotan Cohen [EMAIL PROTECTED] writes:
On a Debian-based system running KDE 3.5.10 I see several files that
are used when logging in / starting a Konsole:
.profile
.bash_history
.bash_logout
.bash_profile
.bashrc
Thanks in advance. If there are any
Dotan Cohen [EMAIL PROTECTED] writes:
2008/11/19 tyler [EMAIL PROTECTED]:
Dotan Cohen [EMAIL PROTECTED] writes:
On a Debian-based system running KDE 3.5.10 I see several files that
are used when logging in / starting a Konsole:
.profile
.bash_history
.bash_logout
.bash_profile
.bashrc
I believe equivalent to .profile
.bashrc
Run once for each interactive shell, after .profile
The main difference between .profile and .bashrc is that
.profile only gets run when you start a login shell,
but .bashrc gets run for all shells.
So, for example, if you use
$ su -
you'll run
On Wednesday 19 November 2008, tyler [EMAIL PROTECTED] wrote
about 'Re: Which files do what: .bashrc and friends':
I believe .profile and .bash_profile are synonyms, so you'd only use one
or the other.
.profile is only used by bash when it cannot find .bash_profile. .profile
is also used
On Wednesday 19 November 2008, Dotan Cohen [EMAIL PROTECTED] wrote about
'Re: Which files do
what: .bashrc and friends':
1) Is a login shell run when the user logs onto KDE (even though he
does not see a konsole window)?
Nope a login shell is when bash is executed with the -l option, or having
Boyd Stephen Smith Jr. [EMAIL PROTECTED] writes:
On Wednesday 19 November 2008, Dotan Cohen [EMAIL PROTECTED] wrote about
'Re: Which files do
what: .bashrc and friends':
1) Is a login shell run when the user logs onto KDE (even though he
does not see a konsole window)?
Nope a login shell
) is installed file /etc/kde3/kdm/Xsession
executes user's login shell, for example $HOME/.bash_profile which in
turn might source .bashrc too.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Dotan Cohen a écrit :
Thanks in advance. If there are any good docs that explain this, I'd
love to see them. I have not been able to google anything recent that
is relevant to Debian.
Quick'n dirty solution :
Another way to know, even if it does not cover all cases, is to put the
following
Mike McCarty [EMAIL PROTECTED]:
Dotan Cohen wrote:
.bashrc
Run once for each interactive shell, after .profile
... if called by .profile or .bash_profile.
A long time ago, this was automatic (a la ksh and ENV; if ENV =
~/.kshrc, then ~/.kshrc was run on login shell invocation). Every
exits, bash reads and executes commands from the
file ~/.bash_logout, if it exists.
When an interactive shell that is not a login shell is started, bash
reads and executes commands from /etc/bash.bashrc and ~/.bashrc, if
these files exist. This may be inhibited by using
system. My .bash_profile and .bashrc files were the
default files loaded during the install. However, my PATH remains
unchanged when I log on even though the .bash_profile file has the
lines to add my ~/bin directory. I can make the change manually after
I've logged on and can execute files
.bash_profile and .bashrc files were the
default files loaded during the install. However, my PATH remains
unchanged when I log on even though the .bash_profile file has the
lines to add my ~/bin directory. I can make the change manually after
I've logged on and can execute files
a ~/bin
directory to my system. My .bash_profile and .bashrc files were the
default files loaded during the install. However, my PATH remains
unchanged when I log on even though the .bash_profile file has the
lines to add my ~/bin directory. I can make the change manually after
I've logged
I'm a new user to Debian Linux. I have the latest version loaded on a
dedicated PC with all the default settings. I have added a ~/bin directory
to my system. My .bash_profile and .bashrc files were the default files
loaded during the install. However, my PATH remains unchanged when I log
On Saturday 12 January 2008 20:50 John Salmon wrote:
I'm a new user to Debian Linux. I have the latest version loaded on a
dedicated PC with all the default settings. I have added a ~/bin directory
to my system. My .bash_profile and .bashrc files were the default files
loaded during
I've just discovered that a stable install (4.0, (with rdiff-backup
pulled from testing)) has a wonky (that's a technical term, you
understand ... ;-) ) /etc/skel/bashrc apparently.
If I ssh in as a freshly-created user and then run the set command, I
get pages and pages of script-looking
On Tue, Sep 18, 2007 at 10:08:35 -0500, Kent West wrote:
I've just discovered that a stable install (4.0, (with rdiff-backup pulled
from testing)) has a wonky (that's a technical term, you understand ... ;-)
) /etc/skel/bashrc apparently.
If I ssh in as a freshly-created user and then run
On 09/18/2007 10:08 AM, Kent West wrote:
I've just discovered that a stable install (4.0, (with rdiff-backup
pulled from testing)) has a wonky (that's a technical term, you
understand ... ;-) ) /etc/skel/bashrc apparently.
[...]
I don't see anything particularly odd in /etc/skel/bashrc
On Tue, Aug 21, 2007 at 04:14:04PM -0700, Dr. Jennifer Nussbaum wrote:
PS1='\h\w $ '; export PS1
So, nothing fancy. How do i get my coloured ls back,
and my # prompt as sudo'ed root?
Use \$ rather than a plain $ to get # as root.
A.
--
Ansgar Esztermann
Researcher Sysadmin
) .bashrc file,
and now i dont have the colored output and sudoing to
root
leaves me with a $ prompt. (I do reset my PS1 line,
but i dont know how to have a different one for root,
keeping
the #.) Can someone give me a suggestion? My
complete
.bashrc, less comments, and with my CVSROOT masked
# prompt as root.
I then copied over my (straightforward) .bashrc file,
and now i dont have the colored output and sudoing to
root
leaves me with a $ prompt. (I do reset my PS1 line,
but i dont know how to have a different one for root,
keeping
the #.) Can someone give me a suggestion? My
duplicat a dos llocs. En fi, potser posant un
source ~/.environment en el .Xsession i en el .bashrc i llavors
definir totes les variables en aquest fitxer, però em pregunto si
hi ha algun sistema estàndard de fer-ho. Ho dic perquè si vas
xapusses d'aquestes al final et tornes boig per trobar les coses
El Friday 18/05/07, a les 01:45 (+0200), Orestes Mas va escriure:
A Divendres 18 Maig 2007 00:15, Ernest Adrogué va escriure:
Hola nanos,
A veure, el problema que tinc és que el Gnome/GDM no llegeix el
fitxer .bashrc a l'arrencada, per tant si canvio el PATH, etc. o
les variables
Marc Shapiro wrote:
Lorenzo Bettini wrote:
Hi
on the standard user's home I use everyday I have the .bashrc file
that is read upon login.
Now I created a brand new user (with adduser), but the .bashrc file I
inserted in his home is never read upon login... in /etc/profile and
/etc
Ali Jawad wrote:
I remember that the files are read like
/etc/profile - ~/.bash_profile - ~/.bashrc - ~./profile
but the bashrc file should be created by default without you having to
insert it..
that's what I thought too, but neither .bashrc nor .bash_profile were
created automatically
On Tue, Dec 26, 2006 at 10:53:27AM +0100, Lorenzo Bettini wrote..
I remember that the files are read like
/etc/profile - ~/.bash_profile - ~/.bashrc - ~./profile
but the bashrc file should be created by default without you
having to insert it..
that's what I thought too
Hi
on the standard user's home I use everyday I have the .bashrc file that
is read upon login.
Now I created a brand new user (with adduser), but the .bashrc file I
inserted in his home is never read upon login... in /etc/profile and
/etc/bash.profile the .bashrc is actually never read
Lorenzo Bettini wrote:
Hi
on the standard user's home I use everyday I have the .bashrc file
that is read upon login.
Now I created a brand new user (with adduser), but the .bashrc file I
inserted in his home is never read upon login... in /etc/profile and
/etc/bash.profile the .bashrc
I remember that the files are read like
/etc/profile - ~/.bash_profile - ~/.bashrc - ~./profile
but the bashrc file should be created by default without you having to
insert it..
On 12/25/06, Lorenzo Bettini [EMAIL PROTECTED] wrote:
Hi
on the standard user's home I use everyday I have
Ich habe einen Shellzugang und dort keine Rootrechte.
In der lokalen .bashrc finde ich:
# .bashrc
# User specific aliases and functions
# Source global definitions
if [ -f /etc/bashrc ]; then
. /etc/bashrc
fi
/etc/bashrc kann ich nur lesen, auch klar und dort ist nano definiert, den
On Wed, 25 Oct 2006 16:24:22 +0200 Al Bogner wrote:
Ich habe einen Shellzugang und dort keine Rootrechte.
In der lokalen .bashrc finde ich:
# .bashrc
# User specific aliases and functions
# Source global definitions
if [ -f /etc/bashrc ]; then
. /etc/bashrc
fi
/etc/bashrc
Am Mittwoch, 25. Oktober 2006 16:38 schrieb Evgeni Golov:
On Wed, 25 Oct 2006 16:24:22 +0200 Al Bogner wrote:
Ich habe einen Shellzugang und dort keine Rootrechte.
In der lokalen .bashrc finde ich:
# .bashrc
# User specific aliases and functions
# Source global definitions
if [ -f
Am Mittwoch, 25. Oktober 2006 19:15 schrieb Al Bogner:
So klappt es leider nicht. Wenn ich mutt aufrufe, dann startet noch immer
nano als Editor.
cat .bash_profile
# .bash_profile
# Get the aliases and functions
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi
# User specific
On Wed, Oct 25, 2006 at 07:21:04PM +0200, Al Bogner wrote:
export VISUAL==/usr/bin/vim
Klappt doch, das 2. = war natürlich zu viel.
Grundsaetzlich immer funktionieren Konstrukte wie
alias mutt='EDITOR=vim mutt'
cu
ulf
--
Ulf Volmer
[EMAIL PROTECTED]
www.u-v.de
--
Haeufig gestellte
* Al Bogner [EMAIL PROTECTED] wrote:
So klappt es leider nicht. Wenn ich mutt aufrufe, dann startet noch immer
nano
als Editor.
Hast du die .bash_profile auch eingelesen?
Den Editor für mutt kannst du ausserdem auch in der .muttrc angeben,
vielleicht ist der ja auch in einer globalen
an interactive shell that is not a login shell is started,
bash reads and executes commands from /etc/bash.bashrc and
~/.bashrc, if these files exist. This may be inhibited by using the
--norc option. The --rcfile file option will force bash to read and
execute commands from file
Nein, ganz so einfach ist es nicht. Denn:
a) die shell ist klar eine login shell
b) ich habe die --noprofile option NICHT angegeben
c) ~/.bash_profile ist definitiv da und wird aber trotzdem
bei ssh logins NICHT gesourced (~/.bashrc ist auch da und wird
explizit von der ~/.bash_profile aus
uups, ich hab mir jetzt die man page passage nochmal durchgelesen (und
nicht nur cp). ich würde meinen, als ich das problem hatte, lautete
diese noch anders. jedenfalls war mein fix der, dass ich in der .profile
die .bashrc source.
cu marc
Holger Rauch wrote:
Nein, ganz so einfach ist es nicht
Hallo Marc (und auch an die anderen),
mittlerweile hab ich das eigentliche Problem entdeckt:
Ich vergaß beim Anlegen der accounts mit useradd, den switch -s
für die login shell mitzugeben und nahm fälschlicherweise an, daß auch in
diesem Fall /bin/bash als login shell in die /etc/passwd
On Oct 24, Holger Rauch wrote:
Ich vergaß beim Anlegen der accounts mit useradd, den switch -s
für die login shell mitzugeben und nahm fälschlicherweise an, daß auch in
diesem Fall /bin/bash als login shell in die /etc/passwd eingetragen wird
(weil die bash ja unter Linux sowieso default
* Andreas Putzo:
Allerdings ist /bin/sh normalerweise ein Link auf /bin/bash.
Verhält sich die bash anders, wenn sie als /bin/sh gestartet wird?
Ja: Schau mal in der manpage unter „--norc“.
Andreas
--
The whole world is a tuxedo and you are a pair of brown shoes.
-- George
~/.bashrc if the shell is interactive. This option is on by
default if the shell is invoked as sh.
Schönen Gruß,
Wolf
--
Jetzt ist Frühlingszeit - Zeit für neue, jahreszeitbedingte Bauernregeln: Die
Frühlingsluft riecht frisch und zärtlich, der Winter sagt: Ich habe fertig
Hallo,
ich habe bei einem neu aufgesetzten Testing (Etch) System das Problem, daß
nach einem ssh login die .bash_profile und die .bashrc im HOME-Verzeichnis
eines Benutzers nicht mehr gesourced werden.
Wenn ich auf diesem neu installierten System von einem user mittels
su - user_name auf einen
su amavis
mache, die Loginshell (.bashrc) nicht greift?
Du kannst dich z.B. an einer der konsolen einloggen und es da testen.
--
Viele Gruesse, Kind regards,
Jim Knuth
[EMAIL PROTECTED]
ICQ #277289867
--
Zufalls-Zitat
--
Eine Betriebsanalyse ist eine kostspielige Methode
Jim Knuth schrieb:
das heisst, dass wenn ich als root eingeloggt bin und su amavis
mache, die Loginshell (.bashrc) nicht greift?
su - amavis
dann sollte auch das environment richtig eingelesen werden.
--
Bye,
Patrick Cornelissen
http://www.p-c-software.de
ICQ:15885533
signature.asc
heisst, dass wenn ich als root eingeloggt bin und su amavis
mache, die Loginshell (.bashrc) nicht greift?
.bashrc wird beim starten einer neuen shell eingelesen. .profile ist
fuer Login-Shells zustaendig. su username startet aber nur ne neue
Shell mit ner anderen uid, keine login-shell. Dafuer
nicht wenn du ein neues Xterm
oder so oeffnest.
das heisst, dass wenn ich als root eingeloggt bin und su amavis
mache, die Loginshell (.bashrc) nicht greift?
.bashrc wird beim starten einer neuen shell eingelesen. .profile ist
fuer Login-Shells zustaendig. su username startet aber nur ne
Am Donnerstag 05 Oktober 2006 02:53 schrieb Jim Knuth:
nein. Steht auch alles drin. ;) Ich würde nur gern auch bei allen
Usern die shell farbig haben. Kriegs nicht hin. Hab schon im home
des Users ne .bashrc und/oder .profile angelegt. Mit dem gleichen
Inhalt, den root hat. Denn da
Jim Knuth schrieb:
und das funktioniert eben bei mir NICHT :(
Wie hast du das getestet?
Loginshells werden nur beim logingelesen nicht wenn du ein neues Xterm
oder so öffnest.
Du kannst dich z.B. an einer der konsolen einloggen und es da testen.
--
Bye,
Patrick Cornelissen
at Donnerstag, 5. Oktober 2006 02:53 wrote Jim Knuth:
nein. Steht auch alles drin. ;) Ich würde nur gern auch bei allen
Usern die shell farbig haben. Kriegs nicht hin. Hab schon im home
des Users ne .bashrc und/oder .profile angelegt. Mit dem gleichen
Inhalt, den root hat. Denn da
Hallo,
ich suche eine globale bashrc, die Ergänzungen zu den
lokalen ~/.bashrc's macht.
Im Wesentlichen sollen einige Umgebungsvariablen, aliase
und kleine Programme ausgeführt werden. Da auf der Maschine
bereits mehrere NFS-Homeverzeichnisse exisitieren, bringt
eine Ergänzung in die /etc/skel
Am Mittwoch 04 Oktober 2006 18:20 schrieb Christian Christmann:
ich suche eine globale bashrc, die Ergänzungen zu den
lokalen ~/.bashrc's macht.
Wo finde ich solch eine globale Konfigurationsdatei, die
die o.b. Ergänzungen durchführt?
Am Ende von
man bash
Gruß Chris
--
A: because
Heute (04.10.2006/20:03 Uhr) schrieb Christian Frommeyer,
Am Mittwoch 04 Oktober 2006 18:20 schrieb Christian Christmann:
ich suche eine globale bashrc, die Ergaenzungen zu den
lokalen ~/.bashrc's macht.
Wo finde ich solch eine globale Konfigurationsdatei, die
die o.b. Ergaenzungen
at Mittwoch, 4. Oktober 2006 18:20 wrote Christian Christmann:
Hallo,
ich suche eine globale bashrc, die Ergänzungen zu den
lokalen ~/.bashrc's macht.
Im Wesentlichen sollen einige Umgebungsvariablen, aliase
und kleine Programme ausgeführt werden. Da auf der Maschine
bereits mehrere NFS
| The personal initialization file, executed for login shells
|~/.bashrc
| The individual per-interactive-shell startup file
|~/.bash_logout
| The individual login shell cleanup file, executed when a login
shell exits
|~/.inputrc
bei allen
Usern die shell farbig haben. Kriegs nicht hin. Hab schon im home
des Users ne .bashrc und/oder .profile angelegt. Mit dem gleichen
Inhalt, den root hat. Denn da funktionierts.
,
| FILES
|/bin/bash
| The bash executable
|/etc/profile
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Jim Knuth wrote:
nein. Steht auch alles drin. ;) Ich würde nur gern auch bei allen
Usern die shell farbig haben. Kriegs nicht hin.
shell farbig? nur falls du die anzeige von 'ls' meinst, dann musst du
die environment variable LS_COLORS setzen.
Heute (05.10.2006/03:00 Uhr) schrieb Jan Kechel,
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Jim Knuth wrote:
nein. Steht auch alles drin. ;) Ich wuerde nur gern auch bei allen
Usern die shell farbig haben. Kriegs nicht hin.
shell farbig? nur falls du die anzeige von 'ls' meinst,
On Thu, Oct 05, 2006 at 02:53:02AM +0200, Jim Knuth wrote:
nein. Steht auch alles drin. ;) Ich würde nur gern auch bei allen
Usern die shell farbig haben. Kriegs nicht hin. Hab schon im home
des Users ne .bashrc und/oder .profile angelegt. Mit dem gleichen
Inhalt, den root hat. Denn da
Heute (05.10.2006/03:19 Uhr) schrieb Helmut Franke,
On Thu, Oct 05, 2006 at 02:53:02AM +0200, Jim Knuth wrote:
nein. Steht auch alles drin. ;) Ich würde nur gern auch bei allen
Usern die shell farbig haben. Kriegs nicht hin. Hab schon im home
des Users ne .bashrc und/oder .profile angelegt
1 - 100 of 423 matches
Mail list logo
