Re: [CentOS] Script to monitor websites and generate RSS feed when they change

[Vanhorn, Mike]

I just read an article (part of which is here 
http://www.linuxpromagazine.com/Issues/2020/230/The-sys-admin-s-daily-grind-urlwatch/(language)/eng-US
 ) about urlwatch.

---
Mike VanHorn
Senior Computer Systems Administrator
College of Engineering and Computer Science
Wright State University
265 Russ Engineering Center
937-775-5157
michael.vanh...@wright.edu

On 2/24/20, 7:55 PM, "CentOS on behalf of H"  wrote:

Looking for the above. I have found sites where you can register the sites 
you are interested in - as well as yourself - but I would rather run something 
myself on my server to monitor websites etc which do not have RSS-feeds.

Does anyone use something like this?

___
CentOS mailing list
CentOS@centos.org

https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.centos.org_mailman_listinfo_centos=DwICAg=3buyMx9JlH1z22L_G5pM28wz_Ru6WjhVHwo-vpeS0Gk=_s0N94AIK4hLWzZ1WmAPvZjr8bPWpBPPuhyNjJkGAHs=Psh0wPchS71VwyqP7XQS5JgxmMhjbSmNtrO7A3seEq8=EbjhNzuWZGSbUccCjf6s15NZQjplXkVmIHsayUqDXF0=
 


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

Re: [CentOS] /boot partition too small

[Vanhorn, Mike]

If there are many old kernels in there, you can probably remove the oldest 
one(s) to make room for newer ones.

I've run into problems where the yum update didn't work because there wasn't 
enough room in /boot; my notes for updating now include removing old kernels 
first before running updates.

---
Mike VanHorn
Senior Computer Systems Administrator
College of Engineering and Computer Science
Wright State University
265 Russ Engineering Center
937-775-5157
michael.vanh...@wright.edu

On 10/10/17, 9:55 AM, "CentOS on behalf of KM"  wrote:

First off - let me say I am not an administrator.   I need to know if there is 
an easy way to increase my /boot partition.  When I installed CentOS 6 after 
running 5, it was my oversight not to increase the /boot size.  it's too small 
and I can't do yum updates.
if it's not easy to actually increase it, is it safe to take a chunk in my root 
filesystem (like /new.boot or something) and just mount it as /boot from now on 
so it uses the space or is that not a good idea?  I am sure I could easily copy 
the rpms/kernel stuff over to it and then unmounts the real /boot and mount 
this new area as /boot.
Can you administrators let me know what you think of all this?   Thanks in 
advance.
KM
___
CentOS mailing list
CentOS@centos.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.centos.org_mailman_listinfo_centos=DwIGaQ=3buyMx9JlH1z22L_G5pM28wz_Ru6WjhVHwo-vpeS0Gk=_s0N94AIK4hLWzZ1WmAPvZjr8bPWpBPPuhyNjJkGAHs=oiG0zd3adnkmuJP8BRsykJqAVPEQ_hXcq80Jj-Bfl_c=hg7Ww_cslaLQa4jGDLcy3NhAmURSXvBOW3LXB3JXCuc=
 


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

Re: [CentOS] weird SELinux denial

[Vanhorn, Mike]

On 6/6/17, 1:48 PM, "Daniel Walsh"  wrote:

>Ok, that works then.  The way I read your email indicated that setting 
>the boolean did not allow the access.  I take it you are not running 
>with NIS/Yellow pages and yet you see dbus connecting to port 111?

Well, previously, I didn’t have to set it, because it already was set, but the 
denial was still happening (apparently). NIS has been working, which makes it 
even more confusing.

But, now that I unset it (set it to 0) and then set it back (to 1), now 
allow2why seems to understand that the boolean is set (whereas before it seemed 
to think that the boolean was not set), so I guess I’ll what the log and see 
what happens.

Thanks!

---
Mike VanHorn
Senior Computer Systems Administrator
College of Engineering and Computer Science
Wright State University
265 Russ Engineering Center
937-775-5157
michael.vanh...@wright.edu



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

Re: [CentOS] weird SELinux denial

[Vanhorn, Mike]

On 6/6/17, 12:38 PM, "Daniel Walsh"  wrote:

>I am asking if you run it again, does it change.  If the boolean is set 
>the audit2why should say that the AVC is allowed.

