Re: [CentOS] enlarging partition and its filesystem
On 19/05/16 09:54, Fred Smith wrote: >I've used gparted live cd a number of times, but don't think I knew that it handled lvm2 also. Well, what you are doing with gparted has nothing to do with LVM; just the drive (really, the image file) itself - similar to buying a bigger hdd and then cloning from old (smaller) to new (bigger). Then you have to boot into the system and extend the volume group, logical volume, and ultimately the filesystem. >Since it does, if I resize the lvm, wouldn't the contained filesystem be automatically resized too? (as it has been when I've resized physical partitions containing NTFS and EXT2/3/4 filesystems.) With lvm, lvextend can automatically resize the the underlying ext2/3/4 filesystem for you if you add the extra *-r* option. If you omit it, then you'll need to run *resize2fs* as detailed by Ian. As for NTFS, yes, once you use finish off with gparted, then the filesystem will have been automatically resized to fill the entire partition (haven't worked on partitioning in windows for a while so don't quote me). ak. *Note* Now that I'm having a second look at Ian's instructions, the pvcreate command is not required as you are not adding a second drive, just making the original one bigger. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] DOS line ends on /var/log/boot.log on CentOS 6.7 ?
On 19.05.2016 18:56, Kay Schenk wrote: Hello all -- Recently, I'm seeing DOS line ends, ^M, on my /var/log/boot.log file. Honestly, I don't check this very often so I can't say exactly when this occurred. Is this just MY experience or are others seeing this also. this file shows ident content, as you see during boot, when you start without 'quiet' and there are green or red colors, and these are also stored - somewhat ANSI escape sequences; when you do this: cat /var/log/boot.log you will see the AHA ;-) ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] devtoolset-4
Are you asking if the new libstdc++ is statically linked into your app only for the new functions but your app remains dynamically linked to the old one for the parts of C++ that have remained unchanged, the answer is “no”. Your app is linked to the new library, period. You can use ldd(1) to prove this to yourself. I am not so sure. That is what I thought, but then I compiled something with a compiler from devtoolset (5.2.1) with --std=c++11 flag. ldd gives me: ldd a.out linux-vdso.so.1 => (0x7fff6e5ff000) libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x0039d840) libm.so.6 => /lib64/libm.so.6 (0x0039ce80) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x0039d800) libc.so.6 => /lib64/libc.so.6 (0x0039ce00) /lib64/ld-linux-x86-64.so.2 (0x0039cdc0) Which is stock libstdc++ Devtoolset version is located at: /opt/rh/devtoolset-4/root/usr/lib/gcc/x86_64-redhat-linux/5.2.1/libstdc++.so Additionally there is libstdc++_nonshared.a: /opt/rh/devtoolset-4/root/usr/lib/gcc/x86_64-redhat-linux/5.2.1/libstdc++_nonshared.a In the guide there is a matrix of compatibility: https://access.redhat.com/documentation/en-US/Red_Hat_Developer_Toolset/4/html/User_Guide/sect-Red_Hat_Developer_Toolset-Compatibility.html it says that If I compile with DTS on 6.6 thet it will run on 6.6 and above, but it doesn't say if DTS has to be installed on that machine. So this got me to thinking. I definitelly will check that :) and I really believe that it can be this way. Althought it sounds like black magic. Regards, -Jarek 2016-05-19 23:02 GMT+02:00 Warren Young : > On May 19, 2016, at 3:30 AM, Jarosław Bober > wrote: > > > > Do I have to install devtoolset on all my machines that I want to run > this > > app? > > Probably, yes. That, or redistribute parts of it with your app, either by > cherrypicking files from the devtoolset RPM or statically linking to it. > > > Or would it use built-in libstdc++ library, linking statically only > > the missing parts? > > Are you asking if the new libstdc++ is statically linked into your app > only for the new functions but your app remains dynamically linked to the > old one for the parts of C++ that have remained unchanged, the answer is > “no”. Your app is linked to the new library, period. You can use ldd(1) > to prove this to yourself. > > Yes, this is a pain, which is why most people writing software for older > CentOS releases don’t upgrade their development tools. There’s a lot to be > said for holding off on using new language features until they’re available > in the stock version of the tools for all OSes you need to deploy on. > > I’d like to be using C++11 myself, but a feature-complete version of C++11 > didn’t appear in g++ until 4.8, which first shipped in CentOS 7. I just > got done backporting a feature to a 32-bit CentOS 5 box, so I’m probably > not going to be able to use C++11 for another 3-5 years. Sad, but I still > get the work done with C++98. > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] devtoolset-4
On May 20, 2016, at 8:17 AM, Jarosław Bober wrote: > > ldd gives me: > ldd a.out > linux-vdso.so.1 => (0x7fff6e5ff000) > libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x0039d840) In that case, I don’t see how you can be making use of any C++11/14 features that aren’t implemented by the compiler itself (e.g. type inference via “auto”) or purely in template form. Any feature that uses the compiled Standard C++ Library can’t be using the new library. That may be useful for your purposes. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] DOS line ends on /var/log/boot.log on CentOS 6.7 ?
On 05/19/2016 09:56 AM, Kay Schenk wrote: Hello all -- Recently, I'm seeing DOS line ends, ^M, on my /var/log/boot.log file. Honestly, I don't check this very often so I can't say exactly when this occurred. Is this just MY experience or are others seeing this also. Additionally, boot/log seems very sparse. Is an old issue still in force on this? https://www.centos.org/forums/viewtopic.php?t=17313 Should I get the updated script from CentOS Plus? Thanks for any help. -- Hello again, list. Please disregard this for the time being. I got a personal response that pointed out the doing a cat on boot.log produced a specific correct format whereis I was used to using my gui editor to display log files. Using the "log viewer" utility also shows these non-unix line ending which I found annoying. For those who are interested in additional boot.log settings, I found this page: https://www.centos.org/docs/5/html/5.2/Deployment_Guide/s2-sysconfig-init.html from the old deployment guide but I'm sure these en variables are the same now -- well at least in the 6.x series. -- MzK "Time spent with cats is never wasted." -- Sigmund Freud ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] bareos on CentOS 6
On Tue, May 17, 2016 3:37 pm, m.r...@5-cent.us wrote: > Paul Heinlein wrote: >> On Tue, 17 May 2016, m.r...@5-cent.us wrote: >> >>> I'm hoping *someone* here has worked a bit with bareos. I've tried >>> posting to the google groups for it... and haven't even had one person >>> view my post >>> >>> It was working fine, backing up windows boxes for months. Then, about >>> a week ago, the server got a regular yum update, and rebooted... and >>> it's >>> broken. A job will start... and just keep running forever (as in, over >>> the weekend) and never end; normally, they were all done in a few >>> hours. >>> >>> I stopped bareos-dir, then -fd, then -sd, restarted, no joy. Then I >>> tried shutting them all down, and service restart postgres, and *then* >>> starting up -sd, -fd and -dir. I was starting them manually Friday, and >>> they'd run and finish. But the nightly b/u, a job started... and was >>> still running yesterday. >>> >>> Anyone have any ideas? >> >> Just one idea, and it's not a promising one: >> >> Any chance that the Windows client is spinning trying to backup cygwin >> files, specifically /var/log/lastlog? > > Nope. I'm *explicitly* telling bareos to back up c:/Users/, and, in a > couple of cases, d:/ or e:/ - we don't care about the system or logs at > all. If something happens, desktop support will ghost reimage them. What I would try to do is: the moment no other jobs are running do strace on storage daemon (we assume server part has changed, client part hasn't) then run backup of that particular client. See where it gets you. Also: you never mentioned anything about volumes: are they getting created? Getting data coming to them? I know it has been some time, you probably solved it. If yes, tell us what was it and what solved it. Valeri > > And it was working with no trouble > >mark > > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos > Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
