Discuss

discuss@lists.centos.org

34758 discussions

USBDisk question
by Todd Cary 25 May '08

25 May '08

I have an external USB drive, and when mounted, it was /media/usbdisk. When I recently tried my rsync backup, a usbdisk1 had been created...I guess by the auto-mounting (when the disk is turned on). Is there a way to remove the usbdisk1 and set it up so that the auto-mounting will use usbdisk? Or should I just leave it be? I needed to change my command line for the rsync backup to usbdisk1. Many thanks... Todd -- Ariste Software Petaluma, CA 94952 http://www.toddcary.com/aristephotography/

2 1

resizing partition
by Al Sparks 25 May '08

25 May '08

I'm going to have to resize a partition (shrink it) to make room for more swap space. This is actually not too big of a deal, since we're not talking about a "system" partition (/, /var, /usr, etc), but one where an application resides. So I won't even have to go to "rescue" mode to do this. I can umount this thing live. (and since I'm working on it remotely, that's important). But this system was not configured with LVM. So it occurs to me, that in dealing with a non-LVM partition(s), if the swap space I want to enlarge isn't next to the partition I shrink, my options would be to: 1. Manually "move" the other partitions, probably very risky 2. Simply make a second swap space that's next to the partition I shrink. Have I got the right idea? === Al

2 1

small annoying problem with Ati video driver
by Juan C. Valido 24 May '08

24 May '08

I have a small annoying problem with Ati video driver, when Centos 5.1 starts and gets to the login screen the resolution is too high for my monitor (better than out of range) and it's annoying can I have it start in a lower resolution. Thanks...

2 2

samba question
by david chong 24 May '08

24 May '08

Hi, I am running Centos5.1, trying to configure samba now. I am quite new in this area and hope help from the list. I could not connect to it from a windows xp pc >From the console, I log in and do a >smbclient -L localhost -U% Domain=[MYGROUP] OS=[Unix] Server=[Samba 3.0.25b-0.el5.4] Sharename Type Comment --------- ---- ------- samba Disk IPC$ IPC IPC Service (Samba 3.0.25b-0.el5.4) Domain=[MYGROUP] OS=[Unix] Server=[Samba 3.0.25b-0.el5.4] Server Comment --------- ------- ANTIOCH Samba 3.0.25b-0.el5.4 Workgroup Master --------- ------- MYGROUP ANTIOCH Could you pls help. Thanks David

8 15

CentOS-announce Digest, Vol 39, Issue 12
by centos-announce-request＠centos.org 24 May '08

24 May '08

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2008:0287 Important CentOS 3 ia64 libxslt - security update (Pasi Pirhonen) 2. CESA-2008:0287 Important CentOS 4 ia64 libxslt - security update (Pasi Pirhonen) 3. CESA-2008:0492 Important CentOS 4 ia64 gnutls - security update (Pasi Pirhonen) 4. CESA-2008:0287 Important CentOS 3 s390(x) libxslt - security update (Pasi Pirhonen) 5. CESA-2008:0492 Important CentOS 4 s390(x) gnutls - security update (Pasi Pirhonen) 6. CESA-2008:0287 Important CentOS 4 s390(x) libxslt - security update (Pasi Pirhonen) ---------------------------------------------------------------------- Message: 1 Date: Fri, 23 May 2008 19:19:15 +0300 From: Pasi Pirhonen <upi(a)centos.fi> Subject: [CentOS-announce] CESA-2008:0287 Important CentOS 3 ia64 libxslt - security update To: centos-announce(a)centos.org Message-ID: <20080523161914.GN2456(a)centos.fi> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory 2008:0287 https://rhn.redhat.com/errata/RHSA-2008-0287.html The following updated files have been uploaded and are currently syncing to the mirrors: ia64: updates/ia64/RPMS/libxslt-1.0.33-6.ia64.rpm updates/ia64/RPMS/libxslt-devel-1.0.33-6.ia64.rpm updates/ia64/RPMS/libxslt-python-1.0.33-6.ia64.rpm -- Pasi Pirhonen - upi(a)iki.fi - http://pasi.pirhonen.eu/ Top-postings silently ignored