Well, if I just run audit2why again, it always tells me the same thing. 
However, I have now discovered that if I unset allow_ypbind, and then reset it 
to 1, audit2why then says 

type=AVC msg=audit(1496768649.872:1338): avc:  denied  { name_connect } for  
pid=2413 comm="dbus-daemon" dest=111 
scontext=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 
tcontext=system_u:object_r:portmap_port_t:s0 tclass=tcp_socket

Was caused by:
Unknown - would be allowed by active policy
Possible mismatch between this policy and the one under which 
the audit message was generated.

Possible mismatch between current in-memory boolean settings 
vs. permanent ones.


---
Mike VanHorn
Senior Computer Systems Administrator
College of Engineering and Computer Science
Wright State University
265 Russ Engineering Center
937-775-5157
michael.vanh...@wright.edu


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

Re: [CentOS] weird SELinux denial

[Vanhorn, Mike]

It says what it is my original post; that’s the output from audit2allow –w 
(which is audit2why):

Was caused by:
The boolean allow_ypbind was set incorrectly. 
Description:
Allow system to run with NIS

Allow access by executing:
# setsebool -P allow_ypbind 1

---
Mike VanHorn
Senior Computer Systems Administrator
College of Engineering and Computer Science
Wright State University
265 Russ Engineering Center
937-775-5157
michael.vanh...@wright.edu

On 6/6/17, 9:29 AM, "Daniel Walsh"  wrote:

If you run this avc though audit2why what does it say?



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

[CentOS] weird SELinux denial

[Vanhorn, Mike]

I keep seeing this in my audit.logs:

type=AVC msg=audit(1496336600.230:6): avc:  denied  { name_connect } for  
pid=2411 comm="dbus-daemon" dest=111 
scontext=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 
tcontext=system_u:object_r:portmap_port_t:s0 tclass=tcp_socket

Was caused by:
The boolean allow_ypbind was set incorrectly.
Description:
Allow system to run with NIS

Allow access by executing:
# setsebool -P allow_ypbind 1


The weirdness is that when I check allow_ypbind, it’s already on:

 # getsebool allow_ypbind
allow_ypbind --> on
#


Does anyone with more experience with SELinux than me have any idea why this is 
happening?

---
Mike VanHorn
Senior Computer Systems Administrator
College of Engineering and Computer Science
Wright State University
265 Russ Engineering Center
937-775-5157
michael.vanh...@wright.edu

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

Re: [CentOS] Best practices for copying lots of files machine-to-machine

[Vanhorn, Mike]

On 5/17/17, 5:27 PM, "CentOS on behalf of m.r...@5-cent.us" 
 wrote:

>Why? I just rsync'd 159G in less than one workday from one server to
>another. Admittedly, we allegedly have a 1G network, but

Well, I’ve don’t recall ever having to rsync more than 100G (although I am 
doing multiple rsyncs of about 86G as we speak), and I’ve never been able to do 
it with machines on their own, isolated switch (so my rsync’s are competing 
with everything else on the network), and it’s been a while since I’ve actually 
tried it multiple ways and measured it, but in my experience I’ve never see the 
network outperform the system bus.

---
Mike VanHorn
Senior Computer Systems Administrator
College of Engineering and Computer Science
Wright State University
265 Russ Engineering Center
937-775-5157
michael.vanh...@wright.edu




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

Re: [CentOS] Best practices for copying lots of files machine-to-machine

[Vanhorn, Mike]

On 5/17/17, 12:03 PM, "CentOS on behalf of ken"  wrote:

>An entire filesystem (~180g) needs to be copied from one local linux 
>machine to another.  Since both systems are on the same local subnet, 
>there's no need for encryption.
>
>I've done this sort of thing before a few times in the past in different 
>ways, but wanted to get input from others on what's worked best for them.

If shutting the machines down is feasible, I’d put the source hard drive into 
the destination machine and use rsync to copy it from one drive to the other 
(rather than using rsync to copy from one machine to the other over the 
network).

---
Mike VanHorn
Senior Computer Systems Administrator
College of Engineering and Computer Science
Wright State University
265 Russ Engineering Center
937-775-5157
michael.vanh...@wright.edu


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

Re: [CentOS] can't create printers after upgrading cups

