Re: [SOLVED] Dell E7470 Install: No bootable device found

2016-11-03 Thread Michael B Allen 
On Thu, Nov 3, 2016 at 7:47 PM, stan  wrote:
> On Thu, 3 Nov 2016 15:31:48 -0400
> Michael B Allen  wrote:
>
>> I just tried to install F24 and everything went smoothly but after
>> reboot I just get "No bootable devices found".
>
> I think if this is a recent version of windows that you will need to
> use UEFI to boot, though I'm not very familiar with it.

I have resolved the issue. The machine came with Windows 7 which uses
BIOS (aka Legacy Mode) and not UEFI so I don't even have a UEFI boot
partition. But to boot Fedora Live from USB, I had to switch from
Legacy Mode to UEFI in system setup (F12 at the Dell logo when
booting). Changing this *back* to Legacy Mode after the installation
now loads the grub screen and I can get into the hard disk
installation.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: starting remote firefox via SSH

2016-11-03 Thread Tim 
Allegedly, on or about 19 October 2016, Rick Stevens sent:
> I've done this before. Essentially:
> 
> 1. Ensure "X11Forwarding yes" is set in the REMOTE system's
> /etc/ssh/sshd_config file and make sure sshd has been restarted
> to read it.
> 
> 2. Run "xhost +" as root on the LOCAL system to permit everyone
> to make connections to the LOCAL system's X server.
> 
> 2. "su - unprivileged-user-name" on the LOCAL machine.
> 
> 3. "ssh -X user@REMOTEHOST" to log into the REMOTE machine.
> 
> 4. Verify you have a DISPLAY variable set by doing
> "echo $DISPLAY" on the REMOTE machine. You should get a value
> like "localhost:10.0", indicating you have X forwarded.
> 
> 5. Run "firefox" on the REMOTE machine. The display should pop
> up on your local machine.
> 
> This has worked for me for a long time. 

It's an issue with Firefox, chiefly.  It tries to be clever, and use an
already (locally) running Firefox instance if there is one.

Sure, if there isn't any Firefox running at the time, then issuing the
command will run Firefox on the remote computer displaying on the local
machine.  But, if if Firefox was already running locally, then any
attempt to run Firefox, will (usually) re-use the local one.

-- 
[tim@localhost ~]$ uname -rsvp
Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64

Boilerplate:  All mail to my mailbox is automatically deleted, there is
no point trying to privately email me, I only get to see the messages
posted to the mailing list.

Lucky for you I typed this, you'd never be able to read my handwriting.


___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Emacs24 at f24/f25

2016-11-03 Thread stan 
On Thu, 03 Nov 2016 08:48:37 +0100
Saša Janiška  wrote:


> Org-9.0 is just released, it behaves a little better with 25.1 and
> maybe it’s only some sort of Debian-ism, so on Fedora it might be
> even better since, afaik, it’s closer to the upstream…

This sounds promising.  It's likely that future development will be
geared to the latest version of emacs, so support should only get
better.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Dell E7470 Install: No bootable device found

2016-11-03 Thread stan 
On Thu, 3 Nov 2016 15:31:48 -0400
Michael B Allen  wrote:

> I just tried to install F24 and everything went smoothly but after
> reboot I just get "No bootable devices found".
> 
> I've been using Linux as my primary machine since kernel 2.0.35 and my
> instinct tells me this looks like the bootloader wasn't installed
> correctly.
> 
> Is this a known problem?

Not usually.

> 
> When I "reclaimed" space my drive looked something like the following:
> 
> sda1 Dell Utiility
> sda2 Windows Recovery
> sda3 Windows OS
> 
> So I deleted Windows and reclaimed but I want to leave the Dell
> utility and Windows recovery partition.

This all looks fine.  How large is sda3, and how far from the start of
the disk.  If using bios boot, the boot partition has restrictions on
its location.

> 
> So how do I install the bootloader in F24 so that it boots sda3?
> 
> Is grub still being used?

It's now grub2.

https://fedoraproject.org/wiki/GRUB_2

I think if this is a recent version of windows that you will need to
use UEFI to boot, though I'm not very familiar with it.
https://docs.fedoraproject.org/en-US/Fedora/22/html/Multiboot_Guide/BOOT-BIOS_or_UEFI.html
https://fedoraproject.org/wiki/Unified_Extensible_Firmware_Interface
https://docs.fedoraproject.org/en-US/Fedora/18/html-single/UEFI_Secure_Boot_Guide/

If you are using a bios boot, you need to install the grub2 bootloader
on the disk for the bios to find.  I think the command is

grub2-install /dev/sda

in your case.  You would have to boot a rescue image somehow to do
that.  But, the fedora installer, anaconda, should have taken care of
all of this. How did you install?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Dell E7470 Install: No bootable device found

2016-11-03 Thread Michael B Allen 
I just tried to install F24 and everything went smoothly but after
reboot I just get "No bootable devices found".

I've been using Linux as my primary machine since kernel 2.0.35 and my
instinct tells me this looks like the bootloader wasn't installed
correctly.

Is this a known problem?

When I "reclaimed" space my drive looked something like the following:

sda1 Dell Utiility
sda2 Windows Recovery
sda3 Windows OS

So I deleted Windows and reclaimed but I want to leave the Dell
utility and Windows recovery partition.

So how do I install the bootloader in F24 so that it boots sda3?

Is grub still being used?

It's been ~5 years since I last installed Linux so I'm not familiar
with the latest tool chain.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Botched fedup F23 -> F24 with nvidia

2016-11-03 Thread Greg Woods 
On Thu, Nov 3, 2016 at 11:30 AM, Mark  wrote:

> All I got was a grey page with the text "Oh no! Something has
> gone wrong.
>