1 0

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

24 May '08

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. You can have your Centos system running read-only root in two easy steps: 1. Edit /etc/sysconfig/readonly-root and change READONLY=no to READONLY=yes 2. Reboot 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. Take a look at /etc/rc.d/rc.sysinit to see how the magic is done. This capability is a "technology preview" (beta) and is buggy. Note that /etc/mtab and thus "mount" do not show the complete list of filesystems because the /etc directory is on a read-only filesystem. /proc/mounts always shows the correct mount information. You could update /etc/mtab from /proc/mounts to correct it both after boot and after running the mount or umount commands to change mounts. Run "fgrep -v rootfs /proc/mounts >/etc/mtab" to correct /etc/mtab. Note that mounting or symlinking /proc/mounts to /etc/mtab causes other problems such as breaking the df command. You can change your read-only root filesystem to read-write mode immediately with this command run by the root user: mount -n -o remount,rw / - Fred

2 1

sed
by Scott McClanahan 24 May '08

24 May '08

Not specific to CentOS but I know you guys would be really helpful anyhow. Basically, I have a file which has been editted in the past very similarly to the hosts file only now I want to use it as a hosts file and need to run some fancy sed to massage the data into shape. Currently, the data in the file is in the form of <ip address> <tab> <short hostname> <space> <short hostname alias>. In some cases there may not be any aliases so the end of line would be right after the short hostname (no space at the end either). In other cases there could be many space separated short hostname aliases. What I have been trying to do without success is add our domain name to the first string after the ip address and tab character. As an example, == Before == 1.1.1.1 foo 10.10.10.10 bar bar2 100.100.100.100 foobar foobar2 foobar3 == After == 1.1.1.1 foo.contoso.com 10.10.10.10 bar.contoso.com bar2 100.100.100.100 foobar.contoso.com foobar2 foobar3 Any advice on how to pull this off? Thanks.

8 9

More recent GDE on CentOS 5+
by MHR 23 May '08

23 May '08