[Vanhorn, Mike]

It looks like this may just be a bug upstream:

 https://access.redhat.com/solutions/3001891

Still trying the work-arounds.

---
Mike VanHorn
Senior Computer Systems Administrator
College of Engineering and Computer Science
Wright State University
265 Russ Engineering Center
937-775-5157
michael.vanh...@wright.edu

On 4/26/17, 9:51 AM, "CentOS on behalf of Vanhorn, Mike" 
<centos-boun...@centos.org on behalf of michael.vanh...@wright.edu> wrote:



After upgrading cups on my CentOS 6 systems from version 1.4.2-72.el6 to 
1.4.2-77.el6, I am no longer able to create working printers, either with 
lpadmin from the command line or with system-config-printer. 



When I try to run lpadmin, I get this simple error:



[root@vlsi66 ~]# lpadmin -p newprinter  -v lpd://printserver/serverqueue-E -P 
/path/to/ppd/thing.ppd

lpadmin: Unknown

[root@vlsi66 ~]#



Sometimes, the printer does get created (i.e. it shows up in the output of 
‘lpstat –a’ and printers.conf gets updated), but sometimes it doesn’t. If the 
printer does get created, then there is no new ppd in /etc/cups/ppd.



If I try to create the printer using system-config-printer, I get an error of 



 CUPS server error (adding printer newprinter) 

 There was an error during the CUPS 

 operation: ‘server-error-service-unavailable’.



I’ve looked at file and directory permissions, and checked that cupsd is, in 
fact, running. There is nothing obvious in the logs, except for this, which 
happens at exactly the time the printer should get created:



localhost - - [26/Apr/2017:09:34:01 -0400] "POST /admin/ HTTP/1.1" 401 0 - -



This also occurs if I access localhost:631 from a web browser; and everything 
works fine up to the point of “Add Printer”, and then the web page shows and 
Error: box with “Unknown” (from the lpadmin command), and the 401 error shows 
up in the log. I can’t figure out why it would be a 401 (unauthorized), since 
everything else worked.



Has anyone else run into this problem, where you can’t create a new printer?



Thanks!



---

Mike VanHorn

Senior Computer Systems Administrator

College of Engineering and Computer Science

Wright State University

265 Russ Engineering Center

937-775-5157

michael.vanh...@wright.edu



___
CentOS mailing list
CentOS@centos.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.centos.org_mailman_listinfo_centos=DwIGaQ=3buyMx9JlH1z22L_G5pM28wz_Ru6WjhVHwo-vpeS0Gk=_s0N94AIK4hLWzZ1WmAPvZjr8bPWpBPPuhyNjJkGAHs=SdBWyK0ralxtI5G1OSzTjeeADs5NVHFWwz8kA03RTbQ=w-TSpjlVJ6DZ0WbO7V2Ji4xvYODo-TGXvpE-YIbjPrY=
 


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

[CentOS] can't create printers after upgrading cups

[Vanhorn, Mike]

After upgrading cups on my CentOS 6 systems from version 1.4.2-72.el6 to 
1.4.2-77.el6, I am no longer able to create working printers, either with 
lpadmin from the command line or with system-config-printer. 

When I try to run lpadmin, I get this simple error:

[root@vlsi66 ~]# lpadmin -p newprinter  -v lpd://printserver/serverqueue-E -P 
/path/to/ppd/thing.ppd
lpadmin: Unknown
[root@vlsi66 ~]#

Sometimes, the printer does get created (i.e. it shows up in the output of 
‘lpstat –a’ and printers.conf gets updated), but sometimes it doesn’t. If the 
printer does get created, then there is no new ppd in /etc/cups/ppd.

If I try to create the printer using system-config-printer, I get an error of 

 CUPS server error (adding printer newprinter) 
 There was an error during the CUPS 
 operation: ‘server-error-service-unavailable’.

I’ve looked at file and directory permissions, and checked that cupsd is, in 
fact, running. There is nothing obvious in the logs, except for this, which 
happens at exactly the time the printer should get created:

localhost - - [26/Apr/2017:09:34:01 -0400] "POST /admin/ HTTP/1.1" 401 0 - -