When using the Nvidia proprietary driver, when I have this happen, the only
way I have successfully recovered is to uninstall everything *nvidia* and
reinstall clean. I just finished doing that yesterday.

--Greg
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: /usr/lib & /usr/lib64 & %{_libdir} in .spec files

2016-11-03 Thread Richard Shaw 
On Thu, Nov 3, 2016 at 11:49 AM, arnaud gaboury 
wrote:

>
>
> On Thu, Nov 3, 2016 at 1:47 PM Richard Shaw  wrote:
>
>> On Thu, Nov 3, 2016 at 6:42 AM, arnaud gaboury 
>> wrote:
>>
>> Below is part of my .spec file:
>> --
>>
>> %install
>> install -Dm644 mattermost.service %{buildroot}/usr/lib/systemd/
>> system/mattermost.service
>> install -Dm644 mattermost-user.conf %{buildroot}/usr/lib/sysusers.
>> d/mattermost.conf
>>
>>
>> First install line change to %{buildroot}%{_unitdir} for the systemd file
>> and the second to use %{buildroot}%{_sysusersdir} for the conf file.
>>
>> Also, be consistent, use the macros both in %install and in %files.
>>
>
> Do you mean this ? :
>
> --
>  %install
> install -Dm644 mattermost.service %{buildroot}%{_unitdir}/
> system/mattermost.service
> install -Dm644 mattermost-user.conf %{buildroot}%{_sysuserdir}/
> mattermost.conf
>
> %files
> %{_unitdir}/system/mattermost.service
> %{_sysuserdir}/mattermost.conf
> --
>

Almost, you can test the macro definitions like so:

$ rpm -E %_unitdir
/usr/lib/systemd/system
$ rpm -E %_sysusersdir
/usr/lib/sysusers.d

So no need to add "system" to the directory.


> Where do these macro come from ? Any doc link ?
>

I'm pretty sure the systemd one comes with the systemd package, not sure
about sysusersdir. I've never needed that one before I only found it like
this:

$ rpm --showrc | grep sysuser
-14: _sysusersdir   /usr/lib/sysusers.d
-14: sysusers_create
systemd-sysusers %{?*} >/dev/null 2>&1 || :
-14: sysusers_create_inline
echo %{?*} | systemd-sysusers - >/dev/null 2>&1 || :

Thanks,
Richard
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Botched fedup F23 -> F24 with nvidia

2016-11-03 Thread Mark 
Hi

I've got a Fedora 23 desktop that I thought was time to upgrade to
Fedora 24. I followed these instructions 
https://fedoramagazine.org/upgrading-fedora-23-workstation-to-fedora-24

And because I have nvidia kernel modules from rpmfusion I also did 
dnf install http://download1.rpmfusion.org/free/fedora/rpmfusion-free-r
elease-24.noarch.rpm
dnf install http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-non
free-release-24.noarch.rpm
before fedup. 

The upgrade process went without any problems until the first boot up
with F24. All I got was a grey page with the text "Oh no! Something has
gone wrong. A problem has occurred and the system can't recover. Please
log out and try again."

With Ctrl-Alt-F2 I could get a terminal, and verified that I had a
matching nvidia module for the new kernel. I tried to run the command
nvidia-xconfig and reboot. I also tried to boot one of the F23 kernels.
I tried to disconnect the second monitor if that would make any
difference. All got was that grey page telling me that something was
wrong. dmesg didn't provide any message that I though would be directly
suspicious.

The graphics card is a Nvidia Quadro 600 (GF108GL)

How to recover?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: /usr/lib & /usr/lib64 & %{_libdir} in .spec files

2016-11-03 Thread arnaud gaboury 
On Thu, Nov 3, 2016 at 1:47 PM Richard Shaw  wrote:

> On Thu, Nov 3, 2016 at 6:42 AM, arnaud gaboury 
> wrote:
>
> Below is part of my .spec file:
> --
>
> %install
> install -Dm644 mattermost.service
> %{buildroot}/usr/lib/systemd/system/mattermost.service
> install -Dm644 mattermost-user.conf
> %{buildroot}/usr/lib/sysusers.d/mattermost.conf
>
>
> First install line change to %{buildroot}%{_unitdir} for the systemd file
> and the second to use %{buildroot}%{_sysusersdir} for the conf file.
>
> Also, be consistent, use the macros both in %install and in %files.
>

Do you mean this ? :

--
 %install
install -Dm644 mattermost.service
%{buildroot}%{_unitdir}/system/mattermost.service
install -Dm644 mattermost-user.conf
%{buildroot}%{_sysuserdir}/mattermost.conf

%files
%{_unitdir}/system/mattermost.service
%{_sysuserdir}/mattermost.conf
--

Where do these macro come from ? Any doc link ?

Thank you

Richard
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

[389-users] Re: Get user password expiration date

2016-11-03 Thread Mark Reynolds 
Leo,

