Re: [CentOS] persistent generic device for tape changer

2019-02-07 Thread Ron Loftin


I've taken you as far as I can go.  Now you will have to experiment a
bit for your use case.  I should point out that at least in my system,
the link with the serial number in it shows up even with the line
commented in the rules file.

As always, YMMV.

On Thu, 2019-02-07 at 22:29 +0100, Helmut Drodofsky wrote:
> Hello Ron,
> 
> sounds good. I have 2 tape changer. I persume, udev creates the same
> link for both.
> 
> Can I modify
> SYMLINK+="changer-$env{ID_SERIAL}"
> 
> The serial should be unique.
> 
> Viele Grüße
> Helmut Drodofsky
> 
> Internet XS Service GmbH
> Heßbrühlstraße 15
> 70565 Stuttgart
> 
> Geschäftsführung
> Helmut Drodofsky
> HRB 21091 Stuttgart
> USt.ID: DE190582774
> Fon: 0711 781941 0 
> Fax: 0711 781941 79
> Mail: i...@internet-xs.de
> www.internet-xs.de
> Am 07.02.2019 um 16:17 schrieb Ron Loftin:
> > 
> > On Thu, 2019-02-07 at 10:56 +0100, Helmut Drodofsky wrote:
> > > 
> > > Hello,
> > > 
> > > mtx and therefor amanda use generic device /dev/sg for tape
> > > changer.
> > > 
> > > These devices change on reboot.
> > > 
> > > How to make them persistent?
> > > 
> > > /dev/sch0 and /dev/sch1 seem to be persistent.
> > > 
> > > /dev/tape/by-id/ shows links from WWID to generic device
> > > 
> > > An UDEV rule could help? I have not found any example.
> > I had a similar issue when I moved to Mint 18 with the tape device.
> >  This works with kernel 4.10 and later.  Copy /lib/udev/rules.d/60-
> > persistent-storage-tape.rules to /etc/udev/rules.d and make a
> > change as
> > shown:
> > 
> > diff -n /lib/udev/rules.d/60-persistent-storage-tape.rules
> > /etc/udev/rules.d/60-persistent-storage-tape.rules 
> > d9 1
> > a9 2
> >    SYMLINK+="changer"
> > #  SYMLINK+="tape/by-id/scsi-$env{ID_SERIAL}"
> > 
> > This created /dev/changer as a link to the /dev/sg device that
> > will
> > be consistent every time the system is booted.
> > 
> > > 
> > > 
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
-- 
Ron Loftin  relof...@twcny.rr.com

"God, root, what is difference ?"   Piter from UserFriendly


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] systemd

2019-02-07 Thread James Pearson
Jerry Geis wrote:
> 
> Hi All -  I have a systemd service file to start my application.
> 
> Part of my service file is:
> [Service]
> Type=forking
> ExecStart=/path to start
> ExecStop=/path to stop
> RemainAfterExit=yes
> 
> This works fine "normally".
> 
> However - when I do a "yum update; and reboot"  my script detects a kernel
> change and now does a number of "recompiling" steps for drivers and such
> before starting my application. Somewhere along the way that just stops.
> I'm half way into recompiling those drivers and it just stops.

Could it be you are hitting some default timeout ?

Maybe adding 'TimeoutSec=infinity' could help ?

Or, maybe moving your 'recompiling' stage to an ExecStartPre script ?

(no idea if either of the above will help)

James Pearson
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] persistent generic device for tape changer

2019-02-07 Thread Helmut Drodofsky
Hello Ron,

sounds good. I have 2 tape changer. I persume, udev creates the same
link for both.

Can I modify
SYMLINK+="changer-$env{ID_SERIAL}"

The serial should be unique.

Viele Grüße
Helmut Drodofsky

Internet XS Service GmbH
Heßbrühlstraße 15
70565 Stuttgart

Geschäftsführung
Helmut Drodofsky
HRB 21091 Stuttgart
USt.ID: DE190582774
Fon: 0711 781941 0 
Fax: 0711 781941 79
Mail: i...@internet-xs.de
www.internet-xs.de
Am 07.02.2019 um 16:17 schrieb Ron Loftin:
> On Thu, 2019-02-07 at 10:56 +0100, Helmut Drodofsky wrote:
>> Hello,
>>
>> mtx and therefor amanda use generic device /dev/sg for tape
>> changer.
>>
>> These devices change on reboot.
>>
>> How to make them persistent?
>>
>> /dev/sch0 and /dev/sch1 seem to be persistent.
>>
>> /dev/tape/by-id/ shows links from WWID to generic device
>>
>> An UDEV rule could help? I have not found any example.
> I had a similar issue when I moved to Mint 18 with the tape device.
>  This works with kernel 4.10 and later.  Copy /lib/udev/rules.d/60-
> persistent-storage-tape.rules to /etc/udev/rules.d and make a change as
> shown:
>
> diff -n /lib/udev/rules.d/60-persistent-storage-tape.rules
> /etc/udev/rules.d/60-persistent-storage-tape.rules 
> d9 1
> a9 2
>    SYMLINK+="changer"
> #  SYMLINK+="tape/by-id/scsi-$env{ID_SERIAL}"
>
> This created /dev/changer as a link to the /dev/sg device that will
> be consistent every time the system is booted.
>
>>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


[CentOS] Did I install too much for clamav?

2019-02-07 Thread Robert Moskowitz

I just checked the status of amavisd:

# systemctl -l status amavisd
● amavisd.service - Amavisd-new is an interface between MTA and content 
checkers.
   Loaded: loaded (/usr/lib/systemd/system/amavisd.service; enabled; 
vendor preset: disabled)

   Active: active (running) since Thu 2019-02-07 08:16:59 EST; 7h ago
 Docs: http://www.ijs.si/software/amavisd/#doc
  Process: 5715 ExecStart=/usr/sbin/amavisd -c 
/etc/amavisd/amavisd.conf (code=exited, status=0/SUCCESS)

 Main PID: 6327 (/usr/sbin/amavi)
   CGroup: /system.slice/amavisd.service
   ├─6327 /usr/sbin/amavisd (master)
   ├─6336 /usr/sbin/amavisd (virgin child)
   └─6337 /usr/sbin/amavisd (virgin child)

Feb 07 08:16:59 klovia.htt-consult.com amavis[6327]: Found decoder 
for    .lha  at /usr/bin/7z
Feb 07 08:16:59 klovia.htt-consult.com amavis[6327]: Found decoder 
for    .iso  at /usr/bin/7z
Feb 07 08:16:59 klovia.htt-consult.com amavis[6327]: Found decoder 
for    .exe  at /usr/bin/unarj
Feb 07 08:16:59 klovia.htt-consult.com amavis[6327]: Using primary 
internal av scanner code for ClamAV-clamd
Feb 07 08:16:59 klovia.htt-consult.com amavis[6327]: Found secondary av 
scanner ClamAV-clamscan at /usr/bin/clamscan
Feb 07 08:16:59 klovia.htt-consult.com amavis[6327]: Deleting db files 
__db.002,snmp.db,nanny.db,__db.001,__db.003 in /var/spool/amavisd/db
Feb 07 08:16:59 klovia.htt-consult.com amavis[6327]: Creating db in 
/var/spool/amavisd/db/; BerkeleyDB 0.51, libdb 5.3
Feb 07 08:17:00 klovia.htt-consult.com amavis[6327]: initializing 
Mail::SpamAssassin (0)
Feb 07 08:17:08 klovia.htt-consult.com amavis[6327]: SpamControl: 
init_pre_fork on SpamAssassin done
Feb 07 08:17:08 klovia.htt-consult.com amavis[6327]: extra modules 
loaded after daemonizing/chrooting: 
/usr/lib/perl5/vendor_perl/auto/Net/SSLeay/autosplit.ix, 
/usr/lib/perl5/vendor_perl/auto/Net/SSLeay/randomize.al, 
/usr/share/perl5/Net/libnet.cfg, IO/Socket/SSL.pm, 
Mail/SpamAssassin/Plugin/FreeMail.pm, 
Mail/SpamAssassin/Plugin/SpamCop.pm, Net/Cmd.pm, Net/Config.pm, 
Net/SMTP.pm, Net/SSLeay.pm