This also occurs if I access localhost:631 from a web browser; and everything 
works fine up to the point of “Add Printer”, and then the web page shows and 
Error: box with “Unknown” (from the lpadmin command), and the 401 error shows 
up in the log. I can’t figure out why it would be a 401 (unauthorized), since 
everything else worked.

Has anyone else run into this problem, where you can’t create a new printer?

Thanks!

---
Mike VanHorn
Senior Computer Systems Administrator
College of Engineering and Computer Science
Wright State University
265 Russ Engineering Center
937-775-5157
michael.vanh...@wright.edu

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

Re: [CentOS] setting up auto logout in CentOS 6

[Vanhorn, Mike]

>So, I’ve found that if you want to enforce gconf policies for workstations, 
>you need to put them in /etc/gconf/gconf.xml.mandatory. 


I tried using that, and it still doesn’t automatically logout. In face, the 
value I set in gconf.xml.mandatory doesn’t seem to get noticed at all. I set 
them to different values, and ‘gconftool-2 --get’ still shows the default 
values that I set in /etc/gconf/schemas/gnome-session.schemas.

---
Mike VanHorn
Senior Computer Systems Administrator
College of Engineering and Computer Science
Wright State University
265 Russ Engineering Center
937-775-5157
michael.vanh...@wright.edu


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

[CentOS] setting up auto logout in CentOS 6

[Vanhorn, Mike]

I would like to have my lab workstations logout a session after the person has 
been idle for a certain period of time. After some searching on the web, I got 
into 

/etc/gconf/schemas/gnome-session.schemas

and set the default value of max_idle_action to “forced-logout”:

 
  /schemas/desktop/gnome/session/max_idle_action
  /desktop/gnome/session/max_idle_action
  gnome
  string
  forced-logout
  gnome-session-2.0
  
 The action to take after the maximum idle time
 The name of the action to take when the maximum allowed idle 
time has been reached. The Delay is specified in the "max_idle_time" key. 
Allowed values are: logout, forced-logout. An empty string disables the 
action.
  
  

but the system is not logging me out after the max_idle_time. Is there 
something I’m missing?

Thanks!

---
Mike VanHorn
Senior Computer Systems Administrator
College of Engineering and Computer Science
Wright State University
265 Russ Engineering Center
937-775-5157
michael.vanh...@wright.edu

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

Re: [CentOS] Semi-OT: very weird vi behaviour

[Vanhorn, Mike]

On 4/27/16, 9:39 AM, "centos-boun...@centos.org on behalf of
m.r...@5-cent.us"  wrote:

> And now, I just
>ssh'd in from another windows, same way... and the weirdness isn't there.
>
>Anyone have any clues as to what's going on with that one session?
>
> Mark

It sounds as if, for some reason, in that one session, vi doesn’t know
what your terminal settings are, so it’s in line editing mode (like ed or
ex). I don’t have an explanation as to why it would only happen with that
one session, though.

---
Mike VanHorn
Senior Computer Systems Administrator
College of Engineering and Computer Science
Wright State University
265 Russ Engineering Center
937-775-5157
michael.vanh...@wright.edu
http://www.cecs.wright.edu/~mvanhorn/





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

[CentOS] CUPS not generating a printcap file

[Vanhorn, Mike]

According to all of the documentation I can find, an /etc/printcap file
(or whatever filename is specified with the Printcap directive) is
generated by cupsd ever time a printer is added or removed. On all of my
CentOS 6.7 systems, this is NOT happening. I can restart cups and add or
remove printers over and over and it still doesn't generate the printcap
file. 

Is this a known issue, or is there some way that CentOS is blocking this
from happening?

---
Mike VanHorn
Senior Computer Systems Administrator
College of Engineering and Computer Science
Wright State University
265 Russ Engineering Center
937-775-5157
michael.vanh...@wright.edu
http://www.cecs.wright.edu/~mvanhorn/



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

Re: [CentOS] Disable login at boot

[Vanhorn, Mike]

On 5/20/14 9:59 PM, Karalyn Capone kcap...@haivision.com wrote:

Not disable the screen. I just want the machine to log in on boot
automatically.

I think we're all still confused.

If it's going to be headless and remotely administered, why do you want it
to login automatically on the console?

---
Mike VanHorn
Senior Computer Systems Administrator
College of Engineering and Computer Science
Wright State University
265 Russ Engineering Center
937-775-5157
michael.vanh...@wright.edu
http://www.cecs.wright.edu/~mvanhorn/



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

