Discuss May 2008

discuss@lists.centos.org

268 participants
281 discussions

read only root file system
by Fred Noz 26 May '08

26 May '08

On Saturday 24 May 2008 12:05:30 Fred Noz wrote: > Responding to a question posted earlier this month, Centos 5.1 > includes configuration files for enabling the read-only root > filesystem. Actually, all filesystems can be mounted read-only with > particular files and directories mounted on a read-write tmpfs (in > RAM). This capability comes directly from the upstream provider. > When your computer comes back up, the root and any other system > partitions will be mounted read-only. All the files and directories > listed in /etc/rwtab will be mounted read-write on a tmpfs filesystem. > You can add additional files and directories to rwtab to make them > writable after reboot. > > Note that this system is stateless. When you reboot again, everything > written to the tmpfs filesystem vanishes and the system will be > exactly as it was the last time it was booted. You could add a > writable filesystem on disk or NFS for writing files you want to > retain after rebooting. This is very interesting. Thanks for the sharing Fred. So, it's somekind of Live CD on a disk? I can't think of a practical benefit of using such system, is it to protect it from unwanted modification? Fajar Priyanto | Reg'd Linux User #327841 | Linux tutorial ----- Fajar, There are many practical reasons why one would want to run a Linux system, whether it be desktop or server, with a read-only root. One reason is for ease of maintenance, especially when there are many systems to maintain. You might be administering computers in a classroom, internet access point, or library and you want to be certain that after reboot, the system is exactly as it was the last time it was rebooted, even if the users mess with the system accidentally or on purpose. For example, if a user fills up the /tmp filesystem and causes the system to crash, after booting, the system will have an empty /tmp filesystem. It will not require that fsck to be run because the other filesystems were mounted read-only. This implies no risk of filesystem corruption (except due to physical failures on the disk). Not needing fsck saves time on boot. You could use read-only root on embedded systems where there is no way an administrator could get to the system to fix it. Read-only root is beneficial on a system running on flash media because this avoids having recurring writes wear out some sectors on the media. This is a practical way to run a large group of diskless systems. A single read-only root filesystem can be made available on a network from an NFS server. Many diskless clients can use this readonly-root simultaneously. Of course, this is a way to implement a live CD. In addition to easy maintenance, readonly-root adds a layer of security. The security is broken if someone gains access to the root user, but then many security protections are lost if someone gains root. Even a Database server can benefit from being run on read-only root. The data disk would certainly be mounted read-write, but there is no reason why the operating system and database application software need to be on disks mounted read-write. When an administrator wants to perform an update, upgrade, software, installation. or other system change, the administrator sets the readonly filesystems to read-write using a simple mount command. After the administrator finishes making the changes, a simple mount command (or reboot) sets the readonly filesystems back to read-only. Of course, on systems where the root and system filesystems have no physical write capability, such as on a live CD, they cannot be set to read-write. - Fred --------- Fred Noz Fred(a)Noz.net

5 7

Chip set support
by John Bowden 26 May '08

26 May '08

Hi folks. I,m thinking of purchasing an ASUS mother board with this chip set in it. NVIDIA® nForce® 430 MCP Lan= NVIDIA® nForce® 430 MCP built-in Gigabit MAC with external Attansic PHY. Any one know how well the chip set is supported. Any comments? Thanks John -- Guy Fawkes, the only man to enter the houses of Parliament with honest intentions, (he was going to blow them up!) Registered Linux user number 414240

2 2

COBOL
by Michael 26 May '08

26 May '08

Just curious, maybe some old timers could help me out. I am working with a company that is migrating 20 years of Mainframe Software Development to Unix, HPUX. How much harder would it be to go to Linux, Centos Linux? Also, anyone have any experience with Fujitsu Cobol on Centos? The Fujitsu people only support Red Hat, and said I'd be on my own with Centos. In other words if it works, then I don't care about Fujitsu support. I know some of you are thinking, did someone say "COBOL"? Nobody uses COBOL anymore! If so, let me say "You are wrong". Many large corporations are taking their old business logic that was written in COBOL decades ago, and moving it to new modern platforms, like Linux. Programatically giving these applications a GUI face-lift, while maintaining their original business logic. I know because many companies pay me to do just that. I have a client that wants to use Centos Linux with Fujistu Cobol, and Fujitsu says it's gotta be Red Hat, any help will much appreciated. Thanks, -- Michael Anderson, J3k Solutions Sr.Systems Programmer/Analyst 832.515.3868

14 14

RAID5 or RAID50 for database?
by mcclnx mcc 26 May '08

26 May '08

we have DELL 6800 server with 12 internal disks in it. O.S. is CENTOS 4.6 and SCSI control card is PERC 4e/di. We plan to configure 4 disks (5,8,9,10) as RAID5 or RAID50. This logical volume will be use as file systems and store database backup files. Can anyone tell me which one is better on performance? Thanks. 付費才容量無上限？Yahoo!奇摩電子信箱2.0免費給你，信件永遠不必刪！ - 馬上體驗！

14 36

I/O statistics per PID
by Sergio Belkin 26 May '08

26 May '08

Hi, I've found a great tool called pidstat which is able to report I/O disks statistic. But, it's only for kernels 2.6.20 and later only, is there any tool for Centos xen kernel? Thanks in advance! -- -- Open Kairos http://www.openkairos.com Watch More TV http://sebelk.blogspot.com Sergio Belkin -

2 1

1333/8GB Intel motherboard for C5.1
by Drew Weaver 26 May '08

26 May '08

Hi there, has anyone run into any Desktop/Workstation Intel brand motherboards that work with CentOS 5.1 (4.6/3.9 out of box compatibility is a very large plus) and work with the 1333MHZ cpus such as the 8400/9450 and accept 8GB of RAM? The closest we've found so far is the DG31PR which is alright but it has the limitation of 4GB of RAM and an unsupported Realtek NIC. The DQ35JO is also ok, but requires quite a bit of 'jostling' to get to work such as pci=nommconf and other tweaks, we need something that will work out of box, anyone found anything recently? Thanks in advance if anyone has any hints. -Drew

10 15

how to debug ssh slow connection issues.
by Jason Pyeron 26 May '08

26 May '08