Primary and secondary AV scanner?  Is this right?  I installed:

# grep clam /var/log/yum.log*
/var/log/yum.log:Feb 06 08:40:06 Installed: 
clamav-filesystem-0.101.1-1.el7.noarch

/var/log/yum.log:Feb 06 08:40:29 Installed: clamav-lib-0.101.1-1.el7.armv7hl
/var/log/yum.log:Feb 06 08:40:30 Installed: 
clamav-update-0.101.1-1.el7.armv7hl
/var/log/yum.log:Feb 06 08:40:59 Installed: 
clamav-devel-0.101.1-1.el7.armv7hl

/var/log/yum.log:Feb 06 08:41:01 Installed: clamav-0.101.1-1.el7.armv7hl
/var/log/yum.log:Feb 06 08:46:16 Installed: clamd-0.101.1-1.el7.armv7hl
/var/log/yum.log:Feb 06 08:46:17 Installed: 
clamav-server-systemd-0.101.1-1.el7.armv7hl


thanks


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 6 and 389 Directory Server

2019-02-07 Thread Leon Fauster via CentOS


> Am 07.02.2019 um 19:16 schrieb Eugene Poole :
> 
> I'm not sure it this is the correct location to ask these questions, but ...
> 
> In the past when I worked for a living the place where I worked had thousands 
> of RHEL Linux servers on various hardware, but the access was controlled by 
> Windows Active Directory and a third party piece of software that was the 
> middle-man between the 2.
> 
> Now that I no longer work I'm trying to build a CentOS Linux environment 
> where the access is controlled by 389-Directory Server. But I have no 
> practical experience with 389-Directory Server (Question 1) so I'm looking 
> for a tutorial or 'How To' to put information into 389-DS from a machine that 
> is currently running? (Question 2) Can I export the 389-DS database to a LDIF 
> file, migrate my machine from CentOS 6 to CentOS 7 by doing a fresh CentOS 7 
> install. Install 389-DS and import the just created LDIF file?  I want to use 
> 389-DS (or OpenLDAP) because as my environment grows defining everything 
> locally is becoming hard to be exact.
> 
> Any comments will be helpful


https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html-single/identity_management_guide/

https://www.freeipa.org/page/Main_Page

--
LF

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS-virt] Cri-o 1.13 package

2019-02-07 Thread Matheus Eduardo Bonifacio Morais
Hi Fero,

Thanks for your reply. Anything that I can do to help you on that task?

Thanks.


Em 07/02/2019 12:48, Frantisek Kluknavsky escreveu:
> On 07/02/2019 15:45, Matheus Eduardo Bonifacio Morais wrote:
>> Hi there,
>>
>> I was looking for cri-o 1.13 package to install on CentOS 7.6 but it
>> seems that we only have 1.11 packaged.
>>
>> There is any alternative to 1.13 package to CenOS 7.6 or if I want to
>> use it I should build from source?
>>
>> Thanks.
> Hi,
>
> building 1.13 is on my ever-growing list of tasks, I definitely want to
> do it but will not give you any ETA.
>
> Fero
>

--
Matheus Eduardo Bonifácio Morais
Analista de Infraestrutura de TI,
Plataforma e Aplicações
Confederação Sicredi

Centro Administrativo Sicredi – Porto Alegre
+55 51 3358 7143

sicredi.com.br
Esta mensagem é somente para uso do destinatário informado e pode conter 
informações privilegiadas, proprietárias ou privadas. Se você recebeu esta 
mensagem por engano, por favor, notifique o remetente imediatamente e apague a 
original. Qualquer outro uso deste e-mail é proibido.

This message is for the designated recipient only and may contain privileged, 
proprietary, or otherwise private information. If you have received it in 
error, please notify the sender immediately and delete the original. Any other 
use of the email by you is prohibited.
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt


[CentOS] CentOS 6 and 389 Directory Server

2019-02-07 Thread Eugene Poole

I'm not sure it this is the correct location to ask these questions, but ...