Re: [CentOS] problem configuring grub for a dual-boot

[Vanhorn, Mike]

I tried the suggestion of swapping the disks assignments:

Try telling grub to swap the disks:

  title Windows 7
map (hd1) (hd0)
map (hd0) (hd1)
  rootnoverify (hd1,0)
  chainloader +1

But that still just gets me


 invalid EFI file path
 Error 1: Filename must be either an absolute pathname or blocklist



I think that my failing is something to do with grub and EFI. In the
anaconda-generated  grub.conf file, there is a line that reads

 device (hd0) HD(1,800,64000,9b55c4a9-fdbe-4fcd-857b-8e7e129e29f9)

I have no idea where that UUID came from, as both blkid and ls -l
/dev/disk/by-uuid do not have entries for the disks themselves, just for
the partitions. Maybe that isn't even a UUID. At any rate, I'm wondering
if there should be a similar entry for the other disk in the system.

---
Mike VanHorn
Senior Computer Systems Administrator
College of Engineering and Computer Science
Wright State University
265 Russ Engineering Center
937-775-5157
michael.vanh...@wright.edu
http://www.cecs.wright.edu/~mvanhorn/




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

[CentOS] problem configuring grub for a dual-boot

[Vanhorn, Mike]

I have Windows 7 on /dev/sda and CentOS 6.4 on /dev/sdb. Here are the
layouts:

 (parted) select /dev/sda
 Using /dev/sda (parted) print
   
 Model: ATA WDC WD10EZEX-00Z (scsi)
 Disk /dev/sda: 1000GB
 Sector size (logical/physical): 512B/4096B
 Partition Table: msdos

 Number  Start   End SizeType File system  Flags
 1  1049kB  374MB   373MB   primary  ntfs boot
 2 374MB   1000GB  1000GB  primary  ntfs

 (parted) select /dev/sdb
 Using /dev/sdb
 (parted) print
 Model: ATA ST500DM002-1BD14 (scsi)
 Disk /dev/sdb: 500GB
 Sector size (logical/physical): 512B/4096B
 Partition Table: gpt

 Number  Start   EndSize   File system  Name  Flags
 1  1049kB  211MB  210MB  fat16  boot
 2  211MB   735MB  524MB  ext4
 3  735MB   500GB  499GB lvm

/boot/efi/EFI/redhat/grub.conf looks like this:

 # grub.conf generated by anaconda
 #
 # Note that you do not have to rerun grub after making changes to this
file
 # NOTICE:  You have a /boot partition.  This means that
 #  all kernel and initrd paths are relative to /boot/, eg.
 #  root (hd0,1)
 #  kernel /vmlinuz-version ro root=/dev/mapper/vg_amrl01-lv_root
 #  initrd /initrd-[generic-]version.img
 #boot=/dev/sdb1
 device (hd0) HD(1,800,64000,9b55c4a9-fdbe-4fcd-857b-8e7e129e29f9)
 default=0
 timeout=5
 splashimage=(hd0,1)/grub/splash.xpm.gz
 hiddenmenu
 title CentOS 6 (2.6.32-358.14.1.el6.x86_64)
 root (hd0,1)
 kernel /vmlinuz-2.6.32-358.14.1.el6.x86_64 ro
root=/dev/mapper/vg_amrl01-lv_root rd_NO_LUKS LANG=en_US.UTF-8
rd_LVM_LV=vg_amrl01/lv_swap rd_NO_MD SYSFONT=latarcyrheb-sun16
crashkernel=128M  KEYBOARDTYPE=pc KEYTABLE=us rd_LVM_LV=vg_amrl01/lv_root
rd_NO_DM rhgb quiet
 initrd /initramfs-2.6.32-358.14.1.el6.x86_64.img
 title Windows 7
 rootnoverify (hd1,0)
 chainloader +1
 



The system boots into CentOS just fine, but selecting the Windows 7
entry results in 

 invalid EFI file path
 Error 1: Filename must be either an absolute pathname or blocklist

 Press any key to continue...