I do not have any ideas on this. Where should I start. [root(a)192.168.1.80 security]# date && time ssh -v 192.168.1.21 date Fri May 23 11:43:53 EDT 2008 OpenSSH_3.9p1, OpenSSL 0.9.7a Feb 19 2003 debug1: Reading configuration data /root/.ssh/config debug1: Applying options for 192.168.1.21 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to 192.168.1.21 [192.168.1.21] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /root/.ssh/identity type -1 debug1: identity file /root/.ssh/id_rsa type -1 debug1: identity file /root/.ssh/id_dsa type 2 debug1: Remote protocol version 1.99, remote software version OpenSSH_4.6 debug1: match: OpenSSH_4.6 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_3.9p1 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host '192.168.1.21' is known and matches the RSA host key. debug1: Found key in /root/.ssh/known_hosts:4 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received Paused 9 seconds. debug1: Authentications that can continue: publickey,password debug1: Next authentication method: publickey debug1: Trying private key: /root/.ssh/identity debug1: Trying private key: /root/.ssh/id_rsa debug1: Offering public key: /root/.ssh/id_dsa debug1: Server accepts key: pkalg ssh-dss blen 433 debug1: read PEM private key done: type DSA Paused 9 seconds. debug1: Authentication succeeded (publickey). debug1: channel 0: new [client-session] debug1: Entering interactive session. Paused 16 seconds. debug1: Sending command: echo debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 debug1: channel 0: free: client-session, nchannels 1 debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 13.5 seconds debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0 debug1: Exit status 0 real 0m34.027s user 0m0.014s sys 0m0.083s Fri May 23 11:51:32 EDT 2008 [root@statics31 security]# And the log from 192.168.1.21 (different run so the dates won't match): ==> /var/log/secure <== May 23 12:01:56 192.168.1.21 pam_stack[23836]: called for "PAM_ACCOUNT" May 23 12:01:56 192.168.1.21 pam_stack[23836]: called from "sshd" May 23 12:01:56 192.168.1.21 pam_stack[23836]: initializing May 23 12:01:56 192.168.1.21 pam_stack[23836]: creating child stack `system-auth' May 23 12:01:56 192.168.1.21 pam_stack[23836]: creating environment May 23 12:01:56 192.168.1.21 pam_stack[23836]: NOT passing PAM_AUTHTOK to child: source is NULL May 23 12:01:56 192.168.1.21 pam_stack[23836]: passing PAM_CONV to child May 23 12:01:56 192.168.1.21 pam_stack[23836]: NOT passing PAM_FAIL_DELAY to child: source not set May 23 12:01:56 192.168.1.21 pam_stack[23836]: NOT passing PAM_OLDAUTHTOK to child: source is NULL May 23 12:01:56 192.168.1.21 pam_stack[23836]: passing PAM_RHOST to child May 23 12:01:56 192.168.1.21 pam_stack[23836]: NOT passing PAM_RUSER to child: source is NULL May 23 12:01:56 192.168.1.21 pam_stack[23836]: passing PAM_SERVICE to child May 23 12:01:56 192.168.1.21 pam_stack[23836]: passing PAM_TTY to child May 23 12:01:56 192.168.1.21 pam_stack[23836]: passing PAM_USER to child May 23 12:01:56 192.168.1.21 pam_stack[23836]: NOT passing PAM_USER_PROMPT to child: source is NULL May 23 12:01:56 192.168.1.21 pam_stack[23836]: passing data to child May 23 12:01:56 192.168.1.21 pam_stack[23836]: calling substack May 23 12:01:56 192.168.1.21 pam_stack[23836]: substack returned 0 (Success) May 23 12:01:56 192.168.1.21 pam_stack[23836]: NOT passing PAM_AUTHTOK to parent: source is NULL May 23 12:01:56 192.168.1.21 pam_stack[23836]: passing PAM_CONV to parent May 23 12:01:56 192.168.1.21 pam_stack[23836]: NOT passing PAM_FAIL_DELAY to parent: source not set May 23 12:01:56 192.168.1.21 pam_stack[23836]: NOT passing PAM_OLDAUTHTOK to parent: source is NULL May 23 12:01:56 192.168.1.21 pam_stack[23836]: passing PAM_RHOST to parent May 23 12:01:56 192.168.1.21 pam_stack[23836]: NOT passing PAM_RUSER to parent: source is NULL May 23 12:01:56 192.168.1.21 pam_stack[23836]: passing PAM_SERVICE to parent May 23 12:01:56 192.168.1.21 pam_stack[23836]: passing PAM_TTY to parent May 23 12:01:56 192.168.1.21 pam_stack[23836]: passing PAM_USER to parent May 23 12:01:56 192.168.1.21 pam_stack[23836]: NOT passing PAM_USER_PROMPT to parent: source is NULL May 23 12:01:56 192.168.1.21 pam_stack[23836]: passing data back May 23 12:01:56 192.168.1.21 pam_stack[23836]: passing former back May 23 12:01:56 192.168.1.21 pam_stack[23836]: returning 0 (Success) May 23 12:01:56 192.168.1.21 pam_stack[23844]: called for "PAM_OPEN_SESSION" May 23 12:01:56 192.168.1.21 pam_stack[23844]: called from "sshd" May 23 12:01:56 192.168.1.21 pam_stack[23844]: initializing May 23 12:01:56 192.168.1.21 pam_stack[23844]: found previously-used child stack `system-auth' May 23 12:01:56 192.168.1.21 pam_stack[23844]: NOT passing PAM_AUTHTOK to child: source is NULL May 23 12:01:56 192.168.1.21 pam_stack[23844]: passing PAM_CONV to child May 23 12:01:56 192.168.1.21 pam_stack[23844]: NOT passing PAM_FAIL_DELAY to child: source not set May 23 12:01:56 192.168.1.21 pam_stack[23844]: NOT passing PAM_OLDAUTHTOK to child: source is NULL May 23 12:01:56 192.168.1.21 pam_stack[23844]: passing PAM_RHOST to child May 23 12:01:56 192.168.1.21 pam_stack[23844]: NOT passing PAM_RUSER to child: source is NULL May 23 12:01:56 192.168.1.21 pam_stack[23844]: passing PAM_SERVICE to child May 23 12:01:56 192.168.1.21 pam_stack[23844]: passing PAM_TTY to child May 23 12:01:56 192.168.1.21 pam_stack[23844]: passing PAM_USER to child May 23 12:01:56 192.168.1.21 pam_stack[23844]: NOT passing PAM_USER_PROMPT to child: source is NULL May 23 12:01:56 192.168.1.21 pam_stack[23844]: passing data to child May 23 12:01:56 192.168.1.21 pam_stack[23844]: calling substack May 23 12:01:56 192.168.1.21 pam_stack[23844]: substack returned 0 (Success) May 23 12:01:56 192.168.1.21 pam_stack[23844]: NOT passing PAM_AUTHTOK to parent: source is NULL May 23 12:01:56 192.168.1.21 pam_stack[23844]: passing PAM_CONV to parent May 23 12:01:56 192.168.1.21 pam_stack[23844]: NOT passing PAM_FAIL_DELAY to parent: source not set May 23 12:01:56 192.168.1.21 pam_stack[23844]: NOT passing PAM_OLDAUTHTOK to parent: source is NULL May 23 12:01:56 192.168.1.21 pam_stack[23844]: passing PAM_RHOST to parent May 23 12:01:56 192.168.1.21 pam_stack[23844]: NOT passing PAM_RUSER to parent: source is NULL May 23 12:01:56 192.168.1.21 pam_stack[23844]: passing PAM_SERVICE to parent May 23 12:01:56 192.168.1.21 pam_stack[23844]: passing PAM_TTY to parent May 23 12:01:56 192.168.1.21 pam_stack[23844]: passing PAM_USER to parent May 23 12:01:56 192.168.1.21 pam_stack[23844]: NOT passing PAM_USER_PROMPT to parent: source is NULL May 23 12:01:56 192.168.1.21 pam_stack[23844]: passing data back May 23 12:01:56 192.168.1.21 pam_stack[23844]: passing former back May 23 12:01:56 192.168.1.21 pam_stack[23844]: returning 0 (Success) ==> /var/log/messages <== May 23 12:01:56 192.168.1.21 sshd[23836]: Accepted publickey for root from 192.168.1.80 port 39910 ssh2 May 23 12:01:56 192.168.1.21 sshd(pam_unix)[23844]: session opened for user root by (uid=0) ==> /var/log/secure <== May 23 12:02:01 192.168.1.21 pam_stack[23844]: called for "PAM_SETCRED" May 23 12:02:01 192.168.1.21 pam_stack[23844]: called from "sshd" May 23 12:02:01 192.168.1.21 pam_stack[23844]: initializing May 23 12:02:01 192.168.1.21 pam_stack[23844]: found previously-used child stack `system-auth' May 23 12:02:01 192.168.1.21 pam_stack[23844]: NOT passing PAM_AUTHTOK to child: source is NULL May 23 12:02:01 192.168.1.21 pam_stack[23844]: passing PAM_CONV to child May 23 12:02:01 192.168.1.21 pam_stack[23844]: NOT passing PAM_FAIL_DELAY to child: source not set May 23 12:02:01 192.168.1.21 pam_stack[23844]: NOT passing PAM_OLDAUTHTOK to child: source is NULL May 23 12:02:01 192.168.1.21 pam_stack[23844]: passing PAM_RHOST to child May 23 12:02:01 192.168.1.21 pam_stack[23844]: NOT passing PAM_RUSER to child: source is NULL May 23 12:02:01 192.168.1.21 pam_stack[23844]: passing PAM_SERVICE to child May 23 12:02:01 192.168.1.21 pam_stack[23844]: passing PAM_TTY to child May 23 12:02:01 192.168.1.21 pam_stack[23844]: passing PAM_USER to child May 23 12:02:01 192.168.1.21 pam_stack[23844]: NOT passing PAM_USER_PROMPT to child: source is NULL May 23 12:02:01 192.168.1.21 pam_stack[23844]: passing data to child May 23 12:02:01 192.168.1.21 pam_stack[23844]: calling substack May 23 12:02:01 192.168.1.21 pam_stack[23844]: substack returned 0 (Success) May 23 12:02:01 192.168.1.21 pam_stack[23844]: NOT passing PAM_AUTHTOK to parent: source is NULL May 23 12:02:01 192.168.1.21 pam_stack[23844]: passing PAM_CONV to parent May 23 12:02:01 192.168.1.21 pam_stack[23844]: NOT passing PAM_FAIL_DELAY to parent: source not set May 23 12:02:01 192.168.1.21 pam_stack[23844]: NOT passing PAM_OLDAUTHTOK to parent: source is NULL May 23 12:02:01 192.168.1.21 pam_stack[23844]: passing PAM_RHOST to parent May 23 12:02:01 192.168.1.21 pam_stack[23844]: NOT passing PAM_RUSER to parent: source is NULL May 23 12:02:01 192.168.1.21 pam_stack[23844]: passing PAM_SERVICE to parent May 23 12:02:01 192.168.1.21 pam_stack[23844]: passing PAM_TTY to parent May 23 12:02:01 192.168.1.21 pam_stack[23844]: passing PAM_USER to parent May 23 12:02:01 192.168.1.21 pam_stack[23844]: NOT passing PAM_USER_PROMPT to parent: source is NULL May 23 12:02:01 192.168.1.21 pam_stack[23844]: passing data back May 23 12:02:01 192.168.1.21 pam_stack[23844]: passing former back May 23 12:02:01 192.168.1.21 pam_stack[23844]: returning 0 (Success) ==> /var/log/messages <== May 23 12:02:16 192.168.1.21 sshd[23844]: error: channel 0: chan_read_failed for istate 3 ==> /var/log/secure <== May 23 12:02:16 192.168.1.21 pam_stack[23844]: called for "PAM_SETCRED" May 23 12:02:16 192.168.1.21 pam_stack[23844]: called from "sshd" May 23 12:02:16 192.168.1.21 pam_stack[23844]: initializing May 23 12:02:16 192.168.1.21 pam_stack[23844]: found previously-used child stack `system-auth' May 23 12:02:16 192.168.1.21 pam_stack[23844]: NOT passing PAM_AUTHTOK to child: source is NULL May 23 12:02:16 192.168.1.21 pam_stack[23844]: passing PAM_CONV to child May 23 12:02:16 192.168.1.21 pam_stack[23844]: NOT passing PAM_FAIL_DELAY to child: source not set May 23 12:02:16 192.168.1.21 pam_stack[23844]: NOT passing PAM_OLDAUTHTOK to child: source is NULL May 23 12:02:16 192.168.1.21 pam_stack[23844]: passing PAM_RHOST to child May 23 12:02:16 192.168.1.21 pam_stack[23844]: NOT passing PAM_RUSER to child: source is NULL May 23 12:02:16 192.168.1.21 pam_stack[23844]: passing PAM_SERVICE to child May 23 12:02:16 192.168.1.21 pam_stack[23844]: passing PAM_TTY to child May 23 12:02:16 192.168.1.21 pam_stack[23844]: passing PAM_USER to child May 23 12:02:16 192.168.1.21 pam_stack[23844]: NOT passing PAM_USER_PROMPT to child: source is NULL May 23 12:02:16 192.168.1.21 pam_stack[23844]: passing data to child May 23 12:02:16 192.168.1.21 pam_stack[23844]: calling substack May 23 12:02:16 192.168.1.21 pam_stack[23844]: substack returned 0 (Success) May 23 12:02:16 192.168.1.21 pam_stack[23844]: NOT passing PAM_AUTHTOK to parent: source is NULL May 23 12:02:16 192.168.1.21 pam_stack[23844]: passing PAM_CONV to parent May 23 12:02:16 192.168.1.21 pam_stack[23844]: NOT passing PAM_FAIL_DELAY to parent: source not set May 23 12:02:16 192.168.1.21 pam_stack[23844]: NOT passing PAM_OLDAUTHTOK to parent: source is NULL May 23 12:02:16 192.168.1.21 pam_stack[23844]: passing PAM_RHOST to parent May 23 12:02:16 192.168.1.21 pam_stack[23844]: NOT passing PAM_RUSER to parent: source is NULL May 23 12:02:16 192.168.1.21 pam_stack[23844]: passing PAM_SERVICE to parent May 23 12:02:16 192.168.1.21 pam_stack[23844]: passing PAM_TTY to parent May 23 12:02:16 192.168.1.21 pam_stack[23844]: passing PAM_USER to parent May 23 12:02:16 192.168.1.21 pam_stack[23844]: NOT passing PAM_USER_PROMPT to parent: source is NULL May 23 12:02:16 192.168.1.21 pam_stack[23844]: passing data back May 23 12:02:16 192.168.1.21 pam_stack[23844]: passing former back May 23 12:02:16 192.168.1.21 pam_stack[23844]: returning 0 (Success) May 23 12:02:21 192.168.1.21 pam_stack[23844]: called for "PAM_CLOSE_SESSION" May 23 12:02:21 192.168.1.21 pam_stack[23844]: called from "sshd" May 23 12:02:21 192.168.1.21 pam_stack[23844]: initializing May 23 12:02:21 192.168.1.21 pam_stack[23844]: found previously-used child stack `system-auth' May 23 12:02:21 192.168.1.21 pam_stack[23844]: NOT passing PAM_AUTHTOK to child: source is NULL May 23 12:02:21 192.168.1.21 pam_stack[23844]: passing PAM_CONV to child May 23 12:02:21 192.168.1.21 pam_stack[23844]: NOT passing PAM_FAIL_DELAY to child: source not set May 23 12:02:21 192.168.1.21 pam_stack[23844]: NOT passing PAM_OLDAUTHTOK to child: source is NULL May 23 12:02:21 192.168.1.21 pam_stack[23844]: passing PAM_RHOST to child May 23 12:02:21 192.168.1.21 pam_stack[23844]: NOT passing PAM_RUSER to child: source is NULL May 23 12:02:21 192.168.1.21 pam_stack[23844]: passing PAM_SERVICE to child May 23 12:02:21 192.168.1.21 pam_stack[23844]: passing PAM_TTY to child May 23 12:02:21 192.168.1.21 pam_stack[23844]: passing PAM_USER to child May 23 12:02:21 192.168.1.21 pam_stack[23844]: NOT passing PAM_USER_PROMPT to child: source is NULL May 23 12:02:21 192.168.1.21 pam_stack[23844]: passing data to child May 23 12:02:21 192.168.1.21 pam_stack[23844]: calling substack May 23 12:02:21 192.168.1.21 pam_stack[23844]: substack returned 0 (Success) May 23 12:02:21 192.168.1.21 pam_stack[23844]: NOT passing PAM_AUTHTOK to parent: source is NULL May 23 12:02:21 192.168.1.21 pam_stack[23844]: passing PAM_CONV to parent May 23 12:02:21 192.168.1.21 pam_stack[23844]: NOT passing PAM_FAIL_DELAY to parent: source not set May 23 12:02:21 192.168.1.21 pam_stack[23844]: NOT passing PAM_OLDAUTHTOK to parent: source is NULL May 23 12:02:21 192.168.1.21 pam_stack[23844]: passing PAM_RHOST to parent May 23 12:02:21 192.168.1.21 pam_stack[23844]: NOT passing PAM_RUSER to parent: source is NULL May 23 12:02:21 192.168.1.21 pam_stack[23844]: passing PAM_SERVICE to parent May 23 12:02:21 192.168.1.21 pam_stack[23844]: passing PAM_TTY to parent May 23 12:02:21 192.168.1.21 pam_stack[23844]: passing PAM_USER to parent May 23 12:02:21 192.168.1.21 pam_stack[23844]: NOT passing PAM_USER_PROMPT to parent: source is NULL May 23 12:02:21 192.168.1.21 pam_stack[23844]: passing data back May 23 12:02:21 192.168.1.21 pam_stack[23844]: passing former back May 23 12:02:21 192.168.1.21 pam_stack[23844]: returning 0 (Success) ==> /var/log/messages <== May 23 12:02:16 192.168.1.21 last message repeated 2 times May 23 12:02:21 192.168.1.21 sshd(pam_unix)[23844]: session closed for user root -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100 - - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, purge the message from your system and notify the sender immediately. Any other use of the email by you is prohibited.