I have not had any success building a more recent version of GDE than 2.16.0 on CentOS. I tried jhbuild, and went line by line using the how-to web page for jhbuild (http://www.gnome.org/~jamesh/jhbuild.html) and I get hung up on dbus-glib-l (which does not appear to be in CentOS or available for it, at least from base, updates, extras, KB & rpmforge). Garnome is another possibility that I haven't looked at yet 'cuz jhbuild is supposed to be easy and fully automated (it might be, if everything it needs is already there, but it doesn't tell you up front what that means or how to get it or ...). Gnome "says" we should use the GDE that ships with our distribution, but RH (CentOS) has to oldest revision available. To get a newer one, the Gnome people recommend building my own. Has anyone tried this successfully? How? Thanks. mhr

2 1

Re:Re:Re:Can't get past the splash screen
by Eon Strife 23 May '08

23 May '08

Hi, Thanks, I check those folders, and they are already empty. Now, I tried to remove the freenx by using yum, and then I removed the files it left behind manually in: /usr/bin/nxserver /usr/lib/nx /var/lib/nxserver /etc/nxserver along with the nx user and group and reinstall. The problem worsen, no matter what user I tried, I always got Session Startup Failed: === NX> 700 Session id: cluster.hpc.org-1014-084919CE7F9816540BDEDD5A7928084E NX> 705 Session display: 1014 NX> 703 Session type: unix-gnome NX> 701 Proxy cookie: ee398e9cedaf3adbba4dc966d4433dee NX> 702 Proxy IP: 127.0.0.1 NX> 706 Agent cookie: ee398e9cedaf3adbba4dc966d4433dee NX> 704 Session cache: unix-gnome NX> 707 SSL tunneling: 1 NX> 105 /usr/bin/nxserver: line 1077: 8588 Terminated sleep $AGENT_STARTUP_TIMEOUT NX> 596 Session startup failed. NX> 1004 Error: NX Agent exited with exit status 1. NX> 1006 Session status: closed Can't open /var/lib/nxserver/db/running/sessionId{084919CE7F9816540BDEDD5A7928084E}: No such file or directory. mv: cannot stat `/var/lib/nxserver/db/running/sessionId{084919CE7F9816540BDEDD5A7928084E}': No such file or directory NX> 280 Exiting on signal: 15 === I tried alternative solution by using VNC. In order to have access to desktop, I modifed the content of the Xstartup file (for the root in /root/.vnc/xstartup and for the regular user in /home/EonStrife/.vnc/xstartup) to be : === #!/bin/sh # Uncomment the following two lines for normal desktop: # unset SESSION_MANAGER # exec /etc/X11/xinit/xinitrc [ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup [ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources xsetroot -solid grey vncconfig -iconic & xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" & #startx & exec gnome-session & #twm & === The funny thing is that for regular user I can access the desktop, but for the root I'm only treated with the terminal. (BTW, the client I used are tightVNC and RealVNC) Thanks. ===Previous Message=== Eon Strife wrote: > Hi, > Thanks, it's Gnome, and I'm stuck when I login as root. > By using Putty, I managed to create a new user, and then I tried to login to desktop(using nomachine) as that user, and yes, it works. The problem now is that I stuck when I login as the root. > > NX> 596 Session startup failed. <- The additional line in the sshlog of the root > NX> 1004 Error: NX Agent exited with exit status 1. > Can't open /var/lib/nxserver/db/running/sessionId{0C2C8B077AB56ED37F7A5A72FE8FA7BF}: No such file or directory. > mv: cannot stat `/var/lib/nxserver/db/running/sessionId{0C2C8B077AB56ED37F7A5A72FE8FA7BF}': No such file or directory > NX> 1006 Session status: closed > Exited with status 0. User pressed Ok. As a regular user you shouldn't be able to look into that directory, so that's normal. Only root and nx can do that. Interesting (at least to me) is that you get an error concerning a session that I do not believe it should be looking for. It's like it's attempting to reattach to a session that doesn't exist and then it fails. I could be incorrect, but at this point it's simply a data point. On the client machine (assuming it is linux), have you removed all session data from the user's home directory? By default this is ~/.nx/cache-unix-windowmanagername (for you that is likely gnome) and ~/.nx/letter-hostname-screen-somerandomhashIthink/ Don't remove the config directory or else you'll have to set up the nx information again. See if that doesn't fix the issue. It may not, and I'm sorry if it doesn't, but I am not entirely sure about this particular issue. If the client machine is a windows machine there is a .nx directory, but I am not sure where it's kept. C:\documents and settings\user\.nx maybe. That is where it resides on my windows install at work on XP. I may or may not have changed the directory so you might have to look around a bit. HTH Alex White -- ethericalzen at gmail.com Life is a prison, death is a release Send instant messages to your online friends http://uk.messenger.yahoo.com

2 1

Re: [CentOS] Re: Need help with rsync. [solved]
by James B. Byrne 23 May '08

23 May '08

In-Reply-To: <f4e013870805211022r36194b29gb74ca4421dc2ee77(a)mail.gmail.com> On: Wed, 21 May 2008 10:22:19 -0700, MHR <mhullrich(a)gmail.com> wrote: >> On Wed, May 21, 2008 at 8:37 AM, James B. Byrne <byrnejb(a)harte-lyne.ca> >> wrote: >> >> This indeed turned out to be an SELinux policy problem which I have since >> resolved. > > Whoa, whoa, whoa, nice shooting, Tex! (Ghostbusters) > > Not so fast - please post the solution, too, for posterity (and those > of us who don't use SELinux but might, someday, in the not too distant > far future...). > > Thanks. > > mhr Dealings with SELinux issues typically do not lend themselves to short answers. SELinux is like an onion, each each exception blocks access until resolved. Thus each policy change has to be made individually and then the process retested so that the next impediment evidences itself. On CentOS-5 your friends are: # grep avc /var/log/messages # grep <process> /var/log/audit/audit.log and some of the more useful utilities are: # audit2allow # audit2why # chcon # restorecon # sealert # semanage When I suspect (and that is often the hardest part of the whole exercise, realizing that SELinux is the problem) that SELinux is involved in a problem I start by checking the system log file /var/log/messages with grep avc. If I see things like this: # grep avc /var/log/messages May 16 04:02:33 inet01 kernel: audit(1210924952.785:22973): avc: denied { read } for pid=22282 comm="prelink" name="setserial" dev=dm-0 ino=3309644 scontext=user_u:system_r:prelink_t:s0 tcontext=system_u:object_r:rsync_data_t:s0 tclass=file Then I infer that I have a problem with either the SELinux file contexts or the system policy file. If the SELinux problem is announced at the desktop then you may also find it useful to check for this: # grep setroubleshoot /var/log/messages In which case you may see something like this: Dec 17 14:13:24 inet01 setroubleshoot: SELinux is preventing /usr/sbin/httpd (httpd_t) "write" to virtual.d (etc_t). For complete SELinux messages. run sealert -l 15618e2e-044c-4c4c-b3fc-ec1eba554d02 In this case you can follow the suggestion given in the log message and run sealert: # sealert -l 15618e2e-044c-4c4c-b3fc-ec1eba554d02 Summary SELinux is preventing /usr/sbin/httpd (httpd_t) "write" to virtual.d (etc_t). Detailed Description SELinux is preventing /usr/sbin/httpd (httpd_t) "write" to virtual.d (etc_t). The SELinux type %TARGET_TYPE, is a generic type for all files in the directory and very few processes (SELinux Domains) are allowed to write ... yada-yada-yada... ... Allowing Access You can attempt to fix file context by executing restorecon -v virtual.d The following command will allow this access: restorecon virtual.d And then you can try that, although I have rarely had a problem with SELinux solved so simply: # cd /path/to/virtual.d # restorecon virtual.d Anyway, if that does not work, or one never received an setroubleshoot report to begin with, then I end up turning to audit2allow. I do something like this (where rsync is the process that I am having difficulty with, it could be httpd, vsftp or anything else): # grep rsync /var/log/audit/audit.log | audit2allow Which may yield a report something like this: #============= prelink_t ============== allow prelink_t rsync_data_t:file read; Now, if this does not look too alarming in terms of the access that rsync seems to be seeking (being able to read files to be transferred seems a logical enough expectation and the benefit/limitations of prelink seem to require access in this instance) then we can add this permission to our policy via a local module. You make one of these in this fashion: # # grep rsync /var/log/audit/audit.log | audit2allow -M localrsyncmod ******************** IMPORTANT *********************** To make this policy package active, execute: semodule -i localrsyncmod.pp # Again, you simply follow the instructions given in the report. # semodule -i localrsyncmod.pp Now you do yet another test and check the log files. If the problem is fixed, then great, you are finished. Usually, however, SELinux issues continually reveal one permission problem after another, sometimes with different processes, until, at last, they have all been accommodated. Consequently you end up re-running your tests, checking the audit files, and modifying the local policy one item at a time. Note that simply overriding what SELinux is prohibiting is not what I am advocating here. Sometimes the problem is that the software needs its file system access expectations trimmed back and that requires filing a bug report with the maintainers. However, in a production environment you normally just have to get things working and what I usually do is weigh what the program is requesting against what I want it to do for me. Often the problem is that the default policy is simply too restrictive. On rare occasions I do actually file a bug report but almost always override the local policy anyway just to get on with the job. I hope this helps. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss