Je ne sais pas pourquoi je ne peux pas avoir la copie du mail dans la
réponse. On va donc copier à la main.
>Pour l’architecture globale, si je comprends bien c’est :
Un serveur de fichiers sous un *nix contenant à la fois les boot des
PC et leurs données
Des postes sans disque
zithro a écrit :
> On 24 Feb 2024 23:23, BERTRAND Joël wrote:
>> Un gros serveur sous NetBSD et toutes les stations sont diskless et
>> bootent sur le réseau. Les disques sont en NFS et les swaps en iSCSI.
>
> Peux-tu expliquer ce choix (NFS vs iSCSI) stp ?
Oui, je peux ;-)
> Si je
lent que par exemple
>> une liaison SATA à un disque local, même rotatif).
>>
>> NFS (à l'époque lointaine où je l'avais utilisé) ne crypte pas les
>> données. SSHFS semble les crypter.
>>
>> Autrefois (avant 2000) j'avais même utilisé des Sun4/110 dont le swap
On 24 Feb 2024 23:23, BERTRAND Joël wrote:
Un gros serveur sous NetBSD et toutes les stations sont diskless et
bootent sur le réseau. Les disques sont en NFS et les swaps en iSCSI.
Peux-tu expliquer ce choix (NFS vs iSCSI) stp ?
Si je dis pas de conneries, tu pourrais boot root (/) en
é) ne crypte pas les
> données. SSHFS semble les crypter.
>
> Autrefois (avant 2000) j'avais même utilisé des Sun4/110 dont le swap
> était une partition NFS distante.
>
> Librement
>
Bonsoir,
J'ai un réseau complet et hétérogène avec NIS+NFS.
Un gros s
Le 23 février 2024 Erwann Le Bras a écrit :
> Peut-être faire des essais avec SSHFS? le $HOME des utilisateurs serait monté
> sur chaque client au boot.
>
> Mais je ne sais pas si c'est plus efficace que NFS.
J'ai pas mal utilisé sshfs et ça reste assez performant même via
internet pour des
On 2/23/24 12:02, Erwann Le Bras wrote:
Bonjour
Peut-être faire des essais avec SSHFS? le $HOME des utilisateurs
serait monté sur chaque client au boot.
Mais je ne sais pas si c'est plus efficace que NFS.
J'aurais tendance à imaginer que c'est moins efficace que NFS, qui est
de toute
Bonjour
Peut-être faire des essais avec SSHFS? le $HOME des utilisateurs serait
monté sur chaque client au boot.
Mais je ne sais pas si c'est plus efficace que NFS.
Le 20/02/2024 à 12:26, Pierre Malard a écrit :
Ou ahh ! NIS, ça ne me rajeuni pas ça ;-)
Et pourquoi pas un LDAP pour
Ou ahh ! NIS, ça ne me rajeuni pas ça ;-)
Et pourquoi pas un LDAP pour l’authentification ?
Pour ce qui du montage direct du répertoire partagé sur la home dir ce n’est
pas judicieux car ça va ramer dur si on fait une utilisation gourmande en
entrée sortie.
Si je me souviens de ce qu’on avait
accède à internet, j'ai fais
iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
Est ce judicieux ?
J'ai essayé avec NIS avec debian 11, l'authentification à l'air de
bien fonctionner. Pour l'authentification, NIS est il bien adapté pour
ce genre de configuration ?
A l'époque déjà
iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
Est ce judicieux ?
J'ai essayé avec NIS avec debian 11, l'authentification à l'air de bien
fonctionner. Pour l'authentification, NIS est il bien adapté pour ce
genre de configuration ?
Par contre au niveau de l'export (NFS), cela rame un peu (je
On Wed, Jul 26, 2023 at 10:31:09AM +0200, Christoph Pleger wrote:
> I found out that, though this works for users listed in /etc/passwd, it
> does not for users who have a remote NIS account.
>
> That problem already occurred a longer time ago, but in the meanwhile,
> I had solve
is is to ensure that, if someone is logged in on the graphical
console at the time when a USB is inserted, this person becomes the
owner of the devive file belonging to the stick, /dev/sd[a-z].
I found out that, though this works for users listed in /etc/passwd, it
does not for users who have
Jean-Claude Marquès a écrit :
> OK, merci pour l'info. Donc il "suffit" de :
> systemctl stop nscd.service
> rm -f /var/cache/nscd/*
> systemctl start nscd.service
>
> 3 commandes qui remplaceraient le reboot.
Personnellement, c'est un systemctl stop nscd et systemctl disable
nscd. Le
cette distribution debian 11).
Pour le coup, NIS est un service qui peut même tomber en marche.
Bien évidemment, l'identification de la cause m'intéresse très fortement
(rien trouvé dans les logs...).
libnss. Ce truc est de plus en plus moisi. Il faut même virer le cache
nscd qui se
r chaque cohorte
> d'étudiants concernés (3 à ce jour sur cette distribution debian 11).
> Pour le coup, NIS est un service qui peut même tomber en marche.
>
> Bien évidemment, l'identification de la cause m'intéresse très fortement
> (rien trouvé dans les logs...).
libnss. Ce
jour sur cette distribution debian
11). Pour le coup, NIS est un service qui peut même tomber en
marche.
Bien évidemment, l'identification de la cause m'intéresse très
fortement (rien trouvé dans les logs...).
Bonne soirée
Jean-Claude
led, try:
# `info libc "Name Service Switch"' for information about this file.
passwd: compat nis
group: compat nis
shadow: compat nis
gshadow:files
hosts: files mdns4_minimal [NOTFOUND=return] dns
networks: files
protocols: db f
Bonjour à tous,
J'ai une station de travail qui est en Debian/Bookworm et qui
fonctionnait correctement jusqu'à une mise à jour récente (apportée par
unattented upgrade) et je n'arrive pas à trouver ce qui coince.
Configuration :
- serveur NIS/NFS tournant sous NetBSD 9.2
Bon...
Problème réglé, mais je ne sais pas comment. Je ne vois pas pourquoi
j'ai besoin de rebooter pour que la configuration soit prise en compte.
Et je n'ai pas trouvé comment débugguer efficacement un problème avec
pam. Je suis donc preneur de toute idée.
Bien cordialement,
JKB
BERTRAND Joël a écrit :
> Bon, c'est de pire en pire. Même le compte de mon épouse ne fonctionne
> plus sur hilbert. J'ai l'impression que le problème tourne autour des
> mots de passe NIS chiffrés en old côté NetBSD, donc en DES.
Un reboot plus tard après avoir changé
Bon, c'est de pire en pire. Même le compte de mon épouse ne fonctionne
plus sur hilbert. J'ai l'impression que le problème tourne autour des
mots de passe NIS chiffrés en old côté NetBSD, donc en DES.
mon poste de
travail avec mon login (mais un autre login sur le NIS fonctionne
parfaitement !). J'avoue ne plus savoir où chercher.
Configuration physique du réseau :
- serveur principal (legendre) fonctionnant nous NetBSD 9.1, exportant
des disques de boot pour les clients ainsi qu'un
Hi,
On 2020-01-09 18:23, Greg Wooledge wrote:
On Thu, Jan 09, 2020 at 05:56:53PM +0100, Christoph Pleger wrote:
Does anybody know what happened in newer kernels that makes
OWNER="$result"
fail for NIS accounts?
At a guess, it's bug #878625 again.
Does it start working again if y
On Thu, Jan 09, 2020 at 05:56:53PM +0100, Christoph Pleger wrote:
> Does anybody know what happened in newer kernels that makes OWNER="$result"
> fail for NIS accounts?
At a guess, it's bug #878625 again.
Does it start working again if you install nscd, or one of its
alternat
n Debian 10 as well
as in Ubuntu 18.04. Searching for the reason gave the result that the
success of the udev rule depends on the kernel version (it worked in
Ubuntu 18.04 with Kernel 4.15.0-50-generic, but does not work with
Kernel 4.15.0-74-generic) as well as on if the user has a local or a NIS
acco
n, Aug 20, 2018 at 12:51:24AM -0300, Joao Roscoe wrote:
> > Hmmm...
> >
> > If I create a NIS group (with a high ID), called serial_ports, dhould I
> > just, as root, chgrp /dev/ttyS0 so that it's group is serial_ports ?
>
> You could, and it may even work, but it would be
Hi.
On Mon, Aug 20, 2018 at 12:51:24AM -0300, Joao Roscoe wrote:
> Hmmm...
>
> If I create a NIS group (with a high ID), called serial_ports, dhould I
> just, as root, chgrp /dev/ttyS0 so that it's group is serial_ports ?
You could, and it may even work, but it would
Hmmm...
If I create a NIS group (with a high ID), called serial_ports, dhould I
just, as root, chgrp /dev/ttyS0 so that it's group is serial_ports ?
João
On Sun, Aug 19, 2018 at 12:47 PM Michael Stone wrote:
> On Fri, Aug 17, 2018 at 02:48:56PM -0300, Joao Roscoe wrote:
> >Right, th
On Fri, Aug 17, 2018 at 02:48:56PM -0300, Joao Roscoe wrote:
Right, that's best practice.
But, what if I need to include a user who is defined in NIS in lp or ttyS0
group? Would going into /etc/group in *every* machine be unavoidable?
That's one option. Another would be to create new
Joao Roscoe wrote:
> But, what if I need to include a user who is defined in NIS in lp or ttyS0
> group? Would going into /etc/group in *every* machine be unavoidable?
your print server will be the only one to consider for lp group for example
or just do something with ansible or
Right, that's best practice.
But, what if I need to include a user who is defined in NIS in lp or ttyS0
group? Would going into /etc/group in *every* machine be unavoidable?
João
On Fri, Aug 17, 2018 at 1:42 PM Greg Wooledge wrote:
> On Fri, Aug 17, 2018 at 01:27:32PM -0300, Joao Roscoe wr
database. Those are managed on a per-system basis
in the local /etc/group or analogous file(s).
Your network database should contain only your organization's local user
and group identities. That's why the default NIS Makefile has MINUID
and MINGID settings.
:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Fri, Aug 17, 2018 at 10:36:38AM -0300, Joao Roscoe wrote:
> > I have redhat and debian machines in the same network. Users and groups
> are
> > controlled via NIS
> >
> > I have realized that redhat and d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Aug 17, 2018 at 10:36:38AM -0300, Joao Roscoe wrote:
> I have redhat and debian machines in the same network. Users and groups are
> controlled via NIS
>
> I have realized that redhat and debian have different groups definitions
On Fri, Aug 17, 2018 at 10:36:38AM -0300, Joao Roscoe wrote:
What would be the best way to manage this (other than managing groups on
machines themselves, individually)? Different NIS domains for different
distros? Is there any tutorial on managing multiple domains on the same NIS
server, out
I have redhat and debian machines in the same network. Users and groups are
controlled via NIS
I have realized that redhat and debian have different groups definitions
for system resources access control. For instance, redhat machines have
group lp with GID 4, while debian states that lp group
On Wed, Apr 1, 2015 at 6:11 PM, Bob Proulx b...@proulx.com wrote:
Jessie implies that you are using default that I cannot name for fear
of starting a flamewar. But it hasn't been heavily tested in
conjuction with NIS/yp.
Since I'm more at a user knowledge level, I am neutral about default
Joao Roscoe wrote:
I'm preparing a new jessie box (test system, preparing for deploying as
soon as it gets into stable).
Jessie implies that you are using default that I cannot name for fear
of starting a flamewar. But it hasn't been heavily tested in
conjuction with NIS/yp.
Installed
.
Installed ntp, ntpdate, tcsh and autofs. There were a few missing NFS
mounts, since mount info should come from NIS, but everything still worked
nicely.
So, I installed NIS, and except for a small delay everything was still ok.
ypwhich returned one of NIS servers (it took about two seconds
-- change this value to 12 to keep log files for 12
months
}
...
But I have another doubt. This log only the login at this machine. But
how to log the autentication of other machines at the NIS server?
How keep the login history of NIS clients at only one file at NIS
server?
Is there any way
On Thu, Jul 4, 2013 at 3:37 PM, Markos mar...@c2o.pro.br wrote:
But I have another doubt. This log only the login at this machine. But
how to log the autentication of other machines at the NIS server?
How keep the login history of NIS clients at only one file at NIS
server?
Is there any
On Mon, Jul 1, 2013 at 4:02 PM, Markos mar...@c2o.pro.br wrote:
The command last -f /var/log/wtmp.1 shows only the month before.
Is there any way to get this information?
Im afraid that info is lost. Unless you have more of those
/var/log/wtmp* logs around...
The retention period of that log
Hello,
We have a NIS server in a small network (6 PCs), and I need to get
informations about the login history of all users on NIS server during
all months.
The command last (on server) shows only the login of current month, on
the server.
The command last -f /var/log/wtmp.1 shows only
Bom Alcione,
Obrigado pela atenção.
Mas resolvi o problema seguindo a resposta que foi enviada pela lista Debian
User:
http://lists.debian.org/debian-user/2013/02/msg00466.html
Tive apenas que editar o arquivo /etc/nsswitch.conf alterando a posição do
nis nas linhas:
De:
passwd: nis
Tive apenas que editar o arquivo /etc/nsswitch.conf alterando a posição
do nis nas linhas:
De:
passwd: nis compat
group: nis compat
shadow:nis compat
Para:
passwd: files nis
group: files nis
shadow: files nis
Ao colocar o nis depois
Dear Bob,
Thank you very much for your attention and details in your explanation.
As a newbie with NIS (and NFS) I'll read, and study, your message
carefully.
I'll copy your explanation as a tutorial. :^)
Greetings,
Markos
Em Ter, 2013-02-12 às 15:17 -0700, Bob Proulx escreveu:
Markos wrote
a NIS Service on a machine (server), to centralize
logging of new users.
Reasonable.
But now, I realized that if I shut down the server I can no longer login
as root, or student1, on the client machines.
That tells me that one of two things are the problem. Either 1) your
/etc
Markos wrote:
Bob Proulx escreveu:
passwd: files nis
group: files nis
shadow: files nis
hosts: files dns
That was the problem!
Yay!
I simply did what you suggested and now I can log in clients with or
without the server. :^)
Good
192.168.0.2:36811
to procedure ypproc_match (pimentel.edu,shadow.byname;-1)
Shose are nis/yp errors. For the shadow map. Is nis/yp working okay
for you? You said that it was.
Feb 10 14:54:39 servidor mountd[1052]: authenticated mount request from
192.168.0.2:920 for /home (/home)
I think
Markos wrote:
I have a small network with 6 machines running Debian Squeeze.
When installing the machines I created only the root account and a user
student1 in all machines on the network.
Sure.
Then I installed a NIS Service on a machine (server), to centralize
logging of new users
Markos wrote:
For the first time, I configured a NIS service on a small network.
Now I observed that if the NIS server is turned off, the NIS client can
not load the login screen. So I'm not able to log even as local user in
client nis machine.
Note that if the client is truly a thin client
Pessoal,
Configurei, pela primeira vez, o serviço NIS em uma rede com 6 máquinas.
Agora observo que se o servidor NIS está desligado, não consigo nem mesmo
entrar na tela de login das máquinas clientes NIS.
Existe alguma forma de inicializar as máquinas cliente NIS e me logar como um
usuário
Pelo que me consta vc pode logar como root localmente, essa conta não é
importada pelo NIS.
Logando como root vc consegue resolver o problema da não inicialização
do cliente NIS, mas tem que fazer isso no terminal (Ctrl+Alt+F1..F6)
On 11-02-2013 17:40, Instruisto Jose wrote:
Pessoal
Dear,
For the first time, I configured a NIS service on a small network.
Now I observed that if the NIS server is turned off, the NIS client can
not load the login screen. So I'm not able to log even as local user in
client nis machine.
What can I do to login as local user in a client nis
Dear Bob,
Em Sáb, 2013-02-09 às 12:52 -0700, Bob Proulx escreveu:
Markos wrote:
I just checked the configuration file /etc/fstab on the client machine
and the server IP address is correct. 192.168.0.1
When writing the message I copied and pasted the IP address of the site
that I used
Dear,
I have a small network with 6 machines running Debian Squeeze.
When installing the machines I created only the root account and a user
student1 in all machines on the network.
Then I installed a NIS Service on a machine (server), to centralize
logging of new users.
But now, I realized
192.168.10.101 with 192.168.0.1
In /etc/nsswitch.conf file:
passwd: files nis
group: files nis
shadow: files nis
Ok.
But what about the files /etc/passwd ... /etc/gshadow. Should remove
the + at the end of these files?
If you modify the /etc
Markos wrote:
I just checked the configuration file /etc/fstab on the client machine
and the server IP address is correct. 192.168.0.1
When writing the message I copied and pasted the IP address of the site
that I used as a reference and I forgot to check.
Sorry for the mistake.
No
Mark Neyhart wrote:
Markos wrote:
mount 192.168.0.1:/home /home
The ip address in the above mount command agrees with the address in
/etc/network/interfaces.
The file /etc/network/interfaces of the server is:
auto eth0
iface eth0 inet static
address 192.168.0.1
But the ip address you
Dear Bob,
Em Dom, 2013-02-03 às 12:48 -0700, Bob Proulx escreveu:
Markos wrote:
I'm trying to configure the services NIS+NFS in a small network (7 PCs),
all running Squeeze.
Okay. Sounds good.
The NIS service seems to be working
Good.
but NFS don't mounts the /home partition
with
the address in etc/network/interfaces.
I copied these options from a site. I was thinking to simplify and
replace with just defaults
192.168.10.101:/home /home nfs defaults 0 0
You should replace 192.168.10.101 with 192.168.0.1
In /etc/nsswitch.conf file:
passwd: files nis
group
Markos wrote:
I'm trying to configure the services NIS+NFS in a small network (7 PCs),
all running Squeeze.
Okay. Sounds good.
The NIS service seems to be working
Good.
but NFS don't mounts the /home partition on the clients during boot.
Focus only on the NFS part of the debugging. Do
Oi Jonathan,
Encontrei sua mensagem e também estou tendo problemas para configurar o NIS+NFS
O NIS está funcionando e consigo montar na mão o /home nos clientes.
Editei o /etc/fstab mas não monta no boot.
Você sugere algum tutorial para eu tentar rastrear o problema?
Obrigado,
Markos
--- Em
Pessoal,
Estou com dificuldade para finalizar a configuração dos serviços NIS+NFS em uma
rede com 7 PCs rodando Squeeze.
Parece que o NIS está funcionando.
Mas o NFS não monta o /home nos clientes durante o boot.
Consigo montar pelo terminal com o comando
mount 192.168.0.1:/home /home
Dear,
Please, I'm confused!
I'm trying to configure the services NIS+NFS in a small network (7 PCs),
all running Squeeze.
The NIS service seems to be working but NFS don't mounts the /home
partition on the clients during boot.
But I can manually mount the /home partition on the clients
Olá Colegas,
Estou fazendo testes com um servidor nis e quero que os clientes tenham
suas pastas /home e outras pastas montadas remotamente via nfs e
automaticamente via autofs. Já configurei o servidor nis, os clientes
autenticam normalmente no servidor. O problema é quando tento colocar o
Boa tarde ! estou com problemas para ativar o nis no squid, pelo que vi o
nis ja esta ok neste servidor mas a interação entre squid e o nis nao
autentica, alguém ja faz esse servidor ?
segue meu squid.conf :
http_port 3128 transparent
visible_hostname .x.xx
cache_dir ufs /var/spool
estou com problemas com o nis e o nfs, meu tenho alguns grupos cadastrados
no servidor nis nfs um deles é alunos e o outro prof, na maquina no cliente
nis nfs o grupo alunos conecta mas o prof nao e isso tanto no nos quanto no
nfs alguem sabe o que pode ser ?
Sim. Deve ser problema de
Em Sexta-feira 25 Fevereiro 2011, às 17:53:15, Anderson Bertling escreveu:
Boa tarde
estou com problemas com o nis e o nfs, meu tenho alguns grupos cadastrados
no servidor nis nfs um deles é alunos e o outro prof, na maquina no cliente
nis nfs o grupo alunos conecta mas o prof nao e isso
Boa tarde
estou com problemas com o nis e o nfs, meu tenho alguns grupos cadastrados
no servidor nis nfs um deles é alunos e o outro prof, na maquina no cliente
nis nfs o grupo alunos conecta mas o prof nao e isso tanto no nos quanto no
nfs alguem sabe o que pode ser ?
desde ja fico grato
Em 25 de fevereiro de 2011 17:30, Anderson Bertling
andersonbertl...@gmail.com escreveu:
Boa tarde
estou com problemas com o nis e o nfs, meu tenho alguns grupos cadastrados
no servidor nis nfs um deles é alunos e o outro prof, na maquina no cliente
nis nfs o grupo alunos conecta mas o prof
Boa tarde
estou com problemas com o nis e o nfs, meu tenho alguns grupos cadastrados
no servidor nis nfs um deles é alunos e o outro prof, na maquina no cliente
nis nfs o grupo alunos conecta mas o prof nao e isso tanto no nos quanto no
nfs alguem sabe o que pode ser ?
desde ja fico grato
Boa noite
Estou com problemas para autenticar alguns usuários, no cliente nis nfs, a
grande maioria esta conectando normalmente, mas alguns não tem acesso nem
nas pastas, alguem já enfrentou esse problema ? sabe com solucionar ?
desde já fico grato pela ajuda
--
Att
Anderson Bertling
Como você fez a configuração dos clientes?? está usando LDAP também??
Em 25 de fevereiro de 2011 20:59, Anderson Bertling
andersonbertl...@gmail.com escreveu:
Boa noite
Estou com problemas para autenticar alguns usuários, no cliente nis nfs, a
grande maioria esta conectando normalmente
Bom dia,
Possuo um servidor com nis e nfs, tenho dois usuários nesse servidor, um
deles eu acesso via ssh e vnc normalmente mas o segundo não acessa, eles
estão em grupos diferentes, um deles chega no servidor mas o outro não
segue log
servidor
3726:Feb 14 07:09:16 server rpc.yppasswdd[1009
com nis e nfs, tenho dois usuários nesse servidor, um
deles eu acesso via ssh e vnc normalmente mas o segundo não acessa, eles
estão em grupos diferentes, um deles chega no servidor mas o outro não
segue log
servidor
3726:Feb 14 07:09:16 server rpc.yppasswdd[1009]: update cacau (uid=20219
verefica se o teu usuário tem permissão para logar no ssh, verefica o teu
/etc/ssh/sshd.conf
--
att
Marcos Carraro
Linux user #511627
2011/2/14 Anderson Bertling andersonbertl...@gmail.com
Bom dia,
Possuo um servidor com nis e nfs, tenho dois usuários nesse servidor, um
deles eu acesso
na porta do ssh e depois
verefica se o teu usuário tem permissão para logar no ssh, verefica o teu
/etc/ssh/sshd.conf
--
att
Marcos Carraro
Linux user #511627
2011/2/14 Anderson Bertling andersonbertl...@gmail.com
Bom dia,
Possuo um servidor com nis e nfs, tenho dois usuários nesse
Marcos, entao meu servidor nis nfs nao tem porta liberada para a internet só
para a rede interna, ja no meu servidor vnc e ssh que que da acesso a rede
interna tem,
internet
|
server
servidor nis nfs nao tem porta liberada para a internet
só para a rede interna, ja no meu servidor vnc e ssh que que da acesso a
rede interna tem,
internet
|
server
lenny) that mount NFS from a Solaris 10 (x86)
box
through autofs (5.0.4-3.2 amd64). They all do their authentication
through
NIS (which is also being served by the same box). Another Solaris 10
(sparc)
machine is the DNS server for our domain. Unfortunately, the NIS domain
and
the DNS domain
On Sat, Jan 8, 2011 at 11:03 PM, Joseph Lenox lordofhyph...@gmail.com wrote:
Anywhere this info could be added for the other people who will undoubtedly
run into this when Squeeze goes stable?
I assume that you mean in the release notes.
I've emailed debian-...@lists.debian.org because I
Hello,
I'm running a series of Debian 6.0 Squeeze clients on my network (in
the process of upgrading from lenny) that mount NFS from a Solaris 10
(x86) box through autofs (5.0.4-3.2 amd64). They all do their
authentication through NIS (which is also being served by the same box).
Another
through
NIS (which is also being served by the same box). Another Solaris 10 (sparc)
machine is the DNS server for our domain. Unfortunately, the NIS domain and
the DNS domain are not the same.
Every file is being listed as belonging to UID/GID 4294967294, which I see
from Google appears
). They all do their authentication through
NIS (which is also being served by the same box). Another Solaris 10 (sparc)
machine is the DNS server for our domain. Unfortunately, the NIS domain and
the DNS domain are not the same.
snip
Squeeze must be defaulting to nfsv4.
Make sure
). They all do their authentication through
NIS (which is also being served by the same box). Another Solaris 10 (sparc)
machine is the DNS server for our domain. Unfortunately, the NIS domain and
the DNS domain are not the same.
Every file is being listed as belonging to UID/GID 4294967294, which I
We just had some craziness with smbd going into a
tight loop while attempting to start Samba.
It turned out to be because smbd thought a printing
service was running, but it couldn't make sense of
attempts to communicate with that printing service.
The reason for this appears to be that
Bonjour,
désolé pour ce HS. ce n'a pas de rapport avec debian. mais bcp d'entre
vous administrent des parcs de machines et donc connaissent NIS.
Mon labo a acheté un cluster. dessus il y a oscar et cenOS. Je me
retrouve admin de ce cluster. Je commence donc à regarder comment on
ajoute un
giggzounet wrote:
Bonjour,
Bonjour
désolé pour ce HS. ce n'a pas de rapport avec debian. mais bcp d'entre
vous administrent des parcs de machines et donc connaissent NIS.
...
Le support me dit vous devez faire un make -C /var/yp pour mettre à
jour la base NIS...c'est vrai ça marche
Le vendredi 03 septembre 2010 à 11:47 +0200, giggzounet a écrit :
Bonjour,
désolé pour ce HS. ce n'a pas de rapport avec debian. mais bcp d'entre
vous administrent des parcs de machines et donc connaissent NIS.
Mon labo a acheté un cluster. dessus il y a oscar et cenOS. Je me
retrouve
Re,
On Fri, Sep 03, 2010 at 11:47:31AM +0200, giggzounet wrote:
désolé pour ce HS. ce n'a pas de rapport avec debian. mais bcp
d'entre vous administrent des parcs de machines et donc connaissent
NIS.
Connaît-on jamais NIS ? :-)
maintenant je me dis que mon utilisateur pouet veut changer
Le 03/09/2010 14:11, Julien a écrit :
Le vendredi 03 septembre 2010 à 11:47 +0200, giggzounet a écrit :
Bonjour,
désolé pour ce HS. ce n'a pas de rapport avec debian. mais bcp d'entre
vous administrent des parcs de machines et donc connaissent NIS.
Mon labo a acheté un cluster. dessus il y
Le 03/09/2010 14:13, JF Straeten a écrit :
Re,
On Fri, Sep 03, 2010 at 11:47:31AM +0200, giggzounet wrote:
désolé pour ce HS. ce n'a pas de rapport avec debian. mais bcp
d'entre vous administrent des parcs de machines et donc connaissent
NIS.
Connaît-on jamais NIS
On Fri, Sep 03, 2010 at 11:47:31AM CEST, giggzounet giggzou...@gmail.com said:
Bonjour,
désolé pour ce HS. ce n'a pas de rapport avec debian. mais bcp d'entre
vous administrent des parcs de machines et donc connaissent NIS.
Mon labo a acheté un cluster. dessus il y a oscar et cenOS. Je me
.)
intéressant! il est où ce script adduser.local ???
Tu le crées dans /usr/local/sbin ;-)
Ici, y avait bêtement ça dedans :
oda:~# cat /usr/local/sbin/adduser.local
#!/bin/bash
#
#
echo -e \nI: Execution de $0 :
echo -e I: (Arguments passes : $@)\n
echo -e I: Rafraichissement des cartes NIS :\n
make -C
echo -e I: Rafraichissement des cartes NIS :\n
make -C /var/yp
Mais on y met ce qu'on veut. Il est appelé avec les arguments
suivants :
nom du compte id du compte id du groupe rep home du user
C'est ce que montre la ligne :
echo -e I: (Arguments passes : $@)\n
Exemple
hi,
nscd was the problem. He cached the local passwd ...
cu denny
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
hi,
I have a real strange problem. We have a NIS system with Debian Lenny
clients and LDAP as second system, but LDAP is not the problem here. I
want, that the user have to use the passwd command (cause of cracklib
support via pam). Here some facts on one client:
/etc/nsswitch.conf
passwd: file
On 3/25/2010 6:18 PM, Michael Biebl wrote:
Am 25.03.2010 23:38, schrieb Joseph Lenox:
I tried the pam_group approach, and id says the user is in the plugdev
group, but I'm still getting a permissions error from DBus. Adding the exact
user to the plugdev group on the local machine worked as
1 - 100 of 1274 matches
Mail list logo