In the past when I worked for a living the place where I worked had 
thousands of RHEL Linux servers on various hardware, but the access was 
controlled by Windows Active Directory and a third party piece of 
software that was the middle-man between the 2.


Now that I no longer work I'm trying to build a CentOS Linux environment 
where the access is controlled by 389-Directory Server. But I have no 
practical experience with 389-Directory Server (Question 1) so I'm 
looking for a tutorial or 'How To' to put information into 389-DS from a 
machine that is currently running? (Question 2) Can I export the 389-DS 
database to a LDIF file, migrate my machine from CentOS 6 to CentOS 7 by 
doing a fresh CentOS 7 install. Install 389-DS and import the just 
created LDIF file?  I want to use 389-DS (or OpenLDAP) because as my 
environment grows defining everything locally is becoming hard to be exact.


Any comments will be helpful

TIA

--
Eugene Poole
Woodstock, Georgia

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


[CentOS-docs] [Gitblit] rbowen pushed 1 commits => websites/centos.org.git

2019-02-07 Thread Gitblit
https://git.centos.org/summary/websites!centos.org.git

>---
 master branch updated (1 commits)
>---

 rbowen 
 Thursday, February 7, 2019 15:18 +

 typo

 
https://git.centos.org/commit/websites!centos.org.git/1d81f753401ff761c1ae5ff0857dce657b55b837
___
CentOS-docs mailing list
CentOS-docs@centos.org
https://lists.centos.org/mailman/listinfo/centos-docs


Re: [CentOS] Pb with bounding

2019-02-07 Thread Pierre Malard
Sorry, my answer take a while… but I would test before write.

Effectively, the problem became from switch configuration.
Our switch are a stack of Avaya ERS4870 and I have difficulties to understand 
the interface. I had configure all ports concerned by my configuration like 
that for all ports:
In the « VLAN » Configuration:
  - VLAN tagging: « tagAll(trunk) »
  - « PrivateVlanPortType »: « trunk »
  - « DefaultVlanID » : to a LAN not distribued. I don’t understand why they 
ask for that even I choose « tagAll » (!!!)
For the « LACP » one:
  - activate « AdmiEnabled »
  - « ActorAdminState » structure: activation of « lacpActive », « aggregation 
» and « shortTimeout »
  - « actorAdminKey »: chose one

In my case the problem come that I have gave one of my real VLAN as « 
DefaultVlanID ». With this configuration no paquet can pass. Now I have choose 
the VLAN 1 in this case and everything is Ok.

Best regards and thanks…

> Le 7 févr. 2019 à 01:36, Gordon Messmer  a écrit :
> 
> On 2/6/19 9:47 AM, Pierre Malard wrote:
>> We have a Dell server with 4 Ethernet interface. I would to aggregate them 
>> in a bond.
>> ...
>> :/etc/sysconfig/network-scripts# cat ifcfg-bond0
>> ...
>> BONDING_OPTS="mode=802.3ad
> 
> 
> What type of managed switch are you using for those interfaces? Can you also 
> include the configuration that you gave the switch? Do the switch logs 
> indicate any errors with the bonded ports?
> 
> 
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos

--
Pierre Malard

   « Tant que les lions n’auront pas leurs propres historiens, les histoires
   de chasse tourneront toujours à la gloire du chasseur »
  Proverbe africain
   |\  _,,,---,,_
   /,`.-'`'-.  ;-;;,_
  |,4-  ) )-,_. ,\ (  `'-'
 '---''(_/--'  `-'\_)  πr

perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-.  ;-;;,_:  |,A-  ) )-,_. ,\ 
(  `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"'  `-'"'"'\_): 
24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print'
- --> Ce message n’engage que son auteur <--



signature.asc
Description: Message signed with OpenPGP
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] persistent generic device for tape changer

2019-02-07 Thread Ron Loftin
On Thu, 2019-02-07 at 10:56 +0100, Helmut Drodofsky wrote:
> Hello,
> 
> mtx and therefor amanda use generic device /dev/sg for tape
> changer.
> 
> These devices change on reboot.
> 
> How to make them persistent?
> 
> /dev/sch0 and /dev/sch1 seem to be persistent.
> 
> /dev/tape/by-id/ shows links from WWID to generic device
> 
> An UDEV rule could help? I have not found any example.

