similar to: Possible funny with /sbin/fsck

Hello All, Hardware: HP ML570 2G Ram Dual 2.8G procs Compaq 5300 Smart Array Controller Software: Centos 4.1 I yum-med a server last week and rebooted it. When it came up, it stopped. Looking at the console, I got: ---snip Setting Hostname: OK Checking root filesystem: /dev/cciss/c0d0p10 is mounted, e2fsck cannot continue, aborting failed *** an error occurred during the file system check

On Fri, March 10, 2017 11:57, m.roth at 5-cent.us wrote: > > Looks like only one sector's bad. Running badblocks should, > I think, mark that sector as bad, so the system doesn't try > to read or write there. I've got a user whose workstation has > had a bad sector running for over a year. However, if it > becomes two, or four, or 64 sectors, it's replacement

Hi, I am rsyncing from my source server A to a destination server B. A/vol1 contains two files syslog.txt and syslog.bak B/vol1 contains five files syslog.txt, syslog.bak, initlog.txt, internal.txt, and internal.bak. I want to preserve the 5 files on B/vol1 when I do rsync from A to B. Here is the command I use: rsync -av --delete --exclude-from=EXCLUDEFILE A/ B I've tried the option

Hello, I was wondering about the feasibility of including a startup script for icecast for redhat/fedora installs? I've had to do an rpm install on an fc4 box, and a source install, rpms couldn't be found for an rh9 machine, yah i know that's old. And in both cases i had to drop in a custom-made startup script, see below. I was wondering esepcially in the case of the rpm, and

On Tue, Mar 14, 2017, 7:41 AM James B. Byrne <byrnejb at harte-lyne.ca> wrote: > On Fri, March 10, 2017 11:57, m.roth at 5-cent.us wrote: > > > > > Looks like only one sector's bad. Running badblocks should, > > I think, mark that sector as bad, so the system doesn't try > > to read or write there. I've got a user whose workstation has > > had

Hello Centos, I am getting an error that I am not familiar with when I restart ssh. [root at virtcent01:~] #service sshd restart Stopping sshd: [ OK ] Starting sshd:WARNING: initlog is deprecated and will be removed in a future release [ OK ] [root at virtcent01:~] # I was just

I am changing a system from zap to DAHDI. I removed everything zap. when doing the command: sh -x /etc/init.d/dahdi start, I see initlog -q -c 'modprobe wct4xxp' sh: /sbin/ztcfg: No such file or directory FATAL: Error running install command for wct4xxp doing updatedb then, locate zap returns me /var/lib/asterisk/sounds/spy-zap.gsm /usr/share/groff/1.18.1.1/font/devps/zapfdr.pfa

In fedora core 2 and 3 starting asterisk using contrib/init.d/rc.redhat.asterisk (installed by make config), if asterisk dies, it doesn't restart. Seems the problem is in initlog. The standard way to start services in fedora is by calling daemon <service> that results in: $nice initlog $INITLOG_ARGS -c "$*" Removing initlog works correctly. I don't know if this is a

SELinux is set to permissive mode and warns on startup of a service (during boot-up): Warning! Could not relabel /dev/pts/0 with user_u:object_r:initrc_devpts_t, not relabeling.Operation not permitted So far, so good. But this logging let's this application and all that should start after it hang. ps then shows: initlog -q -c /etc/rc3.d/S98bigsister start (bigsister is a monitoring agent)

I updated six severs this weekend to 3.6 and I am now getting some junk spewed into the "messages" file on "all" six severs. (Only on boot up) There was none of this happing previously. I attached a txt copy because the encoding of my mailer doesn't like it. Also noticed the spew looks simular to the contents of the "initlog.conf" file, attched also. I'm

If I have the 6th column in fstab (the pass column) set to 0, does that mean disk checks will never be forced at boot regardless of anything like File System State, Mount Count, and Check Interval on the file system itself, or are there exceptions to this? I know `man fstab` says: If the sixth field is not present or zero, a value of zero is returned and fsck will assume that the filesystem does

For some time now I have been puzzled as to why certain portions of my system boot were quite slow -- but only after journal recoveries. I was fearing that there was some ugly interaction between the recovery and the use of the journal shortly afterward but alas that is not the case. So just in case anybody else is seeing this problem and decides to try to hunt it down, let me save you some

Hi, I have just installed 2.0.1 on two boxes. One box did not have shorewall on at all and the other had 1.4.10 on. Both these boxes are Debian. On the 1.4 box it upgraded fine, and everything works OK. The /etc/init.d/shorewall script runs on startup and loads shorewall fine. On the clean box the /etc/init.d/shorewall script does not seem to work. When run it produces no output, so on bootup

Hello. I've problem with rsync 3.1.3 in my distribution (TLD Linux). It segfaults when service is started. Services are controlled by rc-scripts (TLD Linux is systemd free). Actual command thats being run by rc-scripts is: nice -n 15 initlog -c "/usr/bin/rsync --daemon --dparam=pidfile=/var/run/rsync.pid" When ran by hand it works, when ran from rc-scripts rsync segfaults. The

I tried to use tightvnc back in August and had some help, but I stopped due to IPv6 support. Now I am back at tightvnc and cannot get the server started. This is on a new Centos install that did have regular vncserver working on it (I did a yum erase vnc-server first). So I have a working /etc/sysconfig/vncserver and my user has the appropriate ~/.vnc files that worked with regular vnc.

Hey! No, actually shorewall works very well and starts and so on... Thanks for this! Problem is that it won''t start on boot it seems. At least it doesn''t enable forwarding. However, if I do /etc/init.d/shorewall restart it enables forwarding and the rest... But not if I do /etc/init.d/shorewall start ;) Seems weird... System is Debian Sid, Shorewall is prepackaged by Debian...

I have worked quite a bit with CentOS 4.x with SAN, multipathing, LVM etc. The way I mount my file systems is using a script that is called during startup that runs fsck, imports the physical volumes, and volume groups, activates the logical volumes, creates the mount point if needed then mounts the volume, I mainly made it for software iSCSI due to the iscsi stack loading after the system mount

Hello all, I am trying to port some more code from windows 2000 to linux. The specific functionality I would like to port is called "Structured Exception Handling" and it works like so: 1. Define a function which based upons a signal throws an exceptoion. For example: void translateException(unsigned int u, EXCEPTION_POINTERS* pExp) { switch (u) { case (unsigned

After looking at this problem longer, I believe that there is something wrong with the disassembler. When I run my transformation and then disassemble the output, I get bytecode that looks like: ----- int %main(int %argc, sbyte** %argv) { entry: alloca int ; <int*>:0 [#uses=3] alloca sbyte** ; <sbyte***>:0 [#uses=3] store int %argc,

2013/2/12 Doug Lytle <support at drdos.info> > >> non-standard locations such as /usr/local/sbin > > If compiling from source, it'd normally be specified by the --prefix > option: > > ./configure --prefix=/usr/local > > Doug > > -- > Ben Franklin quote: > > "Those who would give up Essential Liberty to purchase a little Temporary >