4 14

cups causing segfault
by Gregory P. Ennis 26 May '08

26 May '08

Everyone, I have a new installation of Centos 5.1 that I am using on a gateway server that also has dhcp, named servers. I also have cups set up to function as a print server, and sendmail is being used as a relay to our mail server. yum-cron appears to be updating everything daily as desired. This Centos 5.1 gateway was created to replace a Fedora Core 5 system with the same functions. When I set up cups I copied the FC5 subdirectory into the Centos 5.1 system. Everything appears to work as expected. For some reason I am having sendmail crator without giving me a notice in the logs as far as I can determine. However, when I looked at the messages logs I found it filled with many entries in the form of : kernel: ipp[24519]: segfault at 0000000000000000 rip 00002aaaabf2abc0 rsp 00007fff25495348 error 4 I've done a google search and there appeared to be a problem with doubled printer entries in the printer.conf causing the log entry, but after checking my printer.conf file everything appears to be ok. This file also worked on FC5 without a problem. I am not sure if the cups problem is related to the sendmail problem. Any ideas? Greg Ennis

2 6

RE: [CentOS] Hourly restart
by Gregg McClintic 25 May '08

25 May '08

To be honest I have no idea what is needed by the kernel for the bios to beable to check that the os is responding correctly. I enabled it on a test server and had the same issue on a default 4.6 cent install. I could have the name in the bios (the service ) incorrect ie, watch guard,watch dog , watch "something" I know it is psent on serval types of motherboad manufactures. Take a look should be easy to find

2 1

Opinions about SSH and DNS
by Clint Dilks 25 May '08

25 May '08

Hi People, As part of securing SSH we currently have UseDNS set to yes. But we are finding that a number of ISP's are deliberately refusing to configure matching forward and reverse DNS records. So I am wondering how many of you are still using this option?

2 1

← Newer
1
...
5
6
7
8
9
10
11
...
29
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss May 2008