By my understanding, since grub is installed on sdb, then sdb becomes hd0
and thus sda would become hd1, and so telling it to boot Windows from
hd1,0 makes sense. Also, since anaconda created the Windows entry during
the CentOS install, I would have expected this to work. However, as it
doesn't work, I'm clearly missing something. Can someome please point me
in the right direction as to why this isn't working?

Thanks!


---
Mike VanHorn
Senior Computer Systems Administrator
College of Engineering and Computer Science
Wright State University
265 Russ Engineering Center
937-775-5157
michael.vanh...@wright.edu
http://www.cecs.wright.edu/~mvanhorn/




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

Re: [CentOS] Disabling user switching in CentOS 6

[Vanhorn, Mike]

On 7/8/13 5:57 PM, James Pearson jame...@moving-picture.com wrote:

We've applied the patch available from
https://bugzilla.gnome.org/show_bug.cgi?id=598255 to the gnome-session
SRPM - which works for us (with the above gconf settings)



Interestingly, I have just done the same thing, but the user switching is
still enabled and functioning.

---
Mike VanHorn
Senior Computer Systems Administrator
College of Engineering and Computer Science
Wright State University
265 Russ Engineering Center
937-775-5157
michael.vanh...@wright.edu
http://www.cecs.wright.edu/~mvanhorn/




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

[CentOS] Disabling user switching in CentOS 6

[Vanhorn, Mike]

Installing CentOS 6 on a lab full of workstations, and I want to disable
fast user switching. With CentOS 5, I simply made sure that the
user_switch_enabled entry in
/etc/gconf/schemas/gnome-screensaver.schemas was set to false. However,
that doesn't work with CentOS 6.

I've found various proposed solutions to this issue, such as

gconftool-2 --direct --config-source
xml:readwrite:/etc/gconf/gconf.xml.mandatory \
--type bool --set /apps/gnome-screensaver/user_switch_enabled false
gconftool-2 --direct --config-source
xml:readwrite:/etc/gconf/gconf.xml.mandatory \
--type bool --set /desktop/gnome/lockdown/disable_user_switching true

neither of which work, either. Does anyone know the proper way to disable
user switching with CentOS 6?

Thanks!


---
Mike VanHorn
Senior Computer Systems Administrator
College of Engineering and Computer Science
Wright State University
265 Russ Engineering Center
937-775-5157
michael.vanh...@wright.edu
http://www.cecs.wright.edu/~mvanhorn/




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

[CentOS] Getting confirmation for power button

[Vanhorn, Mike]

Using CentOS 5.8:

Currently on my workstations, when I press the power button the computer
immediately does a 'shutdown -h now' (per /etc/acpid/events/power.conf).
Is there a way to change it so that a confirmation dialog comes up, rather
than an immediate shutdown?

I assume that I am going to need to change that power.conf file to tell
some program that the power button's been pressed, rather than making a
call to shutdown, but I haven't been able to figure out what program to
which I need to make a call.

Thanks!

---
Mike VanHorn
Senior Computer Systems Administrator
College of Engineering and Computer Science
Wright State University
265 Russ Engineering Center
937-775-5157
michael.vanh...@wright.edu
http://www.cecs.wright.edu/~mvanhorn/




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

Re: [CentOS] Getting confirmation for power button

[Vanhorn, Mike]

On 4/25/13 9:46 AM, Giles Coochey gi...@coochey.net wrote:

You are talking about something that acpid is doing for you:

http://linux.die.net/man/8/acpid



Yes, I know this is handled by acpid; that's where the
/etc/acpid/events/power.sh file comes in. I'm asking if anyone knows what
changes to make to that file so that it gives a prompt first.

I'm guessing that there is a program out there already that will prompt
for a shutdown, I just don't know what that program is.

---
Mike VanHorn
Senior Computer Systems Administrator
College of Engineering and Computer Science
Wright State University
265 Russ Engineering Center
937-775-5157
michael.vanh...@wright.edu
http://www.cecs.wright.edu/~mvanhorn/




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

Re: [CentOS] Getting confirmation for power button

[Vanhorn, Mike]

On 4/25/13 10:38 AM, John Doe jd...@yahoo.com wrote:

On CentOS 5: /etc/acpi/events/power.conf

Sorry, I meant power.conf in my original post, not power.sh.

Do you use gnome?
If so, in 'System / Preferences / ... / Power Managment', in the
'General' tab,

Yes, and that works fine, *if* the user is logged in. But what about when
the workstation is sitting there at the login window? At that point, when
the action from power.conf is taken, there is no power manager, so it does
the shutdown. 

I'm wanting to get a prompt in that situation, too.

---
Mike VanHorn
Senior Computer Systems Administrator
College of Engineering and Computer Science
Wright State University
265 Russ Engineering Center
937-775-5157
michael.vanh...@wright.edu
http://www.cecs.wright.edu/~mvanhorn/




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

Re: [CentOS] problem with machine freezing for short periods

[Vanhorn, Mike]

On 7/25/12 10:34 AM, Vanhorn, Mike michael.vanh...@wright.edu wrote:


I have two HP dc7800 convertible minitowers that are exhibiting the
following issue: every 5-10 minutes, they will freeze for about 30
seconds, and then pick right back up again. During the freeze, it seems
that nothing at all happens on the system; the clock doesn't even advance
(it just picks up again with the next second, and that 30-or-so seconds
are lost).

I've tried both CentOS 5.8 and 5.7, thinking it was a kernel
incompatibility, but the problem happened with both versions. I have tried
different hard drives, different memory, even swapped the entire machine,
and the problem exists everywhere. I have tried adding pci=nommconf to
the kernel line, as that was reported as being necessary back with 5.2 on
these machines, but that made no difference (and shouldn't be necessary
now, anyway, as I believe the issue has either been fixed or
worked-around).

I am stuck, and can't figure out where to even suspect the problem might
actually be. There are no errors getting logged anywhere that I can find,
probably because everything just stops temporarily, so there's nothing
for the system to log.

Does anyone have any idea where I could look to fix this? I think I am
next going to go back to 5.2, where the pci=nommconf is necessary, because
at least back that far it appears to have been working for other people.
However, I really would like to have this running 5.8.

Thanks!


As a followup, I've determined that it is network related, but I'm still
not sure what the problem is. I did go back to CentOS 5.2, but the problem
still exists with that version, too.

Basically, what seems to be happening is that the network freezes around
30 seconds, and then picks right back up. There are no errors in any logs
that I can find, and process that are running locally and that only depend
on local resources keep right on going and don't have a problem.

I have tried using a different network card (as opposed to the one on the
motherboard), but the problem happens with that, too. It almost has to be
a configuration issue, or a BIOS settting, but I don't get it.

---
Mike VanHorn
Senior Computer Systems Administrator
College of Engineering and Computer Science
Wright State University
265 Russ Engineering Center
937-775-5157
michael.vanh...@wright.edu
http://www.cecs.wright.edu/~mvanhorn/




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

[CentOS] [SOLVED] Re: problem with machine freezing for short periods

[Vanhorn, Mike]

It turned out to be something very simple, but which wasn't obvious to
check to begin with. There was another computer (a Windows machine) that
was supposed to have been taken out of service a long time ago, but
someone has recently put it back on the network. Because it was supposed
to have been no longer used, it's IP address was re-allocated (a year and
a half ago!) to the machine that I have been agonizing over all week.

On someone's suggestion, I decided to put the problem PC on a different
subnet, because we thought it might be something amiss with the new
networking hardware that was installed a month or so ago, and suddenly the
problem went away. Some more investigation, and we discovered that the IP
address was still being used, and, thus, stumbled across the actual
problem.

Thank you to all who responded!

It's always the simplest things, in the last place you look...

---
Mike VanHorn
Senior Computer Systems Administrator
College of Engineering and Computer Science
Wright State University
265 Russ Engineering Center
937-775-5157
michael.vanh...@wright.edu
http://www.cecs.wright.edu/~mvanhorn/




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

Re: [CentOS] problem with machine freezing for short periods

[Vanhorn, Mike]

On 7/25/12 11:24 AM, m.r...@5-cent.us m.r...@5-cent.us wrote:

When you say swapped the entire machine, what did you do?

I have two of them, and thinking it was the hardware on the one, I moved
the hard drive to the second, but the problem existed there, too. That
points to something with the software, but, well, I haven't found anything
yet.

Also, what's
running on them? Have you tried running top -d 10 or smaller (that will
update the screen every 10 secs; I only recently found that current top
allows tenths of a second.

I haven't tried top, but that's a good idea. I usually have one window
open that is running uptime every second in a continuous loop, mainly to
tell me when exactly it happens. Originally, when the problem was first
noticed, we had VLSI software being run on it, but at this point, the only
thing I have on the machine is the operating system, and I'm going through
my step-by-step configuration until I notice the problem occurring.

---
Mike VanHorn
Senior Computer Systems Administrator
College of Engineering and Computer Science
Wright State University
265 Russ Engineering Center
937-775-5157
michael.vanh...@wright.edu
http://www.cecs.wright.edu/~mvanhorn/




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

Re: [CentOS] problem with machine freezing for short periods

[Vanhorn, Mike]

On 7/25/12 12:04 PM, Mogens Kjaer m...@lemo.dk wrote:

I've several HP dc7x00 machines, and I've never seen that problem
with centos 5 or 6.

I do, too. Things are fine on our 7900s, and the 8000-series machines we
have. I'm only seeing it on these two 7800s.

Do you also see the problem if you boot in runlevel 3, i.e. without X?

Yes. I was thinking it maybe had something to do with the graphics card,
so I left it in runlevel 3, but the problem still persisted. It still may
be the graphics card, though, come to think of it, so I may need to try
taking it out.

---
Mike VanHorn
Senior Computer Systems Administrator
College of Engineering and Computer Science
Wright State University
265 Russ Engineering Center
937-775-5157
michael.vanh...@wright.edu
http://www.cecs.wright.edu/~mvanhorn/




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

Re: [CentOS] problem with machine freezing for short periods

[Vanhorn, Mike]

On 7/25/12 12:07 PM, John Doe jd...@yahoo.com wrote:

Do you have the latest BIOS?

Yes.

Did you get a CD to run tests (like Insight Diagnostics Offline)?

Yes, I used my copy of the UBCD to run memory and hard drive diagnostics,
and both passed.

---
Mike VanHorn
Senior Computer Systems Administrator
College of Engineering and Computer Science
Wright State University
265 Russ Engineering Center
937-775-5157
michael.vanh...@wright.edu
http://www.cecs.wright.edu/~mvanhorn/




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

Re: [CentOS] problem with machine freezing for short periods

[Vanhorn, Mike]

On 7/25/12 12:22 PM, Keith Roberts ke...@karsites.net wrote:

Hi Mike. Are you on 32 or 64 bits ?

64. I have thought of trying 32 bit, just to see if it made a difference,
but if it does, that won't help me because we need 64 bits for the
software we're running, anyway.

---
Mike VanHorn
Senior Computer Systems Administrator
College of Engineering and Computer Science
Wright State University
265 Russ Engineering Center
937-775-5157
michael.vanh...@wright.edu
http://www.cecs.wright.edu/~mvanhorn/




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

[CentOS] problem with machine freezing for short periods

[Vanhorn, Mike]

I have two HP dc7800 convertible minitowers that are exhibiting the
following issue: every 5-10 minutes, they will freeze for about 30
seconds, and then pick right back up again. During the freeze, it seems
that nothing at all happens on the system; the clock doesn't even advance
(it just picks up again with the next second, and that 30-or-so seconds
are lost).

I've tried both CentOS 5.8 and 5.7, thinking it was a kernel
incompatibility, but the problem happened with both versions. I have tried
different hard drives, different memory, even swapped the entire machine,
and the problem exists everywhere. I have tried adding pci=nommconf to
the kernel line, as that was reported as being necessary back with 5.2 on
these machines, but that made no difference (and shouldn't be necessary
now, anyway, as I believe the issue has either been fixed or
worked-around).

I am stuck, and can't figure out where to even suspect the problem might
actually be. There are no errors getting logged anywhere that I can find,
probably because everything just stops temporarily, so there's nothing
for the system to log.

Does anyone have any idea where I could look to fix this? I think I am
next going to go back to 5.2, where the pci=nommconf is necessary, because
at least back that far it appears to have been working for other people.
However, I really would like to have this running 5.8.

Thanks!

---
Mike VanHorn
Senior Computer Systems Administrator
College of Engineering and Computer Science
Wright State University
265 Russ Engineering Center
937-775-5157
michael.vanh...@wright.edu
http://www.cecs.wright.edu/~mvanhorn/




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