Would you mind if I put this script on our wiki page
(http://www.port389.org)?

Thanks,
Mark

On 11/03/2016 09:49 AM, Leo Pleiman wrote:
> I put together this little script, run from cron, to email my users
> when it's time to change their password. Feel free to use and chop up
> if you like..
>
> #!/usr/bin/perl
>
>
> # Name: check_password_expiration_date.pl
> 
>
> # Author: Leo Pleiman
>
> # Date: July 11, 2013
>
> # This is designed as a cron job to query the password expiration date
> on accounts and send an email
>
> # of the impending expiration to the account owner and the Systems Admins
>
>
> use Date::Calc qw( Delta_Days Today );
>
> use Mail::Sendmail;
>
>
> $cmd = "\/usr\/bin\/ldapsearch -x passwordexpirationtime=*|grep
> uid:|grep -v apple|cut -c6- >/tmp/users\n";
>
> system $cmd;
>
>
> open USERS, "/tmp/users" or die "Couldn't open file";
>
> while () {
>
> chomp;
>
> $user = $_;
>
> $USER = uc($user);
>
> $cmd = "\/usr\/bin\/ldapsearch -x uid=$user +
> passwordexpirationtime|grep passwordexpirationtime:|cut -d: -f2|cut
> -c2-9 >/tmp/date\n";
>
> system $cmd;
>
> system "cat /tmp/date|cut -c1-4 >/tmp/year";
>
> system "cat /tmp/date|cut -c5-6 >/tmp/month";
>
> system "cat /tmp/date|cut -c7-8 >/tmp/day";
>
>
> open FILE, "/tmp/year" or die "Couldn't open file";
>
> while () {
>
> chomp;
>
> $YEAR = $_;
>
> close FILE;
>
> }
>
> open FILE, "/tmp/month" or die "Couldn't open file";
>
> while () {
>
> chomp;
>
> $MONTH = $_;
>
> close FILE;
>
> }
>
> open FILE, "/tmp/day" or die "Couldn't open file";
>
> while () {
>
> chomp;
>
> $DAY = $_;
>
> close FILE;
>
> }
>
>
> ($YEAR2,$MONTH2,$DAY2) = Today();
>
> $days = Delta_Days($YEAR2,$MONTH2,$DAY2, $YEAR,$MONTH,$DAY);
>
>
>
> $DAYS = $days - 7;
>
> #print "$days   $DAYS   $USER\n";
>
> if ($DAYS <= 7 ) {
>
> if ($DAYS <= 0 ) {
>
> %mail = ( To  => "$user\@example.com ",
>
>   Cc  => 'systemsgr...@example.com ',
>
>   From=> 'systemsgr...@example.com
> ',
>
>   Subject => "$USER YOUR PASSWORD HAS EXPIRED",
>
>   Message => "$user, your password has
> expired. You have a limited number of logins avaliable before your
> account will be locked. Proceed immediately to blah, blah, blah\n  
> sysref $days"
>
> );
>
> sendmail(%mail) or die $Mail::Sendmail::error;
>
> }
>
> else {
>
> %mail = ( To  => "$user\@example.com ",
>
>   From=> 'systemsgr...@example.com
> ',
>
>   Subject => "$USER YOUR PASSWORD IS ABOUT TO
> EXPIRE",
>
>   Message => "$user, your password will expire
> in $DAYS days. Reference blah, blah, blah  instructions on changing
> your password."
>
> );
>
> sendmail(%mail) or die $Mail::Sendmail::error;
>
> #print "OK. Log says:\n", $Mail::Sendmail::log;
>
> }
>
> }
>
> }
>
> close USERS;
>
> system "cd /tmp;rm -rf users date year month day";
>
> exit
>
>
> Leo Pleiman
> Senior System Engineer
> Direct 202-787-3622
> Cell 410-688-3873
>
> DonorPro merged with Salsa, read about it here.
> 
>
> On Thu, Nov 3, 2016 at 9:37 AM, Predrag Zečević - Technical Support
> Analyst  > wrote:
>
> On 11/ 3/16 01:21 PM, Mark Reynolds wrote:
>
> Todor,
>
> All you need to do is request the passwordexpirationtime
> attribute from
> the user entry:
>
> For example:
>
> # ldapsearch -D "cn=directory manager" -W -b "dc=domain,dc=com"
> uid=USERID passwordexpirationtime
>
> Regards,
> Mark
>
>
> Hi,
>
> there are also more password attributes:
> $ ldapsearch -xLLLD "cn=directory manager" -W -b
> "dc=my-domain,dc=com" uid=USERID passwordExpirationTime
> passwordExpWarned passwordGraceUserTime passwordRetryCount
> passwordAllowChangeTime passwordHistory
>
> With best regards.
> Predrag Zečević
>
> On 11/03/2016 03:10 AM, Todor Petkov wrote:
>
> Hello,
>
> I am trying to get the user password expiration date, so I
> can write a
> script to send warning email before this. I am running the
> following:
> ldapsearch -v -LLLx -h localhost -b
> 
> 'cn="cn=nsPwPolicyEntry,uid=user,ou=People,dc=domain,dc=com",cn=nsPwPolicyContainer,ou=People,dc=domain,dc=com'
> "(objectclass=ldapsubentry)"
>
> But I don't see such attribute in the results. Can you
> give me a hint
> what's the ldap query? My versions are:
>
> 389-admin-console-1.1.8-1.el6.noarch
>

[389-users] Re: Get user password expiration date

2016-11-03 Thread Leo Pleiman 
I put together this little script, run from cron, to email my users when
it's time to change their password. Feel free to use and chop up if you
like..

#!/usr/bin/perl


# Name: check_password_expiration_date.pl

# Author: Leo Pleiman

# Date: July 11, 2013

# This is designed as a cron job to query the password expiration date on
accounts and send an email

# of the impending expiration to the account owner and the Systems Admins


use Date::Calc qw( Delta_Days Today );

use Mail::Sendmail;


$cmd = "\/usr\/bin\/ldapsearch -x passwordexpirationtime=*|grep uid:|grep
-v apple|cut -c6- >/tmp/users\n";

system $cmd;


open USERS, "/tmp/users" or die "Couldn't open file";

while () {

chomp;

$user = $_;

$USER = uc($user);

$cmd = "\/usr\/bin\/ldapsearch -x uid=$user + passwordexpirationtime|grep
passwordexpirationtime:|cut -d: -f2|cut -c2-9 >/tmp/date\n";

system $cmd;

system "cat /tmp/date|cut -c1-4 >/tmp/year";

system "cat /tmp/date|cut -c5-6 >/tmp/month";

system "cat /tmp/date|cut -c7-8 >/tmp/day";


open FILE, "/tmp/year" or die "Couldn't open file";

while () {

chomp;

$YEAR = $_;

close FILE;

}

open FILE, "/tmp/month" or die "Couldn't open file";

while () {

chomp;

$MONTH = $_;

close FILE;

}

open FILE, "/tmp/day" or die "Couldn't open file";

while () {

chomp;

$DAY = $_;

close FILE;

}


($YEAR2,$MONTH2,$DAY2) = Today();

$days = Delta_Days($YEAR2,$MONTH2,$DAY2, $YEAR,$MONTH,$DAY);



$DAYS = $days - 7;

#print "$days   $DAYS   $USER\n";

if ($DAYS <= 7 ) {

if ($DAYS <= 0 ) {

%mail = ( To  => "$user\@example.com",

  Cc  => 'systemsgr...@example.com',

  From=> 'systemsgr...@example.com',

  Subject => "$USER YOUR PASSWORD HAS EXPIRED",

  Message => "$user, your password has expired. You
have a limited number of logins avaliable before your account will be
locked. Proceed immediately to blah, blah, blah\n   sysref $days"

);

sendmail(%mail) or die $Mail::Sendmail::error;

}

else {

%mail = ( To  => "$user\@example.com",

  From=> 'systemsgr...@example.com',

  Subject => "$USER YOUR PASSWORD IS ABOUT TO
EXPIRE",

  Message => "$user, your password will expire in
$DAYS days. Reference blah, blah, blah  instructions on changing your
password."

);

sendmail(%mail) or die $Mail::Sendmail::error;

# print "OK. Log says:\n", $Mail::Sendmail::log;

}

}

}

close USERS;

system "cd /tmp;rm -rf users date year month day";

exit

Leo Pleiman
Senior System Engineer
Direct 202-787-3622
Cell 410-688-3873

DonorPro merged with Salsa, read about it here.


On Thu, Nov 3, 2016 at 9:37 AM, Predrag Zečević - Technical Support Analyst
 wrote:

> On 11/ 3/16 01:21 PM, Mark Reynolds wrote:
>
>> Todor,
>>
>> All you need to do is request the passwordexpirationtime attribute from
>> the user entry:
>>
>> For example:
>>
>> # ldapsearch -D "cn=directory manager" -W -b "dc=domain,dc=com"
>> uid=USERID passwordexpirationtime
>>
>> Regards,
>> Mark
>>
>>
> Hi,
>
> there are also more password attributes:
> $ ldapsearch -xLLLD "cn=directory manager" -W -b "dc=my-domain,dc=com"
> uid=USERID passwordExpirationTime passwordExpWarned passwordGraceUserTime
> passwordRetryCount passwordAllowChangeTime passwordHistory
>
> With best regards.
> Predrag Zečević
>
>> On 11/03/2016 03:10 AM, Todor Petkov wrote:
>>
>>> Hello,
>>>
>>> I am trying to get the user password expiration date, so I can write a
>>> script to send warning email before this. I am running the following:
>>> ldapsearch -v -LLLx -h localhost -b
>>> 'cn="cn=nsPwPolicyEntry,uid=user,ou=People,dc=domain,dc=com"
>>> ,cn=nsPwPolicyContainer,ou=People,dc=domain,dc=com'
>>> "(objectclass=ldapsubentry)"
>>>
>>> But I don't see such attribute in the results. Can you give me a hint
>>> what's the ldap query? My versions are:
>>>
>>> 389-admin-console-1.1.8-1.el6.noarch
>>> 389-ds-1.2.2-1.el6.noarch
>>> 389-adminutil-1.1.19-1.el6.x86_64
>>> 389-ds-base-libs-1.2.11.15-75.el6_8.x86_64
>>> 389-ds-base-1.2.11.15-75.el6_8.x86_64
>>> 389-ds-console-1.2.6-1.el6.noarch
>>> 389-admin-console-doc-1.1.8-1.el6.noarch
>>> 389-admin-1.1.35-1.el6.x86_64
>>> 389-console-1.1.7-1.el6.noarch
>>> 389-ds-console-doc-1.2.6-1.el6.noarch
>>> 389-dsgw-1.1.11-1.el6.x86_64
>>>
>>>
>>> Thanks in advance,
>>> ___
>>> 389-users mailing list -- 389-users@lists.fedoraproject.org
>>> To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
>>>
>>
>>
>>
>> ___
>> 389-users mailing list -- 389-users@lists.fedoraproject.org
>> To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
>>
>>
> --
> Predrag Zečević
> Technical Support Analyst
> 2e Systems GmbH
>
>

[389-users] Re: Get user password expiration date

2016-11-03 Thread Predrag Zečević - Technical Support Analyst 

On 11/ 3/16 01:21 PM, Mark Reynolds wrote:

Todor,

All you need to do is request the passwordexpirationtime attribute from
the user entry:

For example:

# ldapsearch -D "cn=directory manager" -W -b "dc=domain,dc=com"
uid=USERID passwordexpirationtime

Regards,
Mark



Hi,

there are also more password attributes:
$ ldapsearch -xLLLD "cn=directory manager" -W -b "dc=my-domain,dc=com" 
uid=USERID passwordExpirationTime passwordExpWarned 
passwordGraceUserTime passwordRetryCount passwordAllowChangeTime 
passwordHistory


With best regards.
Predrag Zečević

On 11/03/2016 03:10 AM, Todor Petkov wrote:

Hello,

I am trying to get the user password expiration date, so I can write a
script to send warning email before this. I am running the following:
ldapsearch -v -LLLx -h localhost -b
'cn="cn=nsPwPolicyEntry,uid=user,ou=People,dc=domain,dc=com",cn=nsPwPolicyContainer,ou=People,dc=domain,dc=com'
"(objectclass=ldapsubentry)"

But I don't see such attribute in the results. Can you give me a hint
what's the ldap query? My versions are:

389-admin-console-1.1.8-1.el6.noarch
389-ds-1.2.2-1.el6.noarch
389-adminutil-1.1.19-1.el6.x86_64
389-ds-base-libs-1.2.11.15-75.el6_8.x86_64
389-ds-base-1.2.11.15-75.el6_8.x86_64
389-ds-console-1.2.6-1.el6.noarch
389-admin-console-doc-1.1.8-1.el6.noarch
389-admin-1.1.35-1.el6.x86_64
389-console-1.1.7-1.el6.noarch
389-ds-console-doc-1.2.6-1.el6.noarch
389-dsgw-1.1.11-1.el6.x86_64


Thanks in advance,
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org




___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org



--
Predrag Zečević
Technical Support Analyst
2e Systems GmbH

Telephone: +49 6196 9505 815, Facsimile: +49 6196 9505 894
Mobile:+49  174 3109 288, Skype: predrag.zecevic
E-mail:predrag.zece...@2e-systems.com

Headquarter:  2e Systems GmbH, Königsteiner Str. 87,
  65812 Bad Soden am Taunus, Germany
Company registration: Amtsgericht Königstein (Germany), HRB 7303
Managing director:Phil Douglas

http://www.2e-systems.com/ - Making your business fly!
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org

Re: /usr/lib & /usr/lib64 & %{_libdir} in .spec files

2016-11-03 Thread Richard Shaw 
On Thu, Nov 3, 2016 at 6:42 AM, arnaud gaboury 
wrote:

> Below is part of my .spec file:
> --
>
> %install
> install -Dm644 mattermost.service %{buildroot}/usr/lib/systemd/
> system/mattermost.service
> install -Dm644 mattermost-user.conf %{buildroot}/usr/lib/sysusers.
> d/mattermost.conf
>

First install line change to %{buildroot}%{_unitdir} for the systemd file
and the second to use %{buildroot}%{_sysusersdir} for the conf file.

Also, be consistent, use the macros both in %install and in %files.

Richard
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: /usr/lib & /usr/lib64 & %{_libdir} in .spec files

2016-11-03 Thread Tom Horsley 
On Thu, 03 Nov 2016 11:42:43 +
arnaud gaboury wrote:

> So %{_libdir} seems to point to /usr/lib64 rather than to /usr/lib as
> mentioned in wiki[0].

The default is that 32 bit libraries are in /usr/lib,
64 bit libraries are in /usr/lib64 (for intel architectures
at least)
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

[389-users] Re: Get user password expiration date

2016-11-03 Thread Alberto Viana 
Todor,

Off course, but  I started it today, so maybe I will finish in next week,
please send a email directly to me so I can remember :)

Cheers,

Alberto Viana

On Thu, Nov 3, 2016 at 10:16 AM, Todor Petkov 
wrote:

> On Thu, Nov 3, 2016 at 2:13 PM, Alberto Viana 
> wrote:
> > I'm also working on it right now and using perl to do that, so I used
> filter
> > (objectclass=ntUser) and requesting the passwordExpirationTime attribute
> > like this:
> >
> > filter => "objectclass=ntUser",
> > attrs => ["entrydn","mail","passwordExpirationTime"],
> > );
> >
> > In my case, I prefer rather than write attributes to a file.
> >
> > hope that helps in your case.
> >
>
> Hi,
>
> can you share the script?
>
> Thanks
> ___
> 389-users mailing list -- 389-users@lists.fedoraproject.org
> To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
>
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org

[389-users] Re: Get user password expiration date

2016-11-03 Thread Mark Reynolds 
Todor,

All you need to do is request the passwordexpirationtime attribute from
the user entry:

For example:

# ldapsearch -D "cn=directory manager" -W -b "dc=domain,dc=com"
uid=USERID passwordexpirationtime

Regards,
Mark

On 11/03/2016 03:10 AM, Todor Petkov wrote:
> Hello,
>
> I am trying to get the user password expiration date, so I can write a
> script to send warning email before this. I am running the following:
> ldapsearch -v -LLLx -h localhost -b
> 'cn="cn=nsPwPolicyEntry,uid=user,ou=People,dc=domain,dc=com",cn=nsPwPolicyContainer,ou=People,dc=domain,dc=com'
> "(objectclass=ldapsubentry)"
>
> But I don't see such attribute in the results. Can you give me a hint
> what's the ldap query? My versions are:
>
> 389-admin-console-1.1.8-1.el6.noarch
> 389-ds-1.2.2-1.el6.noarch
> 389-adminutil-1.1.19-1.el6.x86_64
> 389-ds-base-libs-1.2.11.15-75.el6_8.x86_64
> 389-ds-base-1.2.11.15-75.el6_8.x86_64
> 389-ds-console-1.2.6-1.el6.noarch
> 389-admin-console-doc-1.1.8-1.el6.noarch
> 389-admin-1.1.35-1.el6.x86_64
> 389-console-1.1.7-1.el6.noarch
> 389-ds-console-doc-1.2.6-1.el6.noarch
> 389-dsgw-1.1.11-1.el6.x86_64
>
>
> Thanks in advance,
> ___
> 389-users mailing list -- 389-users@lists.fedoraproject.org
> To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org

___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org

[389-users] Re: Get user password expiration date

2016-11-03 Thread Todor Petkov 
On Thu, Nov 3, 2016 at 2:13 PM, Alberto Viana  wrote:
> I'm also working on it right now and using perl to do that, so I used filter
> (objectclass=ntUser) and requesting the passwordExpirationTime attribute
> like this:
>
> filter => "objectclass=ntUser",
> attrs => ["entrydn","mail","passwordExpirationTime"],
> );
>
> In my case, I prefer rather than write attributes to a file.
>
> hope that helps in your case.
>

Hi,

can you share the script?

Thanks
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org

[389-users] Re: Get user password expiration date

2016-11-03 Thread Alberto Viana 
I'm also working on it right now and using perl to do that, so I used
filter (objectclass=ntUser) and requesting the passwordExpirationTime
attribute like this:

filter => "objectclass=ntUser",
attrs => ["entrydn","mail","passwordExpirationTime"],
);

In my case, I prefer rather than write attributes to a file.

hope that helps in your case.




On Thu, Nov 3, 2016 at 6:44 AM, Predrag Zečević - Technical Support Analyst
 wrote:

> On 11/ 3/16 08:10 AM, Todor Petkov wrote:
>
>> Hello,
>>
>> I am trying to get the user password expiration date, so I can write a
>> script to send warning email before this. I am running the following:
>> ldapsearch -v -LLLx -h localhost -b
>> 'cn="cn=nsPwPolicyEntry,uid=user,ou=People,dc=domain,dc=com"
>> ,cn=nsPwPolicyContainer,ou=People,dc=domain,dc=com'
>> "(objectclass=ldapsubentry)"
>>
>> But I don't see such attribute in the results. Can you give me a hint
>> what's the ldap query? My versions are:
>>
>> 389-admin-console-1.1.8-1.el6.noarch
>> 389-ds-1.2.2-1.el6.noarch
>> 389-adminutil-1.1.19-1.el6.x86_64
>> 389-ds-base-libs-1.2.11.15-75.el6_8.x86_64
>> 389-ds-base-1.2.11.15-75.el6_8.x86_64
>> 389-ds-console-1.2.6-1.el6.noarch
>> 389-admin-console-doc-1.1.8-1.el6.noarch
>> 389-admin-1.1.35-1.el6.x86_64
>> 389-console-1.1.7-1.el6.noarch
>> 389-ds-console-doc-1.2.6-1.el6.noarch
>> 389-dsgw-1.1.11-1.el6.x86_64
>>
>>
>> Thanks in advance,
>> ___
>> 389-users mailing list -- 389-users@lists.fedoraproject.org
>> To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
>>
>>
> Hi,
>
> we are using something like:
>
> $ ldapsearch -xLLL -D "cn=Directory Manager" -W -b
> "cn=nsPwPolicyContainer,ou=people,dc=my-domain,dc=com"
> "(&(objectClass=ldapsubentry)(objectClass=passwordPolicy)(cn=${givenName}
> ${sn}))"
>
> to get password policy setup for user "cn=${givenName} ${sn}"  and check
> for values:
>
> passwordInHistory: 5
> passwordMinAge: 600
> passwordChange: on
> passwordUnlock: on
> passwordLockoutDuration: 1800
> passwordResetFailureCount: 600
> passwordLockout: on
> passwordMaxFailure: 10
> passwordMaxRepeats: 0
> passwordStorageScheme: ssha
> passwordMaxAge: 7776000
> passwordExp: on
> passwordGraceLimit: 6
> passwordMin8bit: 0
> passwordMinAlphas: 0
> passwordMinSpecials: 1
> passwordMinDigits: 1
> passwordMinLowers: 1
> passwordMinUppers: 1
> passwordMinTokenLength: 5
> passwordMinCategories: 4
> passwordMinLength: 8
> passwordCheckSyntax: on
> passwordMustChange: off
>
>
> Password data is retrieved from LDAP backup ldif, created with command:
>
> $ /usr/lib${ARCH}/dirsrv/slapd-${PADL}/db2ldif.pl -U -N -u -C -D
> 'cn=Directory Manager' -w - -n userRoot -a /tmp/LDAP_dump.ldif
>
> e.g. searching for password data for "cn=${givenName} ${sn}" in output
> file /tmp/LDAP_dump.ldif
>
> passwordExpWarned: 0
> passwordExpirationTime: 20161214070525Z
> passwordGraceUserTime: 0
> passwordAllowChangeTime: 20160915071525Z
> passwordHistory: 20160915070525Z{SSHA}HASH
> passwordHistory: 20150927121604Z{SSHA}HASH
> passwordHistory: 20151228130437Z{SSHA}HASH
> passwordHistory: 20160324145753Z{SSHA}HASH
> passwordHistory: 20160621103821Z{SSHA}HASH
>
> Script parses output for user; determines e-mail address and if reminder
> has to be sent... (maybe there is better way to get that data, but this one
> works).
>
> HTH
>
> With best regards.
> Predrag Zečević
> --
> Predrag Zečević
> Technical Support Analyst
> 2e Systems GmbH
>
> Telephone: +49 6196 9505 815, Facsimile: +49 6196 9505 894
> Mobile:+49 174 3109 288, Skype: predrag.zecevic
> E-mail:predrag.zece...@2e-systems.com
>
> Headquarter:  2e Systems GmbH, Königsteiner Str. 87,
>   65812 Bad Soden am Taunus, Germany
> Company registration: Amtsgericht Königstein (Germany), HRB 7303
> Managing director:Phil Douglas
>
> http://www.2e-systems.com/ - Making your business fly!
>
> ___
> 389-users mailing list -- 389-users@lists.fedoraproject.org
> To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
>
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org

/usr/lib & /usr/lib64 & %{_libdir} in .spec files

2016-11-03 Thread arnaud gaboury 
Below is part of my .spec file:
--

%install
install -Dm644 mattermost.service
%{buildroot}/usr/lib/systemd/system/mattermost.service
install -Dm644 mattermost-user.conf
%{buildroot}/usr/lib/sysusers.d/mattermost.conf

%files
%{_libdir}/systemd/system/mattermost.conf
%{_libdir}/sysusers.d/mattermost.conf

--

which throw two errors when building:

error: File not found:
/home/makerpm/rpmbuild/BUILDROOT/mattermost-3.4-1.fc24.x86_64/usr/lib64/systemd/system/mattermost.conf
error: File not found:
/home/makerpm/rpmbuild/BUILDROOT/mattermost-3.4-1.fc24.x86_64/usr/lib64/sysusers.d/mattermost.conf

I understand I installed these two files in /usr/lib/ (which is what I
want), as said by the below output:
--
+ install -Dm644 mattermost.service
/home/makerpm/rpmbuild/BUILDROOT/mattermost-3.4-1.fc24.x86_64/usr/lib/systemd/system/mattermost.service
+ install -Dm644 mattermost-user.conf
/home/makerpm/rpmbuild/BUILDROOT/mattermost-3.4-1.fc24.x86_64/usr/lib/sysusers.d/mattermost.conf
--