I had a similar issue when I moved to Mint 18 with the tape device.
 This works with kernel 4.10 and later.  Copy /lib/udev/rules.d/60-
persistent-storage-tape.rules to /etc/udev/rules.d and make a change as
shown:

diff -n /lib/udev/rules.d/60-persistent-storage-tape.rules
/etc/udev/rules.d/60-persistent-storage-tape.rules 
d9 1
a9 2
   SYMLINK+="changer"
#  SYMLINK+="tape/by-id/scsi-$env{ID_SERIAL}"

This created /dev/changer as a link to the /dev/sg device that will
be consistent every time the system is booted.

> 
> 
-- 
Ron Loftin  relof...@twcny.rr.com

"God, root, what is difference ?"   Piter from UserFriendly


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS-virt] Cri-o 1.13 package

2019-02-07 Thread Frantisek Kluknavsky
On 07/02/2019 15:45, Matheus Eduardo Bonifacio Morais wrote:
> Hi there,
> 
> I was looking for cri-o 1.13 package to install on CentOS 7.6 but it
> seems that we only have 1.11 packaged.
> 
> There is any alternative to 1.13 package to CenOS 7.6 or if I want to
> use it I should build from source?
> 
> Thanks.

Hi,

building 1.13 is on my ever-growing list of tasks, I definitely want to
do it but will not give you any ETA.

Fero



signature.asc
Description: OpenPGP digital signature
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt


[CentOS-virt] Cri-o 1.13 package

2019-02-07 Thread Matheus Eduardo Bonifacio Morais
Hi there,

I was looking for cri-o 1.13 package to install on CentOS 7.6 but it
seems that we only have 1.11 packaged.

There is any alternative to 1.13 package to CenOS 7.6 or if I want to
use it I should build from source?

Thanks.

--
Matheus Eduardo Bonifácio Morais
Analista de Infraestrutura de TI,
Plataforma e Aplicações
Confederação Sicredi

Centro Administrativo Sicredi – Porto Alegre
+55 51 3358 7143

sicredi.com.br
Esta mensagem é somente para uso do destinatário informado e pode conter 
informações privilegiadas, proprietárias ou privadas. Se você recebeu esta 
mensagem por engano, por favor, notifique o remetente imediatamente e apague a 
original. Qualquer outro uso deste e-mail é proibido.

This message is for the designated recipient only and may contain privileged, 
proprietary, or otherwise private information. If you have received it in 
error, please notify the sender immediately and delete the original. Any other 
use of the email by you is prohibited.
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt


[CentOS] systemd

2019-02-07 Thread Jerry Geis
Hi All -  I have a systemd service file to start my application.

Part of my service file is:
[Service]
Type=forking
ExecStart=/path to start
ExecStop=/path to stop
RemainAfterExit=yes

This works fine "normally".

However - when I do a "yum update; and reboot"  my script detects a kernel
change and now does a number of "recompiling" steps for drivers and such
before starting my application. Somewhere along the way that just stops.
I'm half way into recompiling those drivers and it just stops.

Is there something else I need in the service file ?

Thanks

Jerry
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


[CentOS] persistent generic device for tape changer

2019-02-07 Thread Helmut Drodofsky
Hello,

mtx and therefor amanda use generic device /dev/sg for tape changer.

These devices change on reboot.

How to make them persistent?

/dev/sch0 and /dev/sch1 seem to be persistent.

/dev/tape/by-id/ shows links from WWID to generic device

An UDEV rule could help? I have not found any example.


-- 
Viele Grüße
Helmut Drodofsky

Internet XS Service GmbH
Heßbrühlstraße 15
70565 Stuttgart

Geschäftsführung
Helmut Drodofsky
HRB 21091 Stuttgart
USt.ID: DE190582774
Fon: 0711 781941 0 
Fax: 0711 781941 79
Mail: i...@internet-xs.de
www.internet-xs.de
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos