On 11/20/19 11:03 AM, Patrick Dupre wrote:
When I run nextcloud, I get:
"the password you use to log in to your computer no longer matches that of your
login keyring"
It was not too much an issue when I was able to cancel the request, but
for 2 days now, I am even not able kill the request.
I h
Hello,
When I run nextcloud, I get:
"the password you use to log in to your computer no longer matches that of your
login keyring"
It was not too much an issue when I was able to cancel the request, but
for 2 days now, I am even not able kill the request.
I have to kill the nextcloud application
On 12/04/2015 10:59 AM, Patrick O'Callaghan wrote:
On Fri, 2015-12-04 at 09:30 -0800, Rick Stevens wrote:
To make sure the lockfile gets deleted, you must create a function
that deletes the lockfile, and specify that function in a trap call
to trap SIGINT, SIGTERM, etc. That way it cleans up aft
On Fri, 2015-12-04 at 09:30 -0800, Rick Stevens wrote:
> To make sure the lockfile gets deleted, you must create a function
> that deletes the lockfile, and specify that function in a trap call
> to trap SIGINT, SIGTERM, etc. That way it cleans up after itself if
> you abort it.
For Shell scripts
On 12/04/2015 05:29 AM, Frédéric Bron wrote:
in fact, I just had to delete the .lock file. I do not understand why
it was there.
Many commands create a lock file so that you can't run multiple copies
of the command simultaneously. If you had two users running that
command, both writing to the s
in fact, I just had to delete the .lock file. I do not understand why
it was there.
Thanks,
Frédéric
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraprojec
On 12/03/2015 10:37 AM, Frédéric Bron wrote:
On fedora 23 the following command does not work anymore:
$ passwd -u username
Unlocking password for user username.
passwd: Libuser error at line: 171 - Invalid contents of lock
`/etc/shadow.lock'.
passwd: Error (password not set?)
What can I
On fedora 23 the following command does not work anymore:
$ passwd -u username
Unlocking password for user username.
passwd: Libuser error at line: 171 - Invalid contents of lock
`/etc/shadow.lock'.
passwd: Error (password not set?)
What can I do to unlock this user?
Frédéric
--
users ma
rovide more details of your setup
> for help...
>
> The contents of /etc/nsswitch.conf /etc/samba/smb.conf
> and /etc/pam.d/system-auth ought to put people on the right track.
Thanks James, I have try your suggestion and now "getent passwd" (and
group) work great!
Many Thanks
On 29 Sep 2014 13:11, "Dario Lesca" wrote:
>
> Il giorno lun, 29/09/2014 alle 12.39 +0100, James Hogarth ha scritto:
> > Enumeration is disabled by default for performance reasons.
> >
> > If you really want that as enumerate = true to the domain section of
> > your sssd.conf
>
> Thanks for reply,
Il giorno lun, 29/09/2014 alle 12.39 +0100, James Hogarth ha scritto:
> Enumeration is disabled by default for performance reasons.
>
> If you really want that as enumerate = true to the domain section of
> your sssd.conf
Thanks for reply, James.
But I known nothing about SSSD, and my sssd servi
ser's
> domain.
>
> But the "getent passwd" (and also group) command non work like samba 3
> server.
>
> If I run "getent passwd mydomain\\ospite" the user is show:
> >
MYDOMAIN\ospite:*:4294967295:4294967295::/home/MYDOMAIN/ospite:/bin/false
>
> But
Hi, I have configure samba 4 on my Fedora 20 with "security = domain"
and I have join this workstation to my linux PDC, a samba 3 domain
All work fine and on fedora 20, via samba, I can autenticate the user's
domain.
But the "getent passwd" (and also group) command non
On 01/21/2014 12:29 PM, Chaudhari, Rohit K. wrote:
> Hello,
>
> I want to be able to use the Unix "passwd" command to reset a LDAP
> user's password from the command line. However, I keep getting an
> authentication token manipulation error whenever I try to r
On 07/23/2013 01:54 PM, Augustin Wolf wrote:
I agree. The only acceptable solution would be one way hash, but this
wouldn't be much help, unless OpenLdap supports it.
If the system stored a one-way hash of a "password," and that hash were
usable as an authentication token, then the one-way has
On 23 July 2013 16:39, Stephen Gallagher wrote:
>> That means that either you need the admin's DN and plain-text
>> password in a file (like the older PAM LDAP does) or you need the
>> user to enter their own password (like both sssd and PAM LDAP do).
So, unless using
ng up the bind account for SSSD itself to look up
users, groups, etc. It doesn't perform ANY write operations back to
LDAP at all. The only time SSSD ever modifies the LDAP server is
during a password change operation, and then it's done only with the
credentials of the user changing thei
ons via LDAP server.
It's used for searches, generally when your directory doesn't allow
anonymous searches.
It does work when I'm changing password as a
user using "passwd", right?
"It" consists of connecting to the LDAP server with the password given
by
far as I understand this is the user that is performing all the
actions via LDAP server. It does work when I'm changing password as a
user using "passwd", right? So it might as well change all users
passwords.
How using command "passwd" to change user password differ
t; to userPassword by self write by * auth it is true, but users tend
> to forgot their passwords, and You don't have to give them write
> permission to yserPassword attribute. Now there need to be some
> other way for administrator to reset users passwords. Command
> "passwd&quo
ission to yserPassword attribute. Now
there need to be some other way for administrator to reset users
passwords. Command "passwd" is most common, and doesn't require admin
to remember user DN.
> What ldap server are you using? You may consider contacting thier mailing
> lists
On 20/07/2013, at 9:58 AM, Augustin Wolf wrote:
> Hi list,
> I have a user management in LDAP, as it works fine for user (can
> login, do `passwd` to change his password, etc.)
> But, root cannot change users password otherwise as via ldapmodify. Is
> it normal behavior, or
Hi list,
I have a user management in LDAP, as it works fine for user (can
login, do `passwd` to change his password, etc.)
But, root cannot change users password otherwise as via ldapmodify. Is
it normal behavior, or do I have some configuration errors?
For now, LDAP ACL was "turned off&quo
From: Patrick O'Callaghan
To: Aaron Konstam
Cc: users@lists.fedoraproject.org
Sent: Fri, April 19, 2013 5:08:22 PM
Subject: Re: [Evolution] Problem with evolution passwd
On Fri, 2013-04-19 at 13:27 -0700, Aaron Konstam
From: Patrick O'Callaghan
To: evolution-l...@gnome.org
Sent: Fri, April 19, 2013 3:19:59 PM
Subject: Re: [Evolution] Problem with evolution passwd
On Fri, 2013-04-19 at 08:02 -0700, Aaron Konstam wrote:
> Suddenly this morning when I open evoluti
istration tools. So they are run-time created files, and are
>> not owned by any rpm package, and so are not part of any update to packages.
>>
>> $ rpm -qf /etc/passwd-
>> file /etc/passwd- is not owned by any package
>> $ rpm -qf /etc/group-
>> file /etc/group- is n
ned by any rpm package, and so are not part of any update to packages.
>
> $ rpm -qf /etc/passwd-
> file /etc/passwd- is not owned by any package
> $ rpm -qf /etc/group-
> file /etc/group- is not owned by any package
> $ rpm -qf /etc/shadow-
> file /etc/shadow- is not owned by a
On 02/08/2013 02:37 PM, Reindl Harald wrote:
> are these fails are no longer needed artefacts in F18 or
> where they always only created by system-config-users
> and so untouched by yum-updates?
>
> /etc/passwd-
> /etc/group-
> /etc/gshadow-
> /etc/shadow-
The passwd, gr
are these fails are no longer needed artefacts in F18 or
where they always only created by system-config-users
and so untouched by yum-updates?
/etc/passwd-
/etc/group-
/etc/gshadow-
/etc/shadow-
___
[root@rh:/etc]$ diff passwd passwd-
67d66
< polkitd:x:110:
Joachim Backes wrote:
Question: are these files only created for backup purposes, or is there
another reason for this?
$ man 5 shadow
...
/etc/shadow-
Backup file for /etc/shadow.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription option
he was speaking about "/etc/shadow-" and NOT "/etc/shadow"
and yes i am sure they are backups
Whoops, right you are!
- Mike
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http
Am 12.01.2012 12:52, schrieb Dr. Michael J. Chudobiak:
> On 01/12/2012 12:05 AM, Joachim Backes wrote:
>> Hi all,
>>
>> adding a new user with "useradd ..." will create two additional files
>> never removed:
>>
>> /etc/passwd- and /etc/shadow-
>
> adding a new user with "useradd ..." will create two additional files
> never removed:
>
> /etc/passwd- and /etc/shadow-
>
> Question: are these files only created for backup purposes, or is there
> another reason for this?
>
>
> Looking at a sys
On 01/12/2012 12:05 AM, Joachim Backes wrote:
Hi all,
adding a new user with "useradd ..." will create two additional files
never removed:
/etc/passwd- and /etc/shadow-
Question: are these files only created for backup purposes, or is there
another reason for this?
/etc/passw
Hi all,
adding a new user with "useradd ..." will create two additional files
never removed:
/etc/passwd- and /etc/shadow-
Question: are these files only created for backup purposes, or is there
another reason for this?
Kind regards
--
Joachim Backes
http://www.rhrk.uni-kl.
Synopsis: getent passwd {user} works on secondary and primary server,
getent passwd fails (does not return all users) on secondary, works
correctly on primary.
getent passwd {username} - works when pointing to both primary and
secondary.
getent passwd | grep {username} only works if pointed
ke
backups. Then, it opened /etc/passwd and /etc/shadow, creating new
versions but was unable to write to either file because the / partition
was full. (Remember, /etc must be on the / partition because it has to
be available before the other partitions are mounted because that's
where fstab l
me question had gone unanswered by the community.
I'm only guessing, you understand, but it's quite possible that the two
problems are related. Some program tried to modify the password file
(and shadow, of course) and as a first step, renamed them to make
backups. Then, it opened /e
ticed that the "/" partition was full
so I cleared unwanted files and another thing is I noticed that both the
/etc/passwd and /etc/shadow file was blank. Good thing there was a copy
on /etc called "passwd--" and "shadow--", I cp'ed those files and
rebooted and
, 2011 1:44 PM
To: General discussion list for the 389 Directory server project.
Cc: Beamon, John
Subject: Re: [389-users] (Insufficient 'write' privileges to the
'userPassword') when executing passwd change
On 02/18/2011 11:18 AM, Beamon, John wrote:
This is a new instal
te failed: Server is unwilling to perform
user is not allowed to change password
passwd: Permission denied
Que.2 Now how to sort out this one... ?
Que.3 And one more question is, where i will find all these logs...if
someone file these command at client as well as server machine(i.e.
ldapsearc
On 04/25/2010 02:21 AM, Roger wrote:
> I always set up /etc/sudoers to allow user many but not all root privileges
> Using root is dangerous.
>
> su
> enter root password
> vim /etc/sudoers
You should really use visudo to edit the file. It takes care of
things like locking the file, (not really n
ng up using 'rescue installed system' going to shell:
>> shell-4.0#
>> run passwd, and change password, then reboot
>> but cannot login as root have no trouble loggin as user.
>>
> Are you trying to login as root via the graphical login? If so,
> that
oting up using 'rescue installed system' going to shell:
>> shell-4.0#
>> run passwd, and change password, then reboot
>> but cannot login as root have no trouble loggin as user.
>>
>> auy sugestions
>> Lewis Jessup (have been using linus for awhile
ve tried booting up using 'rescue installed system' going to shell:
> > shell-4.0#
> > run passwd, and change password, then reboot
> > but cannot login as root have no trouble loggin as user.
> >
> > auy sugestions
> > Lewis Jessup (have been using lin
在 2010-04-24六的 05:55 -0700，Lewis Jessup写道：
> I just installed fedora core 12 and install excepts a password for
> root but when trying to login it gives an
> 'authentication failure"
>
> Have tried booting up using 'rescue installed system' going to shell:
>
Hi Lewis,
Lewis Jessup wrote:
> I just installed fedora core 12 and install excepts a password for
> root but when trying to login it gives an 'authentication failure"
>
> Have tried booting up using 'rescue installed system' going to shell:
> shell-4.0#
>
m' going to shell:
> shell-4.0#
> run passwd, and change password, then reboot
> but cannot login as root have no trouble loggin as user.
>
> auy sugestions
I'm not certain you can change it (and have it stick) using rescue
mode. I'd boot up in single-user mode and change
I just installed fedora core 12 and install excepts a password for root but
when trying to login it gives an
'authentication failure"
Have tried booting up using 'rescue installed system' going to shell:
shell-4.0#
run passwd, and change password, then reboot
but cannot l
For some reason my client server is not pulling group information from
the ldap server. "getent passwd" pulls over all the relevant accounts
from the ldap database. "getent group", however, is missing my
personal group. I don't have any entries for my user in /etc/pa
50 matches
Mail list logo