BUT Fedora is looking for them in /usr/lib64, right ?

So %{_libdir} seems to point to /usr/lib64 rather than to /usr/lib as
mentioned in wiki[0].

Am I right? Shall I then write this in %files ? :

/usr/lib/systemd/system/mattermost.conf
/usr/lib/sysusers.d/mattermost.conf

Thank you for help.

[0]https://fedoraproject.org/wiki/How_to_create_an_RPM_package
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: can't shutdown (a stop job is running...)

2016-11-03 Thread Tom Horsley 
On Thu, 3 Nov 2016 17:10:12 +0800
Ed Greshko wrote:

> Being that it is a "common issue" are you aware of any bugzilla open on this?

Just search bugzilla for "a stop job is running":

https://bugzilla.redhat.com/show_bug.cgi?id=1337526
https://bugzilla.redhat.com/show_bug.cgi?id=1307260

But they never fix it, they just wait till the release hits
EOL and let bugzilla automatically close it:

https://bugzilla.redhat.com/show_bug.cgi?id=1088619
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: can't shutdown (a stop job is running...)

2016-11-03 Thread Ed Greshko 


On 11/03/16 14:50, Samuel Sieb wrote:
> On 11/01/2016 07:31 AM, Ed Greshko wrote:
>> On 11/01/16 22:26, Ed Greshko wrote:
>>> On 11/01/16 22:21, Ed Greshko wrote:
 On 11/01/16 18:49, Neal Becker wrote:
> For quite some time now, when I try to reboot (from kde) the shutdown gets
> stuck saying "a stop job is running for ...".  I just hold the power 
> button.
> Any ideas?
 Next time, before you attempt to reboot, issue the "jobs" command in a 
 terminal
 window and
 it should tell you what job is stopped.

>>> Humm.  Sadly, the jobs command will only list jobs which have been 
>>> stopped/owned by
>>> the current shell.  :-(
>>>
>> But, you can use "ps -aux" and find the process with a STAT of "T".
>>
> It's not about stopped jobs, it's about systemd trying to stop some 
> process/service. 
> This has unfortunately been a common issue.  Usually it will time out after 
> 1.5 minutes
> or maybe more, but it should eventually time out and finish the shutdown.  Or 
> try
> CTRL-ALT-DEL, that sometimes makes it continue as well.

Thanks.  I must have mis-read and/or mis-understood what was being said

Being that it is a "common issue" are you aware of any bugzilla open on this?  
I've not
seen this sort of issue on any of my systems other than one which happens only 
when there
was an NFS mount over a WiFi connection and that has been fixed about a year 
ago.

-- 
You're Welcome Zachary Quinto
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

[389-users] Re: Get user password expiration date

2016-11-03 Thread Predrag Zečević - Technical Support Analyst 

On 11/ 3/16 08:10 AM, Todor Petkov wrote:

Hello,

I am trying to get the user password expiration date, so I can write a
script to send warning email before this. I am running the following:
ldapsearch -v -LLLx -h localhost -b
'cn="cn=nsPwPolicyEntry,uid=user,ou=People,dc=domain,dc=com",cn=nsPwPolicyContainer,ou=People,dc=domain,dc=com'
"(objectclass=ldapsubentry)"

But I don't see such attribute in the results. Can you give me a hint
what's the ldap query? My versions are:

389-admin-console-1.1.8-1.el6.noarch
389-ds-1.2.2-1.el6.noarch
389-adminutil-1.1.19-1.el6.x86_64
389-ds-base-libs-1.2.11.15-75.el6_8.x86_64
389-ds-base-1.2.11.15-75.el6_8.x86_64
389-ds-console-1.2.6-1.el6.noarch
389-admin-console-doc-1.1.8-1.el6.noarch
389-admin-1.1.35-1.el6.x86_64
389-console-1.1.7-1.el6.noarch
389-ds-console-doc-1.2.6-1.el6.noarch
389-dsgw-1.1.11-1.el6.x86_64


Thanks in advance,
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org



Hi,

we are using something like:

$ ldapsearch -xLLL -D "cn=Directory Manager" -W -b 
"cn=nsPwPolicyContainer,ou=people,dc=my-domain,dc=com" 
"(&(objectClass=ldapsubentry)(objectClass=passwordPolicy)(cn=${givenName} 
${sn}))"


to get password policy setup for user "cn=${givenName} ${sn}"  and check 
for values:


passwordInHistory: 5
passwordMinAge: 600
passwordChange: on
passwordUnlock: on
passwordLockoutDuration: 1800
passwordResetFailureCount: 600
passwordLockout: on
passwordMaxFailure: 10
passwordMaxRepeats: 0
passwordStorageScheme: ssha
passwordMaxAge: 7776000
passwordExp: on
passwordGraceLimit: 6
passwordMin8bit: 0
passwordMinAlphas: 0
passwordMinSpecials: 1
passwordMinDigits: 1
passwordMinLowers: 1
passwordMinUppers: 1
passwordMinTokenLength: 5
passwordMinCategories: 4
passwordMinLength: 8
passwordCheckSyntax: on
passwordMustChange: off


Password data is retrieved from LDAP backup ldif, created with command:

$ /usr/lib${ARCH}/dirsrv/slapd-${PADL}/db2ldif.pl -U -N -u -C -D 
'cn=Directory Manager' -w - -n userRoot -a /tmp/LDAP_dump.ldif


e.g. searching for password data for "cn=${givenName} ${sn}" in output 
file /tmp/LDAP_dump.ldif


passwordExpWarned: 0
passwordExpirationTime: 20161214070525Z
passwordGraceUserTime: 0
passwordAllowChangeTime: 20160915071525Z
passwordHistory: 20160915070525Z{SSHA}HASH
passwordHistory: 20150927121604Z{SSHA}HASH
passwordHistory: 20151228130437Z{SSHA}HASH
passwordHistory: 20160324145753Z{SSHA}HASH
passwordHistory: 20160621103821Z{SSHA}HASH

Script parses output for user; determines e-mail address and if reminder 
has to be sent... (maybe there is better way to get that data, but this 
one works).


HTH

With best regards.
Predrag Zečević
--
Predrag Zečević
Technical Support Analyst
2e Systems GmbH

Telephone: +49 6196 9505 815, Facsimile: +49 6196 9505 894
Mobile:+49  174 3109 288, Skype: predrag.zecevic
E-mail:predrag.zece...@2e-systems.com

Headquarter:  2e Systems GmbH, Königsteiner Str. 87,
  65812 Bad Soden am Taunus, Germany
Company registration: Amtsgericht Königstein (Germany), HRB 7303
Managing director:Phil Douglas

http://www.2e-systems.com/ - Making your business fly!
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org

Re: Emacs24 at f24/f25

2016-11-03 Thread Saša Janiška 
stan  writes:

> All past built fedora packages are available in koji.  So if you go to
> http://koji.fedoraproject.org/koji/packageinfo?packageID=560 you can
> download the emacs package of your choice.  And then install it using
> dnf -C downgrade emacs[rest of rpm name] You'll have to provide all
> dependencies of the downgraded package that dnf asks for as well (also
> from koji).

OK. It sounds good.

> A more involved solution would see you building an RPM for F24 from the
> F22 src.rpm.  And blocking further updates to emacs using the -x
> option to dnf.

Well, that’s the last resort.

> I'm not sure what org is,

It’s well-know org-mode package (http://orgmode.org)

> but is there no way to bring it into compliance with emacs 25? A lot
> easier in the long run to stay in synchronization with the OS you are
> running.

Org-9.0 is just released, it behaves a little better with 25.1 and maybe
it’s only some sort of Debian-ism, so on Fedora it might be even better
since, afaik, it’s closer to the upstream…


Sincerely,
Gour

-- 
One who works in devotion, who is a pure soul, and who controls
his mind and senses is dear to everyone, and everyone is dear to
him. Though always working, such a man is never entangled.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

[389-users] Get user password expiration date

2016-11-03 Thread Todor Petkov 
Hello,

I am trying to get the user password expiration date, so I can write a
script to send warning email before this. I am running the following:
ldapsearch -v -LLLx -h localhost -b
'cn="cn=nsPwPolicyEntry,uid=user,ou=People,dc=domain,dc=com",cn=nsPwPolicyContainer,ou=People,dc=domain,dc=com'
"(objectclass=ldapsubentry)"

But I don't see such attribute in the results. Can you give me a hint
what's the ldap query? My versions are:

389-admin-console-1.1.8-1.el6.noarch
389-ds-1.2.2-1.el6.noarch
389-adminutil-1.1.19-1.el6.x86_64
389-ds-base-libs-1.2.11.15-75.el6_8.x86_64
389-ds-base-1.2.11.15-75.el6_8.x86_64
389-ds-console-1.2.6-1.el6.noarch
389-admin-console-doc-1.1.8-1.el6.noarch
389-admin-1.1.35-1.el6.x86_64
389-console-1.1.7-1.el6.noarch
389-ds-console-doc-1.2.6-1.el6.noarch
389-dsgw-1.1.11-1.el6.x86_64


Thanks in advance,
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org

Re: can't shutdown (a stop job is running...)

2016-11-03 Thread Samuel Sieb 

On 11/01/2016 07:31 AM, Ed Greshko wrote:

On 11/01/16 22:26, Ed Greshko wrote:

On 11/01/16 22:21, Ed Greshko wrote:

On 11/01/16 18:49, Neal Becker wrote:

For quite some time now, when I try to reboot (from kde) the shutdown gets
stuck saying "a stop job is running for ...".  I just hold the power button.
Any ideas?

Next time, before you attempt to reboot, issue the "jobs" command in a terminal 
window and
it should tell you what job is stopped.


Humm.  Sadly, the jobs command will only list jobs which have been 
stopped/owned by
the current shell.  :-(


But, you can use "ps -aux" and find the process with a STAT of "T".

It's not about stopped jobs, it's about systemd trying to stop some 
process/service.  This has unfortunately been a common issue.  Usually 
it will time out after 1.5 minutes or maybe more, but it should 
eventually time out and finish the shutdown.  Or try CTRL-ALT-DEL, that 
sometimes makes it continue as well